Edit
Attach
P
rintable
r16 - 2014-05-01 - 16:51:09 - Main.sbeard
You are here:
TWiki
>
Deployment Web
>
DeploymentInstallingUpgradingAndMigrating
>
InstallProxyServers
>
ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right"> Configuring enterprise CLM reverse proxies: !WebSphere 8.5 ND Proxy %DKGRAY% Authors: Main.IndradriBasu, Main.SudhakarFrederick <br> Build basis: Rational solution for Collaborative Lifecycle Management (CLM) 4.0.3, !WebSphere Application Server - Network Deployment 8.5.0.2 %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> This guide explains how to setup and configure a CLM environment using [[http://www-01.ibm.com/software/webservers/appserv/was/][WebSphere Application Server - Network Deployment (WAS ND)]] and [[http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.ibm.websphere.nd.multiplatform.doc%2Fae%2Ftjpx_setupps.html][WebSphere Proxy Server]], such that users will be able to access the various CLM applications by changing the context root of a central URL which is processed by !WebSphere Proxy Server. The Proxy Server will then route the requests to the appropriate application server nodes where the CLM applications (JTS, CCM, QM, RM) reside. ---++ Other topics in this series * [[UnderstandingReverseProxy][Understanding reverse proxy]] * [[ConfigureCLMEnterpriseReverseProxy][Configuring Enterprise CLM Reverse Proxies: WebSphere 8 and IHS 8]] * [[ConfigureCLMEnterpriseReverseProxyWithApache][Configuring Enterprise CLM Reverse Proxies: Apache and mod_proxy]] ---++ Introduction In this deployment scenario you will setup a CLM environment and a proxy server, with each of the applications in a separate WAS profile in a single physical server environment. The user accessible Public URIs will be different as the Proxy Server will route the requests to respective application server nodes. The topology is described in detailed in the CLM Infocentre topic [[https://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/topic/com.ibm.jazz.install.doc/topics/c_topology_ex_stand_clm_dept.html][Standard single-server departmental topology]] while the use of Proxy Servers in CLM topologies is described in [[https://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/c_reverse_proxy.html&scope=null][Reverse proxy servers in topologies]]. This topology is typically useful for deployments where the initial volume of users is low or in deployments where only a single CLM application (CCM, RM or QM) is initially used. As the volume of users increases or additional applications are added, a distributed enterprise topology should be considered. As described in the Infocentre - in addition to being able to redeploy the applications at a later stage - using a proxy server has the following additional benefits: * Server rename can be avoided, unless there is a change in domain name itself. * For security and user friendliness, port numbers are not visible (not required) in the public URIs <p class="message-area message-warn"><b>WARNING:</b> <span style="font-weight: bold;">All of the setup and configuration documented here MUST be done *before* running the JTS setup wizard to ensure that the public URIs are set correctly to the external URIs.</span></p> An example of what you should have at the end of this article is provided in this sketch: %ATTACHURL%/clm-rp-overview.png ---++ Prerequisites and Assumptions <ul> <li>WebSphere Application Server ND profiles are used<br /></li> <li>When configuring Global Security in Section 1.2 follow the guidance in one of the following articles :<br> <a href="https://jazz.net/library/article/97">Tip: Configuring WAS with Federated realm</a><br> <a href="https://jazz.net/library/article/96">Tip: Configuring WAS with LDAP realm</a><br> <a href="https://jazz.net/library/article/549">Installing Rational Team Concert 3.x with IBM WAS, IBM DB2 and Microsoft Active Directory</a><br> <a href="https://jazz.net/library/article/479">Configuring Jazz applications for LDAP on WAS 7.0.0.7</a><br/></li> <li>In this example you will only deploy the JTS and CCM applications for brevity. Once the WAS application server template has been created, it is simple enough to use it to deploy the other applications as required.</li> <li>Administrative console access to the WAS Deployment Manager profile is available<br /></li> <li>The firewall on the server must allow access to only port 443 from the outside world</li> <li>A separate database server is available</li> <li>The physical host used in the example is called "vhost5459". A DNS alias exists that maps "clm.example.org" to this host.<br /></li> <li>Though the steps here were carried out in a Windows environment, their Unix/Linux equivalents will work as well.</li> </ul> <h2><a name="Procedure" id="Procedure"></a>Procedure</h2> <h3></a>1 Setup the ND Deployment Manager<br /></h3> <h4>1.1 Create a Deployment Manager profile</h4> <p>Launch a the !WebSphere Profile Management Tool (PMT) which comes along with the !WebSphere ND installation. You can also launch it from:</p> <pre> <WAS_ND_Install_Dir>/bin/ProfileManagement/pmt.(sh|bat)<br /> </pre> <p>Once the Profile Management Tool has launched, click the <b>"Create..."</b> button. In the dialog window that opens:<br /></p> <ol> <li>Select <b>"WebSphere Application Server</b> > <b>Management"</b> , click <b>"Next >"</b></li> <li>Select <b>"Deployment manager"</b>, click <b>"Next >"</b></li> <li>Select <b>"Advanced profile creation"</b>, click <b>"Next >"</b></li> <li>Ensure the <b>Deploy the administrative console (recommended)</b> option is checked. Click <b>"Next >"</b></li> <li>Leave the defaults, click <b>"Next >"</b></li> <li>Change the following (as per the DNS Alias):<br /> <b>Node Name:</b> clmCellManager01<br /> <b>Host Name:</b> clm.example.org<br /> <b>Cell Name:</b> clmCell01<br /></li> <li>Keep "Enable administrative security" enabled and choose an administrative <b>user name</b> and <b>password</b>. For Example:<br /> <b>User name:</b> admin<br /> <b>Password:</b> admin<br /> Click <b>"Next >"</b></li> <li>Leave the defaults, click <b>"Next >"</b> twice.</li> <li>Make a note of the SOAP port as you will need that while federating application server and proxy server nodes (The default value is 8879).<br /> Leave the default ports, click <b>"Next >"</b></li> <li>Choose whether to run dmgr as a service, click <b>"Next >"</b></li> <li>Click <b>"Create"</b> to create the Deployment Manager profile.</li> <li>Once finished, launch the <i>First Step Console</i> and <b>Start the Deployment Manager</b></li> </ol> <p>Alternatively, you can use the command line to create a deployment manager profile.<br /> To do so, Open a command window and navigate to <i>WebSphere_Install_Folder/bin</i> and execute the following commands:</p> <pre> <WAS_ND_Install_Dir>/bin/manageprofiles.(sh|bat) -create -templatePath <WAS_ND_Install_Dir>/profileTemplates/management -profileName Dmgr01 -profilePath <WAS_ND_Install_Dir>/profiles/Dmgr01 -enableAdminSecurity true -adminUserName admin -adminPassword admin] </pre> <p>Start the Deployment manager profile.<br /></p> <pre> startServer.(sh|bat) dmgr -profileName Dmgr01 </pre> <h4>1.2 Set up Global Security on the Deployment Manager<br /></h4> <p>It is recommended to fully configure the deployment manager security before creating the nodes which will host the application servers. Each of the nodes uses authentication to communicate with the Deployment Manager and if authentication is not configured on the Deployment Manager before the nodes are deployed, the nodes will need to be manually resynchronized.<br /></p> <p>Follow the <a href= "http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/t_deploy_cluster_setup_was_user_registry.html&scope=null"> Configuring Global Security</a> instructions to setup the parameters.<br /></p> <p>Set up the authentication mechanism, refer to <a href="#Prerequisites_and_Assumptions">Prerequisites and Assumptions</a> section.</p> <p>Additionally, configure the Single Sign-on for the Deployment Manager which will be followed by all the other nodes which you are about to create. This is to ensure that applications across different nodes can be accessed by users without having to re-authenticate.<br /></p> <ul> <li>In !WebSphere Integrated Solutions Console, click <b>Security</b> > <b>Global security</b>.</li> <li>Under <b>Authentication</b> section, expand the <b>Web and SIP security</b> and click <b>Single sign-on (SSO)</b></li> <li>Click the <b>Requires SSL</b> check box.</li> <li>In the <b>Domain Name</b> text box, specify <b>your domain name</b> (e.g. example.org) for which the SSO is applicable.</li> <li>Click <b>OK</b> and <b>Save</b> directly to the master configuration.</li> <li style="list-style: none"><br /></li> </ul> <h4>1.3 Restart the Deployment Manager Profile<br /></h4> To Stop the Deployment Manager profile: <pre> <WAS_ND_Install_Dir>/bin/stopServer.(sh|bat) dmgr -profileName DMGR01 -username <admin username> -password <admin user password><br /> </pre> To Start the Deployment Manager profile: <pre> <WAS_ND_Install_Dir>/bin/startServer.(sh|bat) dmgr -profileName DMGR01<br /> </pre> <h4>1.4 Enable Automatic Node Synchronization</h4> <p>Moving forward, all configuration changes you are about to perform, must be propagated and synchronized between all the nodes agents. The synchronization between nodes can be performed manually but enabling automatic synchronization is a more effective way and saves manual effort.</p> <ol> <li>Using a browser, open the !WebSphere Administrative Console (For example: <a href="http://clm.example.org:9043/ibm/console" target="_top">https://clm.example.org:9043/ibm/console</a> and login using the username:<b>admin</b> and password:<b>admin</b><br /></li> <li>Navigate to <b>"System Administration</b> > <b>Console Preferences"</b> and select <b>"Synchronize changes with Nodes"</b></li> <li>Click <b>"Apply"</b></li> </ol> <h3>2 Setup the Application Server Nodes</h3><br /> <h4>2.1 Create and Federate Application Server Nodes</h4> <p>Launch the !WebSphere Profile Management Tool (PMT). You can also launch it from the command line:</p> <pre> <WAS_ND_Install_Dir>/bin/ProfileManagement/pmt.(sh|bat)<br /> </pre> <p>Once the Profile Management Tool has launched, click the <b>"Create..."</b> button. In the dialog that opens:<br /></p> <ol> <li>Select <b>"WebSphere Application Server</b> > <b>Custom profile"</b> , click <b>"Next >"</b></li> <li>Select <b>"Advanced profile creation"</b> and click <b>"Next>"</b></li> <li>Optionally change the Application Server profile name to something meaningful like <b>JTSSrv</b>. Change the profile directory path as well to <b><WAS_ND_Install_Dir>/profiles/JTSSrv</b>. Click <b>"Next >"</b></li> <li>Change the "Node name" to <b>JTSNode</b> to match the profile name and change the "Host name" to <b>clm.example.org</b> (as per your DNS alias) . Click <b>"Next >"</b></li> <li>To federate this Node with the Deployment Manager, enter the FQDN (Fully Qualified Domain Name) of the server in the <i>Deployment Manager Host name or IP address</i> text box. In this case enter <b>clm.example.org</b>.<br /> Enter the correct Soap Port number of the Deployment Manager node.<br /> <b>NOTE:</b> The Soap Port number, can be found in the <WAS_ND_Install_Dir>/profiles/Dmgr01/logs/AboutThisProfile.txt file.<br /> <br /> Under Deployment Manager Authentication, enter the username and password of the Deployment Manager profile.<br /> Click <b>"Next >"</b><br /></li> <li>Leave the defaults and click <b>"Next >"</b> twice.</li> <li>In the Security Certificate (Part 2) page, ensure the certificate information matches the DNS alias name. Click <b>"Next>"</b></li> <li>Leave the defaults and click <b>"Next >"</b></li> <li>Click <b>"Create"</b></li> <li>Once the profile creation finishes, uncheck the "Launch the First Step Console" box and click <b>"Finish"</b>.</li> </ol> Repeat the above steps to create another profile. In Step 3 and 4, enter the profile Name as <b>CCMSrv</b> and Node name as <b>CCMNode</b>. <p>Alternatively, you can use the command line to create a custom profile and federate it with the Deployment Manager.<br /> To do so, Open a command window and navigate to <i>WebSphere_Install_Folder/bin</i> and execute the following commands:</p> <pre> <WAS_ND_Install_Dir>/bin/manageprofiles.(bat|sh) -create -profileName CCMSrv -enableAdminSecurity true -adminUserName jtsadmin -adminPassword Passw0rd -templatePath <WAS_ND_Install_Dir>/profileTemplates/managed -profilePath <WAS_ND_Install_Dir>/profiles/CCMQMSrv -federateLater true </pre> <pre> <WAS_ND_Install_Dir>/profiles/CCMSrv/bin/addNode.(bat|sh) clm.example.org 8879 -username jtsadmin -password Passw0rd </pre> <br /> <p>Verify that the newly created Nodes agents are started and their Status is running (as shown below).<br /></p> <ul> <li>In the !WebSphere Administrative Console, navigate to <b>System administration</b> > <b>Node Agents</b><br /> <img style="width=630 height=125" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1listNodeAgents1.png" /></li> <li style="list-style: none"><br /></li> </ul> <h4>2.2 Create Application Servers on the Federated Nodes</h4> <p>So far, you have created two managed nodes for application servers. Now, you will create and configure one application server (for the JTS application) and create an application server template from it, and then create the second application server (for the CCM application) from the template. This is more efficient than performing the same configuration for each and every application server definitions.</p> <p>To create Application Server definitions, follow the steps below.<br /></p> <ol> <li>Login to the !WebSphere Administrative Console for the Deployment Manager. (For example: https://clm.example.org:9043/ibm/console)</li> <li>On the left panel, navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere Application Servers</b></li> <li>On the right hand section, click the <b>New</b> button and Server creation wizard will come up.<br /> <img style="width=635 height=233" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateAppSrv0.png" /></li> <li style="list-style: none"><br /> <br /></li> <li>Select the <i>Node name</i> as <b>JTSNode</b> and type <b>JTSServer</b> in the <i>Server name</i> text box. Click <b>Next</b>.<br /> <br /> <img style="width=624 height=255" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateAppSrv1.png" /></li> <li style="list-style: none"><br /> <br /></li> <li>In Step 2, select <b>default</b> server template and click <b>Next</b>.<br /> <img style="width=638 height=260" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateAppSrv2.png" /></li> <li style="list-style: none"><br /></li> <li>In Step 3, leave the defaults and click <b>Next</b>.<br /> <img style="width=632 height=249" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateAppSrv3.png" /></li> <li style="list-style: none"><br /></li> <li>In the final Step, click <b>Finish</b>.<br /> <img style="width=631 height=313" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateAppSrv4.png" /></li> <li>Once you are back on the Application Server page, click <b>Save</b> directly to the master configuration.</li> <li>Once the Nodes are synchronized, click <b>OK</b>.</li> </ol> <h4>2.3 Configure the Application Server</h4> <p>Before deploying the CLM applications, you must configure each of the application servers.<br /> Follow the CLM Infocenter topic [[http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/t_s_server_installation_setup_WAS.html][Setting up !WebSphere Application Server]] to configure the parameters for the application server created in the previous step.</p> <h4>2.4 Create an Application Server Template</h4> <p>Now that you finished configuring the first application server, you will create a template from it so that you can create the second server identical to the configuration of the first server.</p> <ol> <li>Navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere application servers</b></li> <li>Select the <b>JTSServer</b></li> <li style="list-style: none">and click <b>Templates...</b>.<br /> <img style="width=483 height=260" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateTmpl1.png" /><br /> <br /></li> <li>Click the <b>New</b> button.</li> <li>Select the <b>JTSServer</b> and click <b>OK</b></li> <li style="list-style: none"><br /> <img style="width=523 height=223" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateTmpl2.png" /><br /> <br /></li> <li>Give a <i>Name</i> to the template like <b>clm_server_template</b> and optionally, enter a <i>Description</i>. Click <b>OK</b><br /> <img style="width=536 height=243" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateTmpl3.png" /></li> <li style="list-style: none"><br /></li> <li>Click <b>Save</b> directly to master configuration.</li> <li style="list-style: none"><br /></li> <li>Once the Nodes are synchronized, click <b>OK</b>.</li> <li style="list-style: none"><br /></li> </ol> <h4>2.5 Create the second Application Server using the Template</h4> <p>Now that our custom application server template is created, we will proceed towards creating the second application server instance. This step is very similar to what you have done earlier except that you select the newly created <i>clm_server_template</i> instead of the <i>default</i> template.<br /></p> <ol> <li>Navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere application servers</b></li> <li>Click the <b>New</b> button.</li> <li>Select <b>CCMNode</b> as the <i>node name</i> and type the <i>server name</i> as <b>CCMServer</b>. Click <b>Next</b>.<br /> <br /> <img style="width=628 height=251" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateAppSrv6.png" /></li> <li style="list-style: none"><br /> <br /></li> <li>Select the <b>clm_server_template</b> template and click <b>Next</b>.<br /> <br /> <img style="width=628 height=284" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateAppSrv7.png" /></li> <li style="list-style: none"><br /> <br /></li> <li>Ensure the <b>Generate Unique ports</b> is checked. Click <b>Next</b>.</li> <li>Click <b>Finish.</b></li> <li>Click <b>Save</b> directly to the master configuration.</li> </ol> <h4>2.6 Start the Application Servers on Federated Nodes</h4> <ol> <li>Open the !WebSphere Administrative Console in a browser. For example: https://clm.example.org:9043/ibm/console</li> <li>On the Left hand panel, navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere Application Servers</b></li> <li>On the right hand section, select the Application Servers and click <b>Start</b>.<br /> <img style="width=634 height=218" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1StartAppSrv1.png" /></li> <li style="list-style: none"><br /> <br /> Ensure the Status pane is showing that both the servers are running as indicated by a green arrow.<br /></li> </ol> <h3><a name="mozTocId290304" id="mozTocId290304"></a>3 Setup the WAS ND Proxy Server</h3> <h4>3.1 Create and federate a Node for the Proxy Server<br /></h4> To create a Proxy Server Profile <p>Launch a the !WebSphere Profile Management Tool (PMT). You can also launch it from:</p> <pre> <WAS_ND_Install_Dir>/bin/ProfileManagement/pmt.(sh|bat)<br /> </pre> <p>Once the Profile Management Tool has launched, click the <b>"Create..."</b> button. In the dialog window that opens:<br /></p> <ol> <li>Select <b>"WebSphere Application Server</b> > <b>Custom profile"</b> , click <b>"Next >"</b></li> <li>Select <b>"Advanced profile creation"</b> and click <b>"Next>"</b></li> <li>Change the profile name to <b>ProxySrv</b>. Accordingly, change the profile directory path as well to <b><WAS_ND_Install_Dir>/profiles/ProxySrv</b>. Click <b>"Next >"</b></li> <li>Change the "Node name" to <b>ProxyNode</b> to match the profile name and change the "Host name" to <b>clm.example.org</b> (as per your DNS alias) . Click <b>"Next >"</b></li> <li>To federate this Node with the Deployment Manager, enter the FQDN (Fully Qualified Domain Name) of the server in the <i>Deployment Manager Host name or IP address</i> text box. In this case enter <b>clm.example.org</b>.<br /> Enter the correct Soap Port number of the Deployment Manager node.<br /> <b>NOTE:</b> The Soap Port number, can be found in the <WAS_ND_Install_Dir>/profiles/Dmgr01/logs/AboutThisProfile.txt file.<br /> <br /> Under Deployment Manager Authentication, enter the username and password of the Deployment Manager profile.<br /> Click <b>"Next >"</b><br /></li> <li>Leave the defaults and click <b>"Next >"</b> twice.</li> <li>In the Security Certificate (Part 2) page, ensure the certificate information matches the DNS alias name. Click <b>"Next>"</b></li> <li>Leave the defaults and click <b>"Next >"</b></li> <li>Click <b>"Create"</b></li> <li>Once the profile creation finishes, uncheck the "Launch the First Step Console" box and click <b>"Finish"</b>.</li> </ol> <br /> <p>Alternatively, you can use the command line to create a custom profile and federate it with the Deployment Manager. To do so, Open a command window and navigate to !WebSphere_Install_Folder/bin. Issue the following command:</p> <pre> <WAS_ND_Install_Dir>/bin/manageprofiles.(bat|sh) -create -profileName ProxySrv -enableAdminSecurity true -adminUserName jtsadmin -adminPassword Passw0rd -templatePath <WAS_ND_Install_Dir>/profileTemplates/managed -profilePath <WAS_ND_Install_Dir>/profiles/ProxySrv -federateLater true </pre> <pre> <WAS_ND_Install_Dir>/profiles/ProxySrv/bin/addNode.(bat|sh) clm.example.org 8879 -username jtsadmin -password Passw0rd </pre> <h4>3.2 Create the Proxy Server on the Federated Node</h4> <p>To create Proxy Server definitions, follow the steps below.<br /></p> <ol> <li>First ensure if the Proxy Server Node that you have just created has Started.<br /> In the !WebSphere Administrative Console, navigate to <b>System administration</b> > <b>Node Agents</b><br /> <img style="width=633 height=223" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1listNodeAgents2.png" /></li> <li style="list-style: none"><br /></li> <li>Login to the !WebSphere Administrative Console.</li> <li>On the Left hand panel, navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere proxy servers</b></li> <li>On the right hand section, click the <b>New</b> button and Server creation wizard will come up.</li> <li>Select the <i>Node name</i> as <b>ProxyNode</b> and type <b>CLMProxy</b> in the <i>Server name</i> text box. Click <b>Next</b>.<br /> <br /> <img style="width=630 height=252" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateProxySrv1.png" /></li> <li style="list-style: none"><br /> <br /></li> <li>In Step 2, uncheck <b>SIP</b> check box and click <b>Next</b>.<br /> <img style="width=633 height=245" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateProxySrv2.png" /></li> <li style="list-style: none"><br /> <br /></li> <li>In Step 3, leave the defaults and click <b>Next</b>.<br /> <img style="width=632 height=249" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1CreateProxySrv3.png" /></li> <li style="list-style: none"><br /> <br /></li> <li>In the final Step, click <b>Finish</b>.<br /></li> <li>Click <b>Save</b> directly to the master configuration</li> <li style="list-style: none"><br /></li> <li>Once the Nodes are synchronized, click <b>OK</b>.</li> </ol> <h4>3.3 Configuring the Proxy Server</h4> <ol> <li>Login to the !WebSphere Administrative Console.</li> <li>On the Left hand panel, navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere proxy servers</b></li> <li>On the right hand side, click the <b>CLMProxy</b><br /> <img style="width=588 height=268" alt="" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1ConfigProxySrv1.png" /></li> <li style="list-style: none"><br /> <br /></li> <li>Under <b>Communications</b> section, expand the <b>Ports</b> and ensure that PROXY_HTTP_ADDRESS and PROXY_HTTPS_ADDRESS are set to 80 and 443 respectively.<br /> <img style="width=417 height=386 alt=" src="https://jazz.net/wiki/pub/Deployment/ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxy/ss1ConfigProxySrv2.png" /></li> <li style="list-style: none"><br /> <br /> If they are not set to as shown above, then you may want to check if any other proceses are blocking port 80 or 443. Click the <b>Details</b> button and change them as needed.<br /> <br /></li> <li>Under <b>Server Infrastructure</b> section, go to <b>Java and Process Management</b> > <b>Process definition</b> > <b>Java Virtual Machine</b><br /></li> <li>Under <b>General Properties</b>, ensure the <b>Verbose garbage collection</b> check box is unchecked.</li> <li>Under General Properties, set the <b>Minimum heap size</b> is set to <b>256MB</b>.</li> <li>Under General Properties, set the <b>Maximum heap size</b> is set to <b>1024MB</b>.</li> <li>In the <b>Generic JVM arguments</b>, add the following argument<br /> <pre> -Xgcpolicy:gencon<br /> </pre></li> <li>Click <b>Apply</b>, and then click <b>Save</b> directly to the master configuration.</li> </ol> <p>You will increase the persistent timeout value so that the connection between the application servers and the proxy server remains open for a little longer time.</p> <ol> <li>Navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere proxy servers</b></li> <li>On the right hand side, click the <b>CLMProxy</b><br /></li> <li>Under <b>Proxy Settings</b>, expand the <b>HTTP Proxy Server Settings</b> tree.</li> <li>Click <b>Proxy server transports</b>.</li> <li>Click <b>HTTPS_PROXY_CHAIN</b>. It should be associated with port 443.</li> <li>Click <b>HTTP inbound channel (HTTP 4)</b>.</li> <li>Under <b>General Properties</b>, set the <b>Persistent timeout</b> to <b>60</b> seconds.</li> <li>Click <b>Apply</b>, and then click <b>Save</b> directly to the master configuration.</li> </ol> <p>Configure the Proxy server thread pools to match the same settings as the CLM application server nodes.</p> <ol> <li>Navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere proxy servers</b></li> <li>On the right hand side, click the <b>CLMProxy</b><br /></li> <li>Under <b>Additional Properties</b>, click <b>Thread pools</b></li> <li>Click <b>Proxy</b></li> <li>Under <b>General Properties</b> make sure the <i>Minimum Size</i> and <i>Maximum Size</i> are both set to <b>200</b> threads</li> <li>Click <b>Apply</b>, and then click <b>Save</b> directly to the master configuration.</li> </ol> <br /> <h4>3.4 Configuring Virtual Hosts</h4> <p>You will be using the <b>default_host</b> virtual hosts in this setup to exchange all communications and as mentioned earlier and you may want the proxy server to resolve only to the DNS alias you have created earlier using the HTTPS port 443 only.</p> <p>To ensure the web modules are associated with the virtual host:</p> <ol> <li>Open and login to the !WebSphere Administrative Console in a browser.</li> <li>On the Left hand panel, navigate to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere application servers</b></li> <li>On the right hand side, click on <b>JTSServer</b></li> <li>Under <b>Communications</b> section, expand the <b>Ports</b> and note down port number for the <b>WC_defaulthost_secure</b> <i>(if you are using an unsecured communication use <b>WC_defaulthost</b> instead)</i></li> <li>Ensure the port number that you noted, exists in the list under <b>Environment</b> > <b>Virtual Hosts</b> > <b>default_Host</b> > <b>Host Aliases</b>. If not, add an entry by clicking on the <b>New</b> button on the above pane.</li> <li>Click <b>Save</b> directly to the master configuration.</li> <li>Once the Nodes are synchronized, click <b>OK</b>.</li> </ol> <p class="message-area message-warn"><b>NOTE:</b> <span style="font-weight: bold;">Repeat the above steps for all application servers. As in this case for JTSServer and CCMServer</span></p> <p>To configure the virtual host with DNS alias:</p> <ol> <li>Open and login to the !WebSphere Administrative Console in a browser.</li> <li>On the Left hand panel, navigate to <b>Environment</b> > <b>Virtual Hosts</b></li> <li>Click <b>default_host</b> > <b>Host Aliases</b></li> <li>For port 443, click the <b>*</b> and replace with the DNS alias <i>(clm.example.org)</i> and click <b>OK</b>.</li> <li>Click <b>Save</b> directly to the master configuration.</li> <li>Once the Nodes are synchronized, click <b>OK</b>.</li> </ol> <br /> <h4>3.5 Starting the Proxy Server</h4> <ol> <li>Navigate back to <b>Servers</b> > <b>Server Types</b> > <b>WebSphere proxy servers</b></li> <li>Select <b>CLMProxy</b> and click <b>Start</b> button to start the proxy server.</li> </ol> <br /> <h2><a name="mozTocId231382" id="mozTocId231382"></a>Deploying CLM applications</h2> <br /> <p>Follow the <a href="http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/t_deploy_was.html"> Deploy CLM Applications on the Server</a> instructions except follow the table below while Mapping Modules to the application servers.<br /> <br /></p> <div> <table style=" width: 640px;" class="gray-table" min-width="600" max-width="600"> <tbody> <tr> <th style=" vertical-align: top; width: 10px;"> <div><strong>Application</strong></div> </th> <th valign="top"> <div><strong>Node</strong></div> </th> <th valign="top"> <div><strong>Mapped Server</strong></div> </th> <th valign="top"> <div><strong>Context root</strong></div> </th> </tr> <tr> <td valign="top">admin.war<br /></td> <td valign="top">JTSNode<br /></td> <td valign="top"> cell=clmCell01,node=JTSNode,server=JTSServer<br /></td> <td valign="top">/admin<br /></td> </tr> <tr> <td valign="top">ccm.war<br /></td> <td valign="top">CCMNode<br /></td> <td valign="top"> cell=clmCell01,node=CCMNode,server=CCMServer<br /></td> <td valign="top">/ccm<br /></td> </tr> <tr> <td valign="top">jts.war<br /></td> <td valign="top">JTSNode<br /></td> <td valign="top"> cell=clmCell01,node=JTSNode,server=JTSServer<br /></td> <td valign="top">/jts<br /></td> </tr> <tr> <td></td> </tr> </tbody> </table> </div> You are now ready to run the JTS/Setup.<br /> <h2><a name="mozTocId860038" id="mozTocId860038"></a>Running the JTS Setup wizard</h2> Now that you have URLs that are server agnostic, you can run the <a href="http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_s_server_installation_setup_wizard.html"> JTS setup wizard</a> and use these URLs when registering the applications. Here are the discovery URLs that will be used:<br /> <br /> Change and Configuration Management: https://clm.example.org/ccm/scr<br /> <br /> <h2><a name="mozTocId343308" id="mozTocId343308"></a>Moving an application</h2> Now suppose that you wish to redeploy the CCM application to it's own separate physical server (for example, ccmserver01.example.org) without affecting users' ability to access it through <span style="font-weight: bold;">https://clm.example.org/ccm</span>. Here is a summary of the steps, previously detailed, to be repeated:<br /> <ol> <li>Create and federate a WAS profile as in Step 2.1 on the new server.</li> <li>Create an Application Server on the new node using the clm_server_template as in Step 2.5.<br /></li> <li>Install the CCM application on the exact same location on the new server so that the template configuration remains effective.<br /> Follow the instructions in the <a href="https://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Fc_deploying_was.html"> CLM Infocenter</a>, making sure to copy over the directory that contains the indexes and configuration files, located at <JazzInstallDir>/server/conf/ccm for the <b>CCM</b> application from the original server.</li> <li>From <b>Applications</b> > <b>Enterprise Applications</b> > <b>ccm_war</b> > <b>Manage Modules</b>, select both the new application server definition and the application.</li> <li>Click <b>OK</b> and <b>Save</b> directly to the master configuration.</li> <li>Restart all the application servers and the proxy server.<br /></li> </ol> <p><br /></p> ---+++++!! Related topics: [[InstallProxyServers][Proxy server installation]], [[UnderstandingReverseProxy][Understanding reverse proxy]], [[ConfigureCLMEnterpriseReverseProxy][Configuring Enterprise CLM Reverse Proxies: WebSphere 8 and IHS 8]], [[ConfigureCLMEnterpriseReverseProxyWithApache][Configuring Enterprise CLM Reverse Proxies: Apache and mod_proxy]] ---+++++!! Additional contributors: Main.RosaNaranjo ---+++++!! Questions and comments: %COMMENT{type="below" target="ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxyComments" button="Submit"}% %INCLUDE{"ConfiguringEnterpriseCLMReverseProxiesWebSphere85NDProxyComments"}% <sticky></div></sticky>
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r20
|
r18
<
r17
<
r16
<
r15
|
More topic actions...
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.