Home
 

User login

 
 

Navigation

 
 

Events

« May 2008
SunMonTueWedThuFriSat
123
45678910
11121314151617
18192021222324
25262728293031
 
Home

Running the Cape Clear Server 7.0.1 Installer

Submitted by admin on Thu, 2007-05-03 12:01.

The following procedure describes how to complete the installation process for Cape Clear Server. The dialog boxes that are displayed on a Windows installation may differ slightly from the dialog boxes on a UNIX installation.

  1. The initial installer dialog box is displayed, as shown below.


    Initial Cape Clear installation panel

    Figure 1. Initial Cape Clear installation panel

  2. Click Next. The Cape Clear license agreement is displayed, as shown below.


    Viewing the Cape Clear license agreement

    Figure 2. Viewing the Cape Clear license agreement

  3. Read the license agreement and then click Accept to accept the terms of the license agreement.

  4. The installer prompts you to choose an installation directory for Cape Clear Server, as shown below.


    Choosing an installation directory

    Figure 3. Choosing an installation directory

    In the text box, type a path or click Select to browse your file system for the absolute path of the directory where you want to install Cape Clear Server.

    Note

    Do not enter a path that includes directory names containing spaces. For example, do not install the products in the Program Files directory. In addition, do not specify a directory path that contains international characters.

    If a confirmation message to create the directory is displayed, click Yes.

  5. Select the type of container into which Cape Clear Server will be deployed, either the JBoss installation that is bundled with Cape Clear Server (Use default container (JBoss)), or a pre-existing application server or servlet engine installation (Use alternative container), as shown below.


    Selecting the type of container

    Figure 4. Selecting the type of container

     

Depending on your choice of container in which to deploy Cape Clear Server, to continue your installation, consult the appropriate section:

Deploying Cape Clear in the Default JBoss Container

