In case of the standalone mode where the JCR and its dependencies are not provided, you will need to deploy the whole ear file corresponding to the artifactId exo.jcr.ear and groupId org.exoplatform.jcr, the rar file is embedded into the ear file. In case the JCR and its dependencies are provided like when you use it with gateIn for example, you will need to deploy only the rar file corresponding to the artifactId exo.jcr.connectors.jca and groupId org.exoplatform.jcr.

Then you will need to configure the connector itself, for example for JBoss AS, you need to create in your deploy directory a file of type *-ds.xml (jcr-ds.xml for example) with the following content:

<connection-factories>
  <tx-connection-factory>
    <jndi-name>jcr/repository</jndi-name>
    <xa-transaction/>
    <!-- The rar name will be exo.jcr.connectors.jca.X.Y.Z.rar in case you deploy only the rar file -->
    <rar-name>exo.jcr.ear.ear#exo-jcr.rar</rar-name>
    <adapter-display-name>eXo JCR Adapter</adapter-display-name>
    <connection-definition>org.exoplatform.connectors.jcr.adapter.SessionFactory</connection-definition>
    <!--
    <config-property name="PortalContainer" type="java.lang.String">portal</config-property>
    -->
    <config-property name="Repository" type="java.lang.String">repository</config-property>
  </tx-connection-factory>
</connection-factories>