Preview only show first 10 pages with watermark. For full document please download

Installing On Websphere Application Server

   EMBED

Share

Transcript

| 167 Chapter 12 Installing on WebSphere Application Server This chapter provides instructions for performing a new installation of TIBCO Collaborative Information Manager on the WebSphere Application Server in a non-clustered environment. Topics • Verifying Prerequisites, page 168 • Configuring the CIM Application for WebSphere Application Server, page 169 • Tuning the Performance of the WebSphere Application Server, page 175 • Setting up Security, page 179 • Troubleshooting Websphere Application Server Problems, page 182 TIBCO Collaborative Information Manager Installation and Configuration Guide 168 | Chapter 12 Installing on WebSphere Application Server Verifying Prerequisites • Ensure that CIM is installed. • Ensure that your specified database is up and running. • Ensure that JMS is up and running. • Ensure that the Websphere Application Server is installed. Deploying CIM on WebSphere Application Server Refer to the appropriate installation documentation supplied with the WebSphere Application server for installation instructions. The administration server needs to be running in order to install and configure TIBCO Collaborative Information Manager. TIBCO Collaborative Information Manager Installation and Configuration Guide Configuring the CIM Application for WebSphere Application Server 169 | Configuring the CIM Application for WebSphere Application Server The following tasks are involved for configuring TIBCO Collaborative Information Manager on the WebSphere Application Server: • Creating a Profile on the Application Server • Setting up WAS Properties for CIM • Configuring Database Drivers and Data Source • Configurator Settings Creating a Profile on the Application Server 1. Create a Profile other than the default one using the Profile creation wizard. 2. Start the Administration Server. a. Go to the $WAS_HOME/profiles//bin directory. b. Enter the following command: ./startServer.sh server1 Setting up WAS Properties for CIM In case of clustered setups, it is recommended that you: — Increase the poolsize per server to 100. — Increase the transaction timeout of the application server to 36000. 1. Login to the Administrative console to configure the properties. 2. In the left panel, expand Servers, Server Types and click WebSphere application servers; in the right panel, click the server1 link. 3. In the right panel, under Server-specific Application Settings: — Select Class loading mode as Classes loaded with local class loader first (parent last). — Select Classloader policy as Multiple. — Click Apply. 4. Under the Container Settings Section, expand Container Services and click Transaction Service. TIBCO Collaborative Information Manager Installation and Configuration Guide 170 | Chapter 12 Installing on WebSphere Application Server 5. Enter the following values and click OK. Total transaction lifetime timeout: 36000 Client inactivity timeout: 7200 Heuristic retry limit: 0 Heuristic retry wait: 0 Heuristic completion direction: ROLLBACK 6. In Container Settings, expand Container Services and click ORB service. Select the Pass by reference checkbox. Click OK followed by Save as described above for other properties. 7. In the left panel, click Environment > WebSphere variables. Select Node=,Server=server1 from the Scope drop down in the right pane. 8. Add the following environment variable entries (by clicking the New button): DISPLAY LD_LIBRARY_PATH MQ_COMMON_DIR MQ_CONFIG_FILE DB2_HOME or ORACLE_HOME DB2INSTANCE ORACLE_JDBC_DRIVER_PATH MQ_HOME MQ_LOG PATH NODE_ID Click Save. 9. Under WebSphere application servers > server1 >Server Infrastructure, expand Java and Process Management and click the Process definition link. Click Java Virtual Machine under Additional Properties. TIBCO Collaborative Information Manager Installation and Configuration Guide Configuring the CIM Application for WebSphere Application Server 171 | Generic JVM Arguments Add Generic JVM arguments as follows: (For readability, each entry is listed here on a separate line below. Enter these in a single line, separated by a single space.) -DLANG=en_US.UTF-8 -DNODE_ID={NODE_ID} -Dclient.encoding.override=UTF-8 -DMQ_HOME=${MQ_HOME} -DMQ_LOG=${MQ_LOG} -DMQ_CONFIG_FILE=${MQ_HOME}/config/ConfigValues.xml -DMQ_COMMON_DIR=${MQ_COMMON_DIR} -DPATH=${PATH} -DOS= -DDISPLAY=:1.0 -Djavax.xml.transform.TransformerFactory=org.apache.xalan.pr ocessor.TransformerFactoryImpl Additionally, add JVM arguments related to Oracle Coherence caching (since CIM uses Coherence by default). -Dtangosol.coherence.cacheconfig=${MQ_HOME}/config/coherence -client-cache-config.xml -Dtangosol.coherence.override=${MQ_HOME}/config/tangosol-coh erence-override.xml -Dtangosol.coherence.log=${MQ_LOG}/tangosol.log -Dtangosol.coherence.wka1=<> -Dtangosol.coherence.ttl=0 • If using the DB2 database, add -DDB2INSTANCE=${DB2INSTANCE} • If using Oracle, add -DORACLE_HOME=${ORACLE_HOME} 10. Set Initial heap size and Maximum heap size (to 1024 at minimum). 11. Click OK. Click Save on the menu bar at the top of the screen. Click Save again. Configuring Database Drivers and Data Source 1. In the left panel, select Resources > JDBC> JDBC providers. TIBCO Collaborative Information Manager Installation and Configuration Guide 172 | Chapter 12 Installing on WebSphere Application Server 2. In the right panel select Node='nodename', Server=server1 from the Scope dropdown list. 3. Click the New button. a. Select the Database type as Oracle or DB2, Provider type as Oracle JDBC Driver or DB2 Using IBM JCC Driver, Implementation type as Connection pool data source, Name and Description. Click Next. b. Provide the classpath. In case of Oracle, provide the location to ojdbc6.jar. In case of DB2, provide the location to db2jcc4.jar. Click Next. c. Click Finish. Click Save. 4. In the left pane, expand Security, select Global security. 5. In the right pane, expand Java Authentication and Authorization Service, click J2C authentication data. Click the New button. 6. Provide the database Alias, User ID, and Password. Click Apply and OK. 7. Select Resources > JDBC > Data sources. Click the New button. 8. Provide the Data source name and JNDI name. Click Next. 9. Select whether to Create a new JDBC provider or to Select an existing JDBC provider. A JDBC Provider was created in Step 3, so you can use the existing one. 10. (Oracle only) Provide the Connection URL. For example: jdbc:oracle:thin:@ or :: . (DB2 only) Provide Driver type, Database name, Server name, and Port number. Click Next. 11. (Oracle only) Select the appropriate data store helper class name (Oracle11g data store helper). Click Next. 12. Complete the security setup. Select Component-managed authenication alias as , Mapping-configuration alias as DefaultPrincipalMapping, and Container-managed authentication alias as . 13. Click Next and then click Finish. Click Save. TIBCO Collaborative Information Manager Installation and Configuration Guide Configuring the CIM Application for WebSphere Application Server 173 | 14. Select the Data source Name and test the connection by clicking Test Connection, you should see a Connection Successful message. Go to Data sources > > Connection pool properties, set the Maximum connections to 50 and the connection timeout to 7200. Locks on DB2 To avoid locks on DB2: 1. Expand Resources > JDBC > JDBC Providers. 2. Select the Configured JDBC Provider. 3. Select Data sources (on the right). 4. Click the name of the Data source for which you want to customize the default Isolation level. 5. Under Additional Properties (on the right), click Custom properties. Click the webSphereDefaultIsolationLevel property and set the value to 2. 6. Click OK, and save the configuration. 7. Restart the Application Server to make the custom property active. Configurator Settings Before starting the CIM application, you need to configure the port numbers (JNDI port), database information and security provider (IBM). This is done through the Configurator. Deploying CIM on Websphere Application Server 1. In the left panel, click Applications > New Application. 2. In the right panel, click New Enterprise Application. 3. Browse to the path of the ECM.ear file (located in $MQ_HOME) and click Next. 4. Select the Detailed installation option and click Next. 5. Click Continue on any Application Security Warnings. 6. Click Next on the Select installation options dialog. 7. Click Next on the Map modules to server, verify that Cluster and servers is properly selected. 8. Click Next on Provide JSP reloading options for Web modules. TIBCO Collaborative Information Manager Installation and Configuration Guide 174 | Chapter 12 Installing on WebSphere Application Server 9. Click Next on Map shared libraries. 10. Click Next on Map shared library relationships. 11. Click Next on Provide JNDI names for beans; verify that all JNDI names are pre-populated. 12. Click Next on Map virtual hosts for Web modules. 13. Click Next on Map context roots for Web modules. 14. Click Next on Ensure all unprotected 2.x methods have the correct level of protection. 15. You will see the installation options summary. Click Finish. 16. After installing click Save. After successful startup, you will get a confirmation message in the log file located in WAS_HOME/logs. You can also check if the application is up through the following URL: http://:/eml/Login For example: http://localhost:9081/eml/Login Setting the class loader policy to Parent Last 1. In the left pane, go to Servers > Server Types > WebSphere application servers. 2. In the right pane, under Application servers, click . 3. You will see the Configuration tab, General Properties. — Click Installed applications under Applications, then click the installed application, for example, ECM. — Under Detail Properties, click Class loading and update detection. 4. On the Class loader screen General Properties, select Classes loaded with local class loader first (parent last) under Class Loader order. 5. Select Single class loader for application under WAR class loader policy. 6. Click Apply and OK. TIBCO Collaborative Information Manager Installation and Configuration Guide Tuning the Performance of the WebSphere Application Server 175 | Tuning the Performance of the WebSphere Application Server To improve the WebSphere application server performance, make some or all of the changes recommended below: Modifying Heap Settings To ensure optimal memory allocation, assign minimum (referred as the initial heap size on the WAS Configuration GUI) and maximum heap settings as follows: • Go to Servers > Server Types > WebSphere application servers > • Under Server Infrastructure, expand Java and Process Management and click Process definition, then click Java Virtual Machine under Additional Properties. • Assign Maximum heap size to as high as possible up to 1.5 GB. Note that you may have to change the operating system settings if you assign more than 1024 MB to heap. • Set the initial (minimum) and maximum heap size to the same value. • Go to Servers > Server Types > WebSphere application servers > • Under Server Infrastructure, expand Java and Process Management and click Process definition, then click Java Virtual Machine under Additional Properties. • Ensure that the Disable JIT option is not selected. JIT Setting Tuning Web Container Number of Threads The default number of threads may have to be changed for Linux OS. Do not change the setting for other OS. To change the number of threads, in the left pane: • Select Servers > Server Types > Websphere application servers. TIBCO Collaborative Information Manager Installation and Configuration Guide 176 | Chapter 12 Installing on WebSphere Application Server • Click in the right pane, then click Thread pools under Additional Properties. • Click WebContainer. • For the Linux OS only, change Maximum Size (threads) to 25. Servlet Caching It is recommended you disable servlet caching. TIBCO Collaborative Information Manager does not require outputs of servlets be cached, as it does not reuse this output. If caching is enabled, it will consume additional memory. To disable servlet caching: • Go to Servers > Server Types > Websphere application servers > • Under Container Settings expand Web Container Settings and click Web container. • Clear the Enable servlet caching checkbox. Cache Size for EJB The default cache size of 2054 is sufficient for TIBCO Collaborative Information Manager installations. It is recommended that you do not change the EJB cache size unless requested by TIBCO Support. If you need to change it, select: • Servers > Server Types > Websphere application servers > • Under Container Settings, expand EJB Container Settings and click EJB container. • Click EJB cache settings under Additional Properties. Changing the Default ORB Threads Setting For Linux OS, you need to change the ORB thread pool. The recommended value is 25. Do not change this value for other operating systems. • Go to Servers > Server Types > Websphere application servers > • Under Container Settings, expand Container Services and click ORB service. • Click ORB.thread.pool under Thread Pool Settings. • Set the Maximum size to 25. TIBCO Collaborative Information Manager Installation and Configuration Guide Tuning the Performance of the WebSphere Application Server 177 | JVM Tuning The following tuning is recommended for optimal performance of JVM. You can change the JVM settings as follows: Select Servers > Application Server > > Server Infrastructure > Java and Process Management > Process definition > Java Virtual Machine > Generic JVM Arguments. For 64 bit non Windows machines, in the JVM settings, you can specify: -d32 or -d64 This specifies whether the program is to be run in a 32-bit or 64-bit environment if available. Currently, only the Java HotSpot Server VM supports 64-bit operation, and the "-server" option is implicit with the use of -d64. If neither -d32 nor -d64 is specified, the default is to run in a 32-bit environment, except for 64-bit only systems. For Windows this option is not available, and the default mode id 32 bit JVM. Refer the JAVA documentation for more details. Permanent Memory Size if using Sun JVM Set the maximum permanent memory size to control garbage collection behavior. The default size is 128 MB which is adequate for most usage. On request, you may change this size to one forth of the max heap size. Ensure that you have adequate free RAM available before changing this value, as this memory must be available in addition to the maximum heap size allocated. -XX:MaxPermSize=256M JVM mode It is recommended to set the JVM to server mode (-server ) Tuning Connection Pool The default prepared statement cache size is 10. Set it to 0. An incorrect setting may result in a TransactionRolledback exception. This setting is Windows specific. • Select Resources > JDBC > JDBC providers > Data sources • Select the Data source; click WebSphere Application Server data source properties under Additional Properties. TIBCO Collaborative Information Manager Installation and Configuration Guide 178 | Chapter 12 Installing on WebSphere Application Server • Set the Statement cache size to 10. The recommended minimum pool size is 10 and maximum is 20. TIBCO Collaborative Information Manager Installation and Configuration Guide Setting up Security 179 | Setting up Security Enabling Cookies TIBCO Collaborative Information Manager uses a cookie to keep track of menus selected by the user. The business sensitive information stored in the cookies should be kept confidential and sent only over a secure link. Use the instructions in this section to make cookies secure by requiring them to be transmitted only over secure links and to the appropriate location. 1. Go to Admin Console of WebSphere Application Server. 2. From the left pane, select Servers >Server Types > WebSphere application servers >; select the in the right pane. 3. In the right pane, scroll down, under Container Settings expand Web Container Settings, click Web container. Under Additional Properties click Session management, click Enable cookies. 4. In the "JSESSIONID" cookie properties, enter the domain and path for which session tracking cookie should be sent. 5. Select the Restrict cookies to HTTPS sessions check box to restrict session cookies to HTTPS sessions. Enabling URL rewriting If your installation does not support cookies, you need to enable URL rewriting. TIBCO Collaborative Information Manager recommends that cookies be enabled. • Select Servers > Server Types > WebSphere application servers; select the in the right pane. Click Session management under Container Settings. • If Cookies are not supported, clear the Enable cookies check box and select the Enable URL rewriting check box. • If Cookies are supported, select the Enable cookies check box and clear the Enable URL rewriting check box. Setting up SSL SSL needs to be setup in order to access the application through a browser over the HTTPS protocol. The following steps are required to setup SSL: 1. Login to the WebSphere Application Server Admin Console. TIBCO Collaborative Information Manager Installation and Configuration Guide 180 | Chapter 12 Installing on WebSphere Application Server 2. In the left panel, click Servers > Server Types > Websphere application servers. Click the in the right pane (the server for which you want to enable SSL. For example, server1). 3. In the right panel, under Container Settings, expand Web Container Settings, click Web container transport chains. 4. The following screen displays the various ports on your server and also provides information on whether SSL is enabled. If SSL is not enabled, you can enable it now. 5. Click New. The Create New Transport Chain page is displayed. Provide the Transport chain name - for example, CIMTransportChain2. Provide the Transport chain template. For SSL, select WebContainer-Secure(templates/chains|webcontainer-chains.xml#Chain_2 ) from the dropdown list. Click Next. 6. Provide the Port name (for example, CIMTransportChain2), Host (for example *), and Port (for example, 9082. Use any unused port number). Click Next. 7. A summary of your selections is displayed. To change any selections, click Previous. 8. Click Finish. The SSL Enabled column for the newly created TransportChain should display Enabled for the specified port. Click the Save link in the Messages box on the top. Click Save on the following screen. 9. In the left panel, expand Environment, click Virtual Hosts. In the right pane select the virtual host name. 10. Under Additional Properties, click Host Aliases and then click New. 11. Under General Properties, enter the Host Name as * and enter the Port number as 9082 (or any other unused port number). 12. Click OK and save the configuration. 13. Restart the server. Browse the application using the https protocol over the listening port. Certificates (only applies if using GDSN software edition) To communicate with 1Sync securely, you may need to download their certificates and insert them into your trusted certificate store if they are not present already. To do this: 1. Open Internet Explorer and type the secure URL of the server. For example, https://preprod.1sync.org. TIBCO Collaborative Information Manager Installation and Configuration Guide Setting up Security 181 | 2. If your computer does not have the certificates in its keystore, a security alert appears. This alert warns you that the certificate is not verified and allows you to view the certificate. Click View Certificate to view the certificate. The Certificate dialog box opens. 3. Click on the Certification Path tab. Each certificate listed must be copied to a file. To copy a certificate: a. Select the Details tab. b. Click Copy to File. The Certificate Export Wizard opens and guides you through the steps for copying certificates, certificate trust lists, and certification revocation lists from a certification store to your disk. c. Choose the Base-64 encoded X.509 (.CER) format and click Next. d. Provide a file name and click Next. e. Click Finish. The certificate is now exported to the file. 4. Import the certificates into the trusted certificate store of the Java virtual machine. The default Java virtual machine location is at /AppServer/java and the corresponding trusted certificate store is at /AppServer/java/jre/lib/security/cacaerts. 5. Use the keytool utility in jre/bin/keytool to insert all the certificates. For example: $keytool -import -alias 1sync -file ./1sync.cer -keystore ../lib/security/cacerts -trustcacerts The standard password for the cacerts store is changeit. After you confirm that you trust the certificate, the following message is displayed: Certificate was added to keystore. 6. Repeat this procedure for all certificates. TIBCO Collaborative Information Manager Installation and Configuration Guide 182 | Chapter 12 Installing on WebSphere Application Server Troubleshooting Websphere Application Server Problems Error Creating Catalogs and Data Sources After Installation Issues: • Error creating a catalog through the UI. • Catalog attributes not defined. • Error creating a data source through the UI. • Data source -1 could not be loaded. Solution: Via the WebSphere Admin UI, select Servers > Application Servers > server1 > Container Services > ORB Service, select the Pass by Reference check box. Background Information: If these errors are seen while performing the above functions, the WebSphere configuration may be incorrect. In WebSphere, the ORB Service should have the Pass by Reference flag checked. You can also check this value by viewing the WebSphere configuration server.xml file for your application server. Look at the XML element listed below and check if the noLocalCopies attribute is set to "true". $WAS_HOME/profiles//config/cells//nodes//servers/server1/server.xml Login Screen Not Visible and the Logs Show a “Naming service not available” Error Issue: The “Naming service not available” error is displayed in the log file and the Login screen is not visible. Solution: This usually happens when a wrong IIOP port number is specified in the $MQ_HOME/config/ConfigValues.xml file. When WebSphere starts, in the SystemOut.log, you should see the following output: [7/27/04 15:28:28:451 PDT] 7b04ccd1 HttpTransport A SRVE0171I: Transport http is listening on port 9,083. [7/27/04 15:28:28:503 PDT] 7b04ccd1 RMIConnectorC A ADMC0026I: RMI Connector available at port 2810 TIBCO Collaborative Information Manager Installation and Configuration Guide Troubleshooting Websphere Application Server Problems 183 | In this example, the port number 2810 should be used in the Configurator > Application Server > WEBSPHERE > JNDI Naming Service URL. Cannot Login After Installation Issue: You have the login screen and your seed data is good but you cannot login. Solution: This means your security provider is invalid, and you can fix that by changing your security provider class name in the Configurator. The default security provider is SUN, if using the WebSphere Application Server, select IBM as the security provider. Enabling memory allocation trace Issue: Memory allocation tracing may be requested by TIBCO Customer Support for analysis of certain problems. Solution: Setup the tracing as follows: Environment > WebSphere Variables. Select the server. Create following environment entries: IBM_MALLOCTRACE - set value as 1 MALLOC_TRACE - set value to $WAS_HOME/profiles//logs/server1/mtrace.log Substitute the absolute directory name for $WAS_HOME. Enabling garbage collection data logging Issue: If you are experiencing memory usage issues, TIBCO Customer Support may request for collection of garbage collections statistics. Solution: To enable garbage collection data collection, change the JVM settings as follows: Servers > Application Server > > Server Infrastructure > Java and Process Management >Process Definition > Java Virtual Machine. Select the Verbose garbage collection check box against it. The garbage collection data is stored in $WAS_HOME/profiles//logs/server1/native_stderr.log Failed Reflecting Values Error Issue: The "IWAV0002E Failed CIM is installed on WAS. reflecting values" warning is displayed when TIBCO Collaborative Information Manager Installation and Configuration Guide 184 | Chapter 12 Installing on WebSphere Application Server Solution: Ignore this warning. For additional information, refer to the following sites: http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp?topic=/c om.ibm.commerce.wcportal.doc/refs/rpo_configerror.htm http://www-1.ibm.com/support/docview.wss?uid=swg24015575 Incorrect Startup message Error Issue: When CIM is deployed on the Websphere Application Server, if for some reason the CIM application does not start up because of initialization errors, the Websphere Application Server UI still shows the application status as Started. Solution: None. If the user in such a scenario hits the CIM login page URL, initialization errors may be listed on that page. TIBCO Collaborative Information Manager Installation and Configuration Guide