The following procedure describes the installation steps that you follow if you have selected the Use default container (JBoss) option:

  1. Click Next. If you have selected to use the default container (JBoss), the installer prompts you for the location of the Java Development Kit (JDK) installation on your system. Browse to the location of your JDK, for example, C:\Program Files\Java\jdk1.5.0_08, as shown below. On Windows and Solaris, the product supports Sun Java Development Kit (JDK) 1.4.2_10 and 1.5.


    Choosing your JDK location

    Figure 5. Choosing your JDK location

  2. Click Next. The installer prompts you to modify, if necessary, the HTTP and HTTPS port configuration for your JBoss application server, as shown below. The port numbers should match those of the JBoss container into which Cape Clear Server is to be deployed and should not already be in use.

    For example, if you are using Oracle as your Cape Clear Server database later on, ensure that the HTTP listener port for JBoss does not conflict with the default number that is already in use by Oracle.


    Specifying port numbers

    Figure 6. Specifying port numbers

    Before proceeding, confirm that the ports you want to use are not being used by other applications.

  3. Click Next. As shown in the following figure, the installer prompts you to specify port numbers for the JBoss installation. These port numbers should not already be in use.


    Specifying port numbers for use with the JBoss application server

    Figure 7. Specifying port numbers for use with the JBoss application server

    Note

    The Cape Clear Clustering UDP Port indicates the port number for the User Datagram Protocol (UDP) transport when running Cape Clear Server in clustered mode on a JBoss server. This port is used for communication between all Cape Clear Server instances in a cluster. This value is set in $CAPE_HOME/Server/jboss-4.0.2/server/all/deploy/ccx.war/WEB-INF/conf/jgroups.protocol.stack.txt. The default is 45566.

  4. Click Next. As shown in the following figure, the installer prompts you to specify a host name or IP address for the computer on which you are installing Cape Clear Server. This information is used to enable clients to communicate with your Web services. If you specify localhost, Web services that you generate will be available on the local machine only and will not be accessible over a network. The default value is the machine name, which ensures that the machine is accessible. You can also specify the IP address of the machine as an alternative.


    Indicating the host name or IP address for your computer

    Figure 8. Indicating the host name or IP address for your computer

  5. Click Next. As shown in the following figure, the installer prompts you to specify an admin user name and password, and then confirm the password by re-entering the password. When connecting to the server and logging in to the Cape Clear Manager and Orchestrator Web consoles, you will use the admin user name and the password that you specify here. The default user name is admin.


    Setting a password for the admin user

    Figure 9. Setting a password for the admin user

  6. Click Next. Select which of the optional Cape Clear Server modules you want to install.


    Selecting optional server modules to install

    Figure 10. Selecting optional server modules to install

    The following options are provided.

    • WS-Reliable Messaging: WS-ReliableMessaging (WS-RM) is a standard protocol that enables messages to be delivered reliably between distributed applications in case of software component, system, or network failures. The Cape Clear Server implementation of this protocol for enables WS-RM for SOAP messages transmitted over HTTP.

    • Clustered Server: which installs the Cape Clear Server instance in clustered mode.

  7. If you did not select the the Clustered Server option, skip the next step and continue to 8. If you selected the Clustered Server option, click Next. The Cluster Configuration page is displayed, which enables you to specify the following details:

    • Join cluster on startup: indicates whether the Cape Clear Server should join the cluster when the server starts.

    • Install in HA configuration: indicates whether to install Cape Clear Server to use a HA-JMS configuration. If your applications will use JMS to communicate, you need to set up your transports to use High-Availablity (HA) JMS. Selecting this option configures the HA-JMS "all" configuration bundled with the JBoss distribution, as described in “Configuring JBoss HA-JMS Queues”.

    • Cluster name: indicates the name for the group of clustered servers. The default value is cc-cluster.

    • JBoss Clustering UDP Port: indicates the port number to use for the UDP transport, also known as IP multicast, for each JBoss server in the group of clustered servers. This value is set in $CAPE_HOME/Server/jboss-4.0.2/conf/server/all/deploy/cluster-service.xml. The default value is 45577. For more details on UDP configuration properties in JBoss, see the JBoss documentation at:

      http://docs.jboss.com/jbossas/guides/clusteringguide/r2/en/html_single/#jbosscache-jgroups-transport-udp

      Note

      The JBoss Clustering UDP Port number should not match the Cape Clear Clustering UDP Port number. It is good practice to configure separate UDP ports for communication between JBoss servers in a clustered environment, for example, in the case of a HA-JMS setup, and for Cape Clear Server clustering-specific requirements.

    • JBoss Servlet Container Cluster UDP Port: indicates the port number to use for each instance of the Tomcat Servlet container in the group of clustered servers. This value is set in $CAPE_HOME/jboss-4.0.2/conf/server/all/deploy/tc5-cluster-service.xml. The default value is 45588.

    For more details and operational guidelines on setting up a Cape Clear Server cluster, see “Setting Up a Cluster”.


    Specifying cluster configuration details

    Figure 11. Specifying cluster configuration details

  8. Click Next. Specify the location where you have copied your Cape Clear runtime licenses, for example, C:\Licenses.


    Specifying the location of your Cape Clear licenses

    Figure 12. Specifying the location of your Cape Clear licenses

  9. Click Next. Select one of the following databases to store message and process state: Oracle, SQL Server, MySQL, or HSQL. HSQL, which is bundled with Cape Clear Server, is recommended for development only and not for production or testing environments.

    Note

    If you selected the Clustered Server optional server module, the HSQL option is not available.


    Selecting the type of database

    Figure 13. Selecting the type of database

  10. Click Next. Specify the database configuration details that will be used by the Cape Clear Server message store and the optional orchestration module (if selected) to connect to your database, as shown below. You should note the database configuration details that you specify for use later when you are setting up your database. For more details on post-installation steps, refer to “Completing Your Installation”.

    If you choose HSQL (Development only) as the database type, no additional set-up of the database is required; that is, unless you change the default connection details, in which case, you will need to edit these values in the $CAPE_HOME/Server/jboss-4.0.2/server/default/deploy/ccx.war/WEB-INF/data/hibernatepersistencedb script. To avoid this configuration step, where possible, do not change the default HSQL settings.


    Specifying the Server database configuration details

    Figure 14. Specifying the Server database configuration details

  11. Click Next. Specify the JMX RMI registry port for JMX management and monitoring, as shown below.


    Specifying the JMX management and monitoring configuration details

    Figure 15. Specifying the JMX management and monitoring configuration details

  12. Click Next. If you have selected to install the optional WS-RM module, you are prompted to select the type of database to be used, either an Oracle or MySQL database, or "in memory". The In Memory (Development only) option means that no database is used, which may be useful if you want to develop and test with WS-RM without setting up a database. In this case, the WS-RM state is not reliable, that is, it is not preserved when Cape Clear Server is shut down.

    Note

    Microsoft SQL Server 2005 is also supported as a WS-RM database configuration, however, because it is not yet available as a WS-RM database option in the installer, you must configure it manually after installation. In this installer step, if you plan to use SQL Server, select the In Memory (Development only) option. Refer to the section “Configuring Microsoft SQL Server 2005 for WS-RM” for the manual configuration steps.


    Specifying the type of WS-RM database

    Figure 16. Specifying the type of WS-RM database

  13. Click Next. Again, if you have selected to install the optional WS-Reliable Messaging module, you are prompted to provide your WS-RM database details, as shown below.

    If you plan to use SQL Server, accept the default settings.


    Specifying the WS-RM database details

    Figure 17. Specifying the WS-RM database details

  14. Click Next. The installation progress panel is displayed, as shown below. Click Details, then select the appropriate page to show either the installation log or error log during installation.


    Viewing installation progress

    Figure 18. Viewing installation progress

  15. Click Install. The installer adds Cape Clear Server to your system and indicates that the installation is complete, as shown below.


    Message box indicating that installation is complete

    Figure 19. Message box indicating that installation is complete

  16. A message is displayed that indicates that the installation is complete. Click OK.


    Notification of installation completion

    Figure 20. Notification of installation completion

  17. Click Exit. The installer closes.

