SettingupWebSphereApplicationServer设置WAS服务器.doc

Setting up WebSphere Application ServerBefore you can deploy CLM applications war files, you must setup your WebSphere Application Server.Before you beginEnsure you have completed the following tasks: WebSphere Application Server is already installed. On Unix systems, ensure that the Open File Limit value is properly set. For more information, see Planning to install on UNIX and Linux systems. The database is created. If you use the default Derby database for evaluation purposes, ensure the location to the database in the perties file is an absolute path. 1. Navigate to JazzInstallDir/server/conf/app where JazzInstallDir is where you installed Jazz Team Server and app is a directory for jts, ccm, or rqm. 2. Open perties for editing. 3. Locate the Derby database location com.ibm.team.repository.db.jdbc.location=conf/jts/derby/repositoryDB, and change the location with an absolute path. For example, com.ibm.team.repository.db.jdbc.location=C:/Progra1/IBM/JazzTeaMServer/server/conf/jts/derby/repositoryDB. The Java 2 Security option must be turned off. If this option is turned on in WebSphere Application Server, the web application will not start. 1. Click Security Global security. 2. Under Java 2 security, clear the check box for Use Java 2 security to restrict application access to local resources. 3. Ensure that the Enable administrative security and Enable application security check boxes are selected. Ensure that the Use available authentication data when an unprotected URI is accessed application server security setting is selected. If you are using the Integrated Solutions Console for the server, use the following steps to verify this setting: 1. Click Security Global security Web and SIP security General settings. 2. Click the Use available authentication data when an unprotected URI is accessed check box. 3. Click OK and Save directly to the master configuration. The Jazz web interface requires that authentication be configured in order to perform authorization and personalize the application. About this taskThis document does not provide details for configuring WebSphere authentication or SSL, which is a complex topic. Detailed information about the various authentication and encryption options is covered in the WebSphere Application Server Information Center. For more information, go to the WebSphere Information Center and use this phrase in search: Securing applications and their environment. Important: The figures used for heap sizes and JVM arguments are only a suggestion; set the value according to your environment. A typical medium-size team can use a value of 4096 MB, providing 4 GB of heap memory for the Jazz Team Server process on a 64-bit computer with a minimum of 8 GB of physical memory. It is important to use the same amount for Initial and Maximum heap sizes. When increasing the Java heap size, ensure that enough unused physical memory is available on the machine to cover the increase. If sufficient physical memory is not available, either install additional memory or take into account the effect on overall performance that occurs.It is also important to have more physical memory than is required by all of the processes on the machine combined to prevent paging or swapping. Paging reduces the performance of the system and affects the performance of the Java memory management system.Procedure1. Verify or update the WebSphere Application Server level. For a list of supported versions and fix packs, see the Detailed System Requirements page. 2. Jazz Team Server requires several specific settings on the Java Virtual Machine in which it runs. To set these properties, in the WebSphere Integrated Solutions Console, click Servers Server Types WebSphere application servers Server1. 3. Under Server Infrastructure, click Java and Process Management Process definition. 4. Under Additional Properties, click Java Virtual Machine. 5. Add the value 4096 to Initial Heap. 6. Add the value 4096 to Maximum Heap Size. 7. In the Generic JVM arguments field, type the following line: -Xmx4g -Xms4g -Xmn512m-Xgcpolicy:gencon -Xnocompressedrefs-Xmx4g -Xms4g -Xmn512m-XX:MaxPermSize=768M -XX:ReservedCodeCacheSize=512M -XX:CodeCacheMinimumFreeSpace=2MNote: Mac OS X is unsupported.-Xmx4g -Xms4g -Xmn512m-XX:MaxPermSize=768M -XX:ReservedCodeCacheSize=512M -XX:CodeCacheMinimumFreeSpace=2M-Xmx4g -Xms4g -Xmn512m-Xgcpolicy:gencon -Xcompressedrefs-Xgc:preferredHeapBase=0x100000000-Xmx4g -Xms4g -Xmn512m-Xgcpolicy:gencon -Xcompressedrefs-Xgc:preferredHeapBase=0x100000000Tip: If you need more heap size, then you can use the following setting, replacing N with the amount of memory to be used and N/8 with 1/8 of the total memory. For example, if -Xmx is set to 8g, -Xmn should be set to 1g.-Xgcpolicy:gencon -XmxN -XmsN -XmnN/8-Xcompressedrefs -Xgc:preferredHeapBase=0x1000000008. Click Apply, and then click Save directly to the master configuration. 9. One of the custom properties you must add is JAZZ_HOME, a system property that specifies where to find certain configuration files. This property uses a URL rather than a simple path, so specify the value as a file-style URL: file:/file path. Under Java Virtual Machine Additional Properties, click Custom properties. Remember: You must use three forward slashes (/) after file:Important: In a distributed environment, when you are using a separate application server for each web application, you must add these custom properties for each instance of the WebSphere Application Server.10. Click New, enter JAZZ_HOME in the Name field, and enter file:/JazzInstallDir/server/conf in the Value field. Substitute JazzInstallDir with the location of Jazz Team Server installation directory. For example, enter file:/C:/PROGRA1/IBM/JazzTeamServer/server/conf on Windows or enter file:/home/user/IBM/JazzTeamServer/server/conf on UNIX systems. Note: To avoid problems, do not use spaces in file paths. For the Program Files directory you can use PROGRA1, and for the Program Files (x86) directory, you can use PROGRA2.11. Click OK. 12. Repeat step 10 and add these custom properties: o Name: java.awt.headless Value: true o Name: org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin Value: true o If you are connecting to an Oracle database, Name: ORACLE_JDBC_DRIVER_FILE Value: Absolute path to the JDBC driver/ojdbc6.jar Note: The path to the JDBC driver must be an absolute path. Do not use URL path (file:/). For more information about Oracle Java Database Connectivity (JDBC) connections, see Setting up an Oracle database.o If you are connecting to a SQL Server database, Name: SQLSERVER_JDBC_DRIVER_FILE Value: Absolute path to the JDBC driver/sqljdbc4.jar Note: