Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
top
top

This topic describes how to use the the JCR Import/Export Tool which is very useful for copying XperienCentral environments
Excerpt
Info

Beginning in version R28, XperienCentral no longer uses the Apache Jackrabbit JCR indexing solution by default. This topic is only relevant to users of XperienCentral versions R27 and lower or if you configure XperienCentral to use Apache Jackrabbit. See The XperienCentral JCR Index for more information.



In This Topic

Table of Contents
maxLevel2
minLevel2

...

Error message

Solutions

java.io.IOException
 

Remove the database.

Could not register namespace mapping wo -> http://gx.nl/wm9objectRemove the /repository/ directory.

...

Code Block
themeEclipse
borderStylesolid
titleinstructions.xml
<?xml version="1.0"?>
<mapping xmlns="http://webmanager.gx.nl/xsd/JCRmapping/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://webmanager.gx.nl/xsd/JCRmapping/1.0.0 webmanager-jcr-mapping-V1.0.0.xsd">
   <description></description>
    
   <operations>

      <!-- set the hostnames -->
      <set>
      <query>//element(*,wm:website_settings)</query>
      <properties>
         <property>wm:backend_hostname</property>
      </properties>
      <values>
         <value>webmanager.test.gx.nl</value>
      </values>
      </set>
      
      <add>
         <query>//element(*,wm:website_settings)</query>
         <properties>
            <property>wm:backend_server_alias</property>
         </properties>
         <values>
            <value>webmanager.gx.nl</value>
         </values>
      </add>
      
      <substitute>
         <query>//element(*,wm:dbcpmanager)</query>
         <properties>
            <property>wm:datasourceurl</property>
         </properties>
         <pattern>(.*)@production\.gx\.nl(.*)</pattern>
            <replacement>$1@test.gx.nl$2</replacement>
      </substitute>

      <remove>
         <query>//element(*,wm:website_settings)</query>
         <properties>
            <property>wm:frontend_server_alias</property>
         </properties>
      </remove>
      
   </operations>
    
</mapping>


Back to top


...

JNDI

As can be seen above for For installations that make use of JNDI to access the database, a different set of arguments needs to be passed into the command. To determine if JNDI is being used, simply view the repository.xml. If the driver is javax.naming.InitialContext, JNDI is being used:

<param name="driver" value="javax.naming.InitialContext" />

Because the repository.xml by default does not contain the actual connection details and no application server context is available during the execution of this tool, it is necessary to provide these connection details directly or indirectly in the arguments passed.

...