To complete your JBoss installation, refer to “Completing Your JBoss Configuration”.

Deploying Cape Clear in a Tomcat 5.5 Container

Cape Clear Server can be deployed into an existing installation of Tomcat 5.5. The following procedure describes the installation steps that you follow for Tomcat 5.5 if you have selected the Use alternative container option (not the bundled JBoss installation):

  1. Click Next. If you have selected to deploy Cape Clear Server in an alternative container (not the bundled JBoss installation), the installer prompts you to select the pre-existing server's name. If you selected Tomcat 5.5, continue to the next step.


    Selecting the Tomcat container

    Figure 21. Selecting the Tomcat container

  2. Click Next. The installer prompts you to browse to the home directory of your Tomcat installation.


    Selecting the location of a pre-existing Tomcat installation

    Figure 22. Selecting the location of a pre-existing Tomcat installation

  3. The installer prompts you for the location of the Java Development Kit (JDK) installation on your system, as shown below. Browse to the location of your JDK, for example, C:\Program Files\Java\jdk1.5.0_04. On Windows and Solaris, the product supports Sun Java Development Kit (JDK) version 1.5.0_04 or later versions of 1.5.


    Choosing your JDK location

    Figure 23. Choosing your JDK location

  4. Click Next. The installer prompts you to modify, if necessary, the port configuration for Cape Clear Server, as shown below. The port numbers should match those used by the Tomcat installation and should not already be in use. If the Tomcat installation is not currently configured with an HTTPS port (which is the default case for a new installation), the pre-specified port number on the following screen can be safely used.


    Specifying Tomcat port numbers

    Figure 24. Specifying Tomcat port numbers

  5. Click Next. As shown in the following figure, the installer prompts you to specify a host name or IP address associated with the Tomcat installation. This information is used to enable clients to communicate with your Web services. If you specify localhost, Web services that you generate will be available on the local machine only and will not be accessible over a network. The default value is the machine name, which ensures that the machine is accessible. You can also specify the IP address of the machine as an alternative.


    Specifying the Tomcat host name

    Figure 25. Specifying the Tomcat host name

  6. Click Next. As shown in the following figure, the installer prompts you to specify an admin user name and password, and then confirm the password. When connecting to the server and logging in to the Cape Clear Manager and Orchestrator Web consoles, you will use the admin user name and the password that you specify here. The default user name is admin.


    Setting a password for the admin user

    Figure 26. Setting a password for the admin user

  7. Click Next. Select which of the optional Cape Clear modules you wish to install. The following steps assume that the following optional Cape Clear modules will be used:

    The following options are provided.

    • WS-Reliable Messaging: WS-ReliableMessaging (WS-RM) is a standard protocol that enables messages to be delivered reliably between distributed applications in case of software component, system, or network failures. The Cape Clear Server implementation of this protocol for enables WS-RM for SOAP messages transmitted over HTTP.


    Selecting the optional server modules to install

    Figure 27. Selecting the optional server modules to install

  8. Click Next. Specify the location where you have copied your Cape Clear runtime licenses, for example, C:\Licenses.


    Specifying the location of your Cape Clear licenses

    Figure 28. Specifying the location of your Cape Clear licenses

  9. Click Next. Select the Server database to be used, either the MySQL or HSQL database, as shown below. Use the HSQL database for development purposes only.


    Selecting the type of database

    Figure 29. Selecting the type of database

  10. Click Next. Specify the configuration details for the Server database, as shown below. You should note the database configuration details that you specify for use later when you are setting up your database.


    Specifying the configuration details of the Server database

    Figure 30. Specifying the configuration details of the Server database

  11. Click Next. Specify the configuration details for the Management and Monitoring module, that is, the port number to be used by Tomcat for its JMX RMI registry, as shown below.


    Specifying the JMX management and monitoring configuration details

    Figure 31. Specifying the JMX management and monitoring configuration details

  12. Click Next. If you have selected to install the optional WS-ReliableMessaging module, you are prompted to select the type of database to be used, either MySQL or "in memory". The In Memory (Development only) option means that no database is used, which may be useful if you want to develop and test with WS-RM without setting up a database. In this case, the WS-RM state is not reliable, that is, it is not preserved when the machine is switched off.


    Selecting the type of WS-RM database

    Figure 32. Selecting the type of WS-RM database

  13. Click Next. You are prompted to provide your WS-RM database details, as shown below.


    Specifying the WS-RM database details

    Figure 33. Specifying the WS-RM database details

  14. Click Next. The installation progress panel is displayed, as shown below. Click Details, then select the appropriate page to show either the installation log or error log during installation.


    Viewing installation progress

    Figure 34. Viewing installation progress

  15. Click Install. The installer adds Cape Clear Server to your system and indicates that the installation is complete, as shown below.


    Message box indicating that installation is complete

    Figure 35. Message box indicating that installation is complete

  16. A message is displayed that indicates that the installation is complete. Click OK.


    Notification of installation completion

    Figure 36. Notification of installation completion

  17. Click Exit. The installer closes.

