Page History

...

...

Gathering the Source Material

...

If the target environment B has to be identical, it is necessary to use the same configuration.xml as on the source environment A. It is important that the configuration.xml file contains the hostnames of both environments. XperienCentral checks whether it is called by the hostnames as configured in the configuration.xml. There will be an error if the hostnames of environment B are not also present in the configuration.xml. New configuration files can be obtained from GX Software.

Back to top

...

Setting up the Target Environment

...

Unzip C:\GX\XperienCentral-copy-of-A\ext\apache-tomcat-7.0.39.zip to C:\GX\XperienCentral-copy-of-A\apache-tomcat\. Edit the C:\GX\XperienCentral-copy-of-A\apache-tomcat\conf\server.xml to make sure it uses the .WAR files that were extracted in the previous step. The following is an example of a server.xml: 

<Server port="8005" shutdown="SHUTDOWN">
   <GlobalNamingResources>
      <!-- Userdatabase is used to secure admin pages! Make sure the path is ok otherwise the admin jsps will not work -->
   <Resource name="WMUserDatabase" auth="Container" type="org.apache.catalina.UserDatabase" description="XperienCentral user database" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" pathname="/vol/www/tomcat-mywebsite/deploy/admin-users.xml" />
   </GlobalNamingResources>
   <Service name="WebManager">
   <Connector port="8009" enableLookups="false" redirectPort="8443" debug="1" protocol="AJP/1.3" URIEncoding="UTF-8" secretRequired="false" connectionTimeout="600000"/>
   <Engine name="WebManager" defaultHost="localhost">
      <Realm className="org.apache.catalina.realm.LockOutRealm" >
         <Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="WMUserDatabase"/>
         </Realm>
         <Host name="localhost" unpackWARs="true" autoDeploy="false" deployOnStartup="false" appBase="/vol/www/tomcat-mywebsite/deploy">
            <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
            <Context path="/web" docBase="webmanager-backend-webapp-1.0-SNAPSHOT.war">
               <Valve className="org.apache.catalina.authenticator.DigestAuthenticator" cache="true" />
            </Context>
         </Host>
      </Engine>
   </Service>
</Server>

...

Place the configuration.xml File

Place the configuration.xml file in the folder C:\GX\XperienCentral-copy-of-A\configuration\. A website will only run properly if the hostnames are present in the configuration.xml. In this case the configuration.xml is used on both environments. Therefore the configuration.xml needs to contain the hostnames of source environment A and target environment B (in this example these hostnames are "127.0.0.1" and "localhost"). 

Check the springmvc-servlet.xml

Open the file C:\GX\XperienCentral-copy-of-A\deploy-wars\webmanager-backend-webapp-1.0-SNAPSHOT\WEB-INF\springmvc-servlet.xml. Check and change the pathnames for the parameters cacheDirectory, repositoryDirectory and webrootDirectory. For example: 

<property name="cacheDirectory">
   <value>C:\GX\XperienCentral-copy-of-A\work\cache\services</value>
</property>
<property name="repositoryDirectory">
   <value>C:\GX\XperienCentral-copy-of-A\work\jcr</value>
</property>
<property name="webrootDirectory">
   <value>C:\GX\XperienCentral-copy-of-A\deploy-wars\webmanager-static-webapp-1.0-SNAPSHOT</value>
</property>

...

Check the startup_config.xml

Open the file C:\GX\XperienCentral-copy-of-A\deploy-wars\webmanager-backend-webapp-1.0-SNAPSHOT\WEB-INF\startup_config.xml. Check and change the pathnames for the parameters base_directory and config_filename. For example: 

<entry name="base_directory" value="C:\GX\XperienCentral-copy-of-A\work" />
<entry name="config_filename" value="C:\GX\XperienCentral-copy-of-A\configuration\configuration.xml"/>

...

Start Tomcat

After performing these tasks Tomcat can be started by running C:\GX\XperienCentral-copy-of-A\apache-tomcat\bin\startup.bat.

Back to top

...

Troubleshooting

The following are issues that might occur during the process as described in this document.

...

If this error appears in the Tomcat log file, then the frontend_hostname of the source environment A has to be added as frontend_server_alias to environment B. This can be done manually using the Setup Tool.

ClassNotFoundError while creating export of the JCR

...

1. The file logging.properties.
2. A folder lib containing a number of files.

...

Back to top