Deploying the Crystal Enterprise web desktop

To deploy the Java version of the Crystal Enterprise web desktop, you must create virtual path mappings on your Java web application server. They map specific URLs to the web application archives (.war files) that implement the Crystal Enterprise User Launchpad and the Crystal Enterprise Admin Launchpad.

Once you have deployed the Launchpads and the Web Component Adapter, set the context path for the WCA in the Crystal Applications area of the Crystal Management Console. Setting the context path ensures that users can view reports using the Active X viewer and the Java viewer shipped with Crystal Enterprise.

To deploy the Crystal Enterprise Launchpads on Tomcat

1. Shut down Tomcat if it is running. Type sh $CATALINA_HOME/bin/shutdown.sh
2. Open the file $CATALINA_HOME/conf/server.xml, in a text editor such as vi.
3. Add the following lines directly above the line <!-- Tomcat Examples Context -->:

   <Context path="/crystal/enterprise10/adminlaunch"
   

   docBase="crystal_root/enterprise/java/applications/admin.war"
   

   debug="0" reloadable="false"/>
   

   <Context path="/crystal/enterprise10/desktoplaunch"
   

   docBase="crystal_root/enterprise/java/applications/desktop.war"
   

   debug="0" reloadable="false"/>
   

   Substitute your Crystal Enterprise install directory for crystal_root

4. Save the file.
5. Restart Tomcat by typing sh $CATALINA_HOME/bin/startup.sh
6. To test the Crystal Enterprise User Launchpad, open a web browser and type http://servername:8080/crystal/enterprise10/desktoplaunch in its address bar. For servername, substitute the name of the machine where you installed Tomcat.

   The Crystal Enterprise User Launchpad should start.

7. To log on to the Java version of the Crystal Enterprise web desktop, click the Crystal Enterprise link.
8. To test the Crystal Enterprise Admin Launchpad, open a web browser and type http://servername:8080/crystal/enterprise10/adminlaunch in its address bar. For servername, substitute the name of the machine where you installed Tomcat.

   The Crystal Enterprise Admin Launchpad opens. Do not click the link to the Crystal Management Console. You must configure the Web Component Adapter before the CMC can start. See Deploying the Web Component Adapter for instructions.

9. Once you have deployed the CMC, ensure that the context path for the WCA is set correctly in the Crystal Applications area of the CMC. See Deploying the Web Component Adapter for instructions.

To deploy the Crystal Enterprise Launchpads on BEA WebLogic

1. Open a web browser, and type http://servername:7001/console in its address bar to open the BEA WebLogic Administrative Console.

   Substitute the name of the machine where you installed BEA WebLogic for servername.

   Note:    By default, BEA WebLogic uses port 7001. If you configured your application server to use a different port number, substitute that port number in the URL.

2. Deploy the Crystal Enterprise User Launchpad as a new web application. Use the .war file found at crystal_root/enterprise/java/applications/desktop.war, and set the context root to /crystal/enterprise10/desktoplaunch

   Note:    To set the context root for the web application, edit the Web Application Deployment Descriptor. [Click Edit Web Application Deployment Descriptors. Click WebApp Ext in the lefthand tree menu, then make your changes to the Context Root field. Click Apply].

3. To test that the Crystal Enterprise User Launchpad deploys correctly, type http://servername:7001/crystal/enterprise10/desktoplaunch in the address bar of a web browser.

   Click the Crystal Enterprise link to launch the application and test that desktop.war was deployed successfully.

4. Deploy the Crystal Enterprise Admin Launchpad as a new web application. Use the .war file found at crystal_root/enterprise/java/applications/admin.war, and set the context root to /crystal/enterprise10/adminlaunch

   Do not click the link to the Crystal Management Console (CMC). You must configure the Web Component Adapter before the CMC can start. See Deploying the Web Component Adapter for instructions.

5. Once you have deployed the CMC, ensure that the context path for the WCA is set correctly in the Crystal Applications area of the CMC. See Deploying the Web Component Adapter for instructions.

To deploy the Crystal Enterprise Launchpads on IBM WebSphere

1. Start the IBM WebSphere Administrative Console. (http://servername:9090/admin/).
2. Install the Crystal Enterprise User Launchpad as a new application. Use the .war file found at crystal_root/enterprise/java/applications/desktop.war, and set the context root to /crystal/enterprise/desktoplaunch
3. Start the new application.
4. To test that the Crystal Enterprise User Launchpad deploys correctly, type http://servername:9080/crystal/enterprise10/desktoplaunch/launchpad.html in the address bar of a web browser.

   Click the Crystal Enterprise link to launch the application and test that desktop.war was deployed successfully.

5. Install the Crystal Enterprise Admin Launchpad as a new application. Use the .war file found at crystal_root/enterprise/java/applications/admin.war, and set the context root to /crystal/enterprise10/adminlaunch
6. Start the application.
7. To test that the Crystal Enterprise Admin Launchpad deploys correctly, type http://servername:9080/crystal/enterprise10/adminlaunch/launchpad.html in the address bar of a web browser.

   Do not click the link to the Crystal Management Console. You must configure the Web Component Adapter before the CMC can start. See Deploying the Web Component Adapter for instructions.

8. Once you have deployed the CMC, ensure that the context path for the WCA is set correctly in the Crystal Applications area of the CMC. See Deploying the Web Component Adapter for instructions.