Starting Tomcat

The Cape Clear Server installation includes a script to start Tomcat with the required environment variables, as follows. For Windows, the script is located at: $CAPE_HOME/Server/bin/startup.bat

For UNIX, the script is located at: $CAPE_HOME/Server/bin/startup.sh

Alternatively, you can choose to set the environment variables manually. To do so, follow the instructions in the following two topics in the section “Completing Your Tomcat Configuration”:

Deploying Cape Clear Server in a WebLogic 9.1 or 9.2 Container

Cape Clear Server can be deployed into an existing installation of WebLogic 9.1 or 9.2.

  1. Click Next. If you have selected to deploy Cape Clear Server in an alternative container (not the bundled JBoss installation), the installer prompts you to select the pre-existing server's name. If you selected WebLogic 9.1/9.2, continue to the next step.


    Selecting the WebLogic container

    Figure 37. Selecting the WebLogic container

  2. Click Next. The installer prompts you to browse to the home directory of your WebLogic installation.


    Selecting the location of a pre-existing WebLogic installation

    Figure 38. Selecting the location of a pre-existing WebLogic installation

  3. Click Next. The installer prompts you for the location of the WebLogic domain into which Cape Clear Server is to be deployed, as shown below.


    Selecting the WebLogic domain directory

    Figure 39. Selecting the WebLogic domain directory

  4. Click Next. The installer prompts you to modify, if necessary, the port configuration for Cape Clear Server, as shown below. The port numbers should match those used by the WebLogic installation and should not already be in use. If the WebLogic installation is not currently configured with an HTTPS port (which is the default case for a new installation), the pre-specified port number on the following screen can be safely used.


    Specifying WebLogic port numbers

    Figure 40. Specifying WebLogic port numbers

  5. Click Next. As shown in the following figure, the installer prompts you to specify a host name or IP address associated with the WebLogic installation. This information is used to enable clients to communicate with your Web services. If you specify localhost, Web services that you generate will be available on the local machine only and will not be accessible over a network. The default value is the machine name, which ensures that the machine is accessible. You can also specify the IP address of the machine as an alternative.


    Specifying the WebLogic host name

    Figure 41. Specifying the WebLogic host name

  6. Click Next. As shown in the following figure, the installer prompts you to specify an admin user name and password, and then confirm the password. When connecting to the server and logging in to the Cape Clear Manager and Orchestrator Web consoles, you will use the admin user name and the password that you specify here. The default user name is admin.


    Setting a password for the admin user

    Figure 42. Setting a password for the admin user

  7. Click Next. If you want to install the Clustered Server optional module, which installs Cape Clear Server in WebLogic in clustered mode, select the Clustered Server check box.


    Selecting optional Server modules for WebLogic

    Figure 43. Selecting optional Server modules for WebLogic

  8. If you did not select the Clustered Server option, skip the next step and continue to 9. If you selected the Clustered Server option, click Next. The Cluster Configuration page is displayed, which enables you to specify the following details:

    • Cape Clear Clustering UDP Port: indicates the port number for the User Datagram Protocol (UDP) transport when running Cape Clear Server in clustered mode in a WebLogic server. This port is used for communication between all Cape Clear Server instances in a cluster. This value is set in $CAPECLEAR_DOMAIN_HOME/capeclear/server/WEB-INF/conf/jgroups.protocol.stack.txt. The default is 45566.

    • Join cluster on startup: indicates whether the Cape Clear Server should join the cluster when the server starts.

    • Cluster name: indicates the name for the group of clustered servers. The default value is cc-cluster.
      For more details and operational guidelines on setting up a Cape Clear Server cluster, see “Setting Up a Cluster”.


    Specifying cluster configuration details

    Figure 44. Specifying cluster configuration details

  9. Click Next. Specify the location where you have copied your Cape Clear runtime licenses, for example, C:\Licenses.


    Specifying the location of your Cape Clear licenses

    Figure 45. Specifying the location of your Cape Clear licenses

  10. Click Next. Select one of the following databases to store message and process state: Oracle, SQL Server, or MySQL.


    Selecting the type of Server database

    Figure 46. Selecting the type of Server database

  11. Click Next. Specify the JNDI DataSource for the database. You can specify the remaining connection details as a post-installation step when configuring your WebLogic application server (see “Creating a WebLogic JDBC DataSource for the Cape Clear Server Database”).


    Specifying the configuration details of the Server database

    Figure 47. Specifying the configuration details of the Server database

  12. Click Next. The installation progress panel is displayed, as shown below. Click Details, then select the appropriate page to show either the installation log or error log during installation.


    Viewing installation progress

    Figure 48. Viewing installation progress

  13. Click Install. The installer adds Cape Clear to your system and indicates that the installation is complete, as shown below.


    Message box indicating that installation is complete

    Figure 49. Message box indicating that installation is complete

  14. A message is displayed that indicates that the installation is complete. Click OK.


    Notification of installation completion

    Figure 50. Notification of installation completion

  15. Click Exit. The installer closes.

