WebSphere Network Deployment Installing Renamed Instances of SP2 WDK Apps

Transcription

1 WebSphere Network Deployment Installing Renamed Instances of SP2 WDK Apps This document provides instructions for installing renamed installations of a WDK App to an app server instance. This is done by installing the WDK App war file with the settings for Context Root and Name to a value other than the standard WDK App name. The standard installation of Web Publisher requires that the Context Root and Name be set to 'wp' during installation using Deployment Manager (DM) Admin Console. The renamed apps are installed by setting the Context Root and Name to a new name, for example,'wp2'. Installing a renamed app consists of the following major steps (Web Publisher will be referenced in these instructions): A. Normal installation of the Web Publisher using the SP2 installer B. OPTIONAL STEP: Move the Web Publisher binaries to a different location (normal installation requires default binaries location if a different location is desired, they can be moved in this step) C. Creation of a new app server instance based on the server that Web Publisher was installed to in Step A above (the new server inherits the configuring that was accomplished during standard Web Publisher installation jvm settings, etc). D. Installation of the wp.war downloaded in Step A above to the new server using DM Admin Console and setting Context Root and Name to the new desired name. E. Manual configuration of the renamed Web Publisher installation. Details for these top level steps follow below: A. Normally Install Web Publisher SP2 Perform normal installation of Web Publisher to a server in the node where you want to install a renamed Web Publisher installation (download wp.war using the Web Publisher installer, install the wp.war using Admin Console and then configure using the Web Publisher installer). There are no manual steps to perform during Step A. Note: With UNIX be sure that you start the Deployment Manager and the node of the App Server sourced with an environment that includes the normal Documentum environment variables B. OPTIONAL Move Binaries to Different Location Normal installation in Step A requires that the WDK app binaries get installed to the default location so the installer can properly configure them. After completion of Step A, if desired, you can move the installed binaries to a different location by following the steps below: 1. Home Connect to DM Admin Console and Select ' ' link. 2. Select the app server where you installed Web Publisher in Step A, and click on Stop Page 1 of 5

2 3. Home Select 'Enterprise ' link 4. Enterprise 5. Name (wp) 6. Enterprise Click on the the application installed in Step A (wp) In ' Binaries' enter the path to the desired new location. The path must end with the root directory for the application (e.g. wp.ear). Click on OK. 7. Home Select ' ' link. 8. Select the app server where you installed Web Publisher in Step A, and click on Start C. Create a New App Server 1. Connect to DM Admin Console and Select ' ' link Create New Server 4. Create New Server Click on 'New'. Make sure the node where you installed Web Publisher in Step A is selected. Enter a new Server Name. Choose radio button Select template Existing application server, and select the server where you installed Web Publisher in Step A. Click Next. Click Finish.. 6. Home Now you will map Default app to the new server (need for Virtual Links support). Select 'Enterprise ' link. 7. Enterprise 8. Default 9. Selecting Click on 'Default' link Click on the 'Map modules to application servers' link Select the Module checkbox, shift select the new app server and the existing app servers that need Default installed, click Apply and then click OK Page 2 of 5

3 10. Default 11. Enterprise Scroll down and click OK (not save) 12. Home Select ' ' link <new app server> 15. Web Container 16. HTTP Transport 17. HTTP Transport Click on the link to the server you just created Click on 'Web Container' link Click on 'HTTP Transports' link Record the port numbers Record the port numbers and go back to the Home page 18. Home Select Environment Virtual Host link 19. Virtual Host Click on 'default_host' link 20. default_host Click on 'Host Aliases' link 21. Host Aliases Click on New 22. New Enter an asterisk (*) in the Host Name field and the non-secure port number (e.g. 9085) in the Port field and then click OK Do the same with the secure port number (e.g. 9444), click OK OK and then click on the 'Save' link 23. Save Note: Instead of creating a new app server, you can perform normal installation of Web Publisher on an existing server (installation of the wp.war or mapping existing install to another server, running the Web Publisher installer to configure the server and mapping Default to the server). Then you can continue with the same steps below. D. Install wp.war With New Context Root and App Name 9. Home Select 'Install New ' link 10. Prep for App Install Prep for App Install Enter or browse to the location of the wp war file you downloaded in Step A (do NOT rename this war file) - Enter the desired new application name (e.g. wp2) into the 'Context Root' field and then click Next Click Next Page 3 of 5

4 12. Install App Step 1 Provide Options 13. Install App Step 2 Map Virtual Hosts 14. Install App Step 3 Map Modules to 15. Install App Step 4 Summary - You can enter a location for 'Directory to Install ' if you don't want the default location (default location is under installedapps directory). NOTE: You do NOT have to use the default location when installing renamed apps. - Enter the desired new application name (e.g. wp2) into the ' Name' and then click Next Click Next Select the Module checkbox, select the newly created app server for installation, click Apply and then click OK Click Finish 16. Installing After installation is completed, click on the 'Save to Master Configuration' link 17. Save Click on Save - Save E. Manually Configure the Renamed Web Publisher App 1. Home Select 'Enterprise ' link 2. Enterprise 3. <new application> Select the link of the new application 4. Library Ref Click the 'Add' link Scroll down and select the 'Libraries' link 5. New Select the standard wp library and click OK. 6. Enterprise Scroll down and click OK (not save) 7. Enterprise Manually copy the was.policy file from the location of the standard wp install to the same relative location of the renamed installation:./deploymentmanager/config/cells/<cellname>/applications/wp.war/deployments/wp/meta -INF/was.policy 9. Manually copy the app.xml file from the location of the standard install to the same relative location of the renamed installation:./appserver/installedapps/<deploymentmanagermode>/wp.ear/wp.war/wp/app.xml (Note: For other WDK apps, the app.xml file is located in the 'wdk' directory) 10. Perform a full synchronization of the App Server node. 11. Stop / Restart the app servers. Page 4 of 5

5 Repeat Steps C E for each additional desired renamed Web Publisher app installation to this SAME NODE. If you want to install to another node, repeat all of the steps the first time. Page 5 of 5