To complete your WebLogic installation, refer to “Completing Your WebLogic 9.1 Configuration”

Deploying Cape Clear in a WebSphere 6.0 or 6.1 Container

  1. Click Next. If you have selected to deploy Cape Clear Server in an alternative container (not the bundled JBoss installation), the installer prompts you to select the pre-existing server's name. If you selected WebSphere 6.0/6.1, continue to the next step.


    Selecting the WebSphere container

    Figure 51. Selecting the WebSphere container

  2. Click Next. Select the WebSphere version, as shown in the following figure:


    Selecting the WebSphere version

    Figure 52. Selecting the WebSphere version

  3. Click Next. Specify the HTTP and HTTPS ports for the WebSphere profile you are using. The "default" profile ports (9080 and 9443) are pre-specified. These ports must match the ones configured in the specific WebSphere profile being used for the deployment and should and should not already be in use.


    Specifying WebSphere port numbers

    Figure 53. Specifying WebSphere port numbers

  4. Click Next. As shown in the following figure, the installer prompts you to specify a host name or IP address for the computer on which you are installing Cape Clear. This information is used to enable clients to communicate with your Web services. If you specify localhost, Web services that you generate will be available on the local machine only and will not be accessible over a network. Otherwise, specify a host or IP address.


    Indicating the host name or IP address for your computer

    Figure 54. Indicating the host name or IP address for your computer

  5. Click Next. As shown in the following figure, the installer prompts you to specify an admin user name and password, and then confirm the password. When connecting to the server and logging in to the Cape Clear Manager and Orchestrator Web consoles, you will use the admin user name and the password that you specify here. The default user name is admin.

    6. Setting a password for the admin user

    Figure 55. Setting a password for the admin user

  6. Click Next. If you want to install the Clustered Server optional module, which installs Cape Clear Server in WebLogic in clustered mode, select the Clustered Server check box.

     


    Selecting the server module to be installed for WebSphere

    Figure 56 Selecting the server module to be installed for WebSphere

  7. If you did not select the Clustered Server option, skip the next step and continue to 8. If you selected the Clustered Server option, click Next. The Cluster Configuration page is displayed, which enables you to specify the following details:

    • Cape Clear Clustering UDP Port: indicates the port number for the User Datagram Protocol (UDP) transport when running Cape Clear Server in clustered mode in a WebSphere server. This port is used for communication between all Cape Clear Server instances in a cluster. This value is set in server.war/WEB-INF/conf/jgroups.protocol.stack.txt. The default is 45566.

    • Join cluster on startup: indicates whether the Cape Clear Server should join the cluster when the server starts.

    • Cluster name: indicates the name for the group of clustered servers. The default value is cc-cluster.

    For more details and operational guidelines on setting up a Cape Clear Server cluster, see “Setting Up a Cluster”.

    Specifying cluster configuration details

    Figure 57. Specifying cluster configuration details

  8. Click Next. Specify the location where you have copied your Cape Clear runtime licenses, for example, C:\Licenses.


    Specifying the location of your Cape Clear licenses

    Figure 58. Specifying the location of your Cape Clear licenses

  9. Click Next. Select one of the following databases to store message and process state: Oracle, SQL Server, or MySQL.


    Selecting the database for WebSphere

    Figure 59. Selecting the database for WebSphere

  10. Click Next. Click Select, then browse to the WebSphere Application Server directory, where Cape Clear Server is to be deployed, for example, C:\Program Files\IBM\WebSphere\AppServer1.


    Selecting the WebSphere application server directory

    Figure 60. Selecting the WebSphere application server directory

  11. Click Next. Select the Create Profile check box to create a new Cape Clear profile. Otherwise, to deploy into an existing profile, do not select this check box.


    Creating the profile

    Figure 61. Creating the profile

  12. Click Next. If you selected the Create Profile check box, the Select the WebSphere profile location, admin port and driver screen is displayed, as shown in the following figure:


    Creating the profile

    Figure 62. Creating the profile

    Specify the WebSphere profile details, then click Next. Click Yes when prompted to create the CapeClearProfile directory if it does not exist.

  13. Specify the configuration details for the database, as shown below. You can specify the remaining connection details as a post-installation step when configuring your WebSphere Application Server (see “Setting Up JDBC and BPEL/WS-RM DataSources Using the Oracle Database”).


    Specifying the configuration details of the Server database

    Figure 63 Specifying the configuration details of the Server database

  14. Click Next. The installation progress panel is displayed, as shown below. Click Details, then select the appropriate page to show either the installation log or error log during installation.


    Viewing installation progress

    Figure 64. Viewing installation progress

  15. Click Install. The installer adds Cape Clear Server to your system and indicates that the installation is complete, as shown below.


    Message box indicating that installation is complete

    Figure 65. Message box indicating that installation is complete

  16. A message is displayed that indicates that the installation is complete. Click OK.


    Notification of installation completion

    Figure 66. Notification of installation completion

  17. Click Exit. The installer closes.

To complete your WebSphere installation, refer to “Completing Your WebSphere Configuration”.

< Back Cape Clear 7.0.1 Server Installation Guide >

 


© 2007, Cape Clear Software Inc