Forms Experience Builder 8.5 Cluster Guide

Preface Authored by: Celine Hall ([email protected]) IBM Forms Level Two Support Team Lead IBM Canada Software Lab, Victoria, BC This guide describes a comprehensive procedure for installing, configuring, and building an IBM Forms Experience Builder v8.5 cluster using:  WebSphere Application Server Network Deployment 8.0.0.6  IBM WebSphere Application Server Multiplatform 8.0.0.6  IBM HTTP Server 8.0.0.6  DB2 10  Forms Experience Builder 8.5 This guide is specifically written for 64-bit IBM Forms Experience Builder and WebSphere Application Server 8.0.0.6. The same approach will apply to any IBM Forms Experience Builder v8 and up 32-bit and WebSphere Application Server 8.0.x 32-bit versions.

September, 2013 © Copyright International Business Machines Corporation 2013. All rights reserved.

Table of Contents Forms Experience Builder 8.5 Cluster Guide ..................................................................... 1 Preface................................................................................................................................. 2 Table of Contents................................................................................................................ 3 Introduction......................................................................................................................... 4 Before you begin................................................................................................................. 5 Part Numbers .................................................................................................................. 5 Items not covered ............................................................................................................ 5 IBM Installation Manager Defining Repositories............................................................... 6 Installing WebSphere Application Server Deployment Manager, IBM HTTP Server, and 8.0.0.6 updates .................................................................................................................... 7 Creating a Profile .......................................................................................................... 14 Creating a second node ..................................................................................................... 18 Create a cluster.................................................................................................................. 20 DB2 setup for Forms Experience Builder (FEB).............................................................. 22 Configure WAS prior to the FEB installation................................................................... 22 Configure the IBM HTTP Server ..................................................................................... 28 Deploy IBM Forms Experience Builder 8.5 ..................................................................... 34 Configure the Builder_Config.properties ......................................................................... 37

Introduction There are multiple ways to set up a cluster environment to run the Forms Experience Builder. The determination on the way in which the cluster is configured always depends on the business need. In a typical production environment, the topology is divided into two large sections: Front End and Back End

Before you begin Prior to installing the Forms Experience Builder to the managed note there are preparation steps that you need to complete. This guild assumes the use of WebSphere Application Server Deployment Manager 8.0.0.6, IBM HTTP Server 8.0.0.6, DB2 9.7, and IBM Forms Experience Builder 8.5.

Part Numbers Installation Manager **required to Install WebSphere Application Server V8.0  CZM90ML IBM Installation Manager for Windows x86 IBM WebSphere Application Server 8.0.0.6  CZM9KML IBM WAS Network Deployment V8.0 (1 of 4)  CZM9LML IBM WAS Network Deployment V8.0 (2 of 4)  CZM9MML IBM WAS Network Deployment V8.0 (3 of 4)  CZVG4ML IBM WAS Network Deployment V8.0 (4 of 4) IMPORTANT: All parts of this image (CZM9KML, CZM9LML CZM9MML and CZVG4ML) must be extracted into the same directory to create a local repository IBM WebSphere Application Server V8.0 Supplements Multiplatform Multilingual Includes IBM HTTP Server V8.0 and Plugins V8.0  CZM91ML - IBM WAS v8.0 Supplements (1 of 4)  CZM94ML - IBM WAS v8.0 Supplements (2 of 4)  CZM95ML - IBM WAS v8.0 Supplements (3 of 4)  CZXR9ML - IBM WAS v8.0 Supplements (4 of 4) DB2 v 10.1

Items not covered This document does not include steps for installing the following:  IBM Installation Manager  DB2 IBM Forms Wiki Information Center: http://www-10.lotus.com/ldd/lfwiki.nsf **Note: to perform the tasks described in this document, you need basic IBM WebSphere Application Server knowledge and administration skills.

IBM Installation Manager Defining Repositories This document assumes that you have the IBM Installation Manager installed. 1. Unzip the four part numbers for IBM WebSphere Deployment Manager (CZM9KML, CZM9LML, CZM9MML, CZVG4ML) into one directory. For example: C:\ibm\installers\DM\ 

Unzip the four part number for IBM HttpServer (CZM91ML, CZM94ML, CZM95ML,CZXR9ML) into one directory. For example: C:\ibm\installers\WAS\WAS

2. Unzip the Fixpack 8.0.0.6 fixes (8.0.0-WS-WAS-FP0000006-part1.zip- 8.0.0-WSWAS-FP0000006-part1 and 8.0.0-WS-WAS-FP0000006-part2.zip into one directory For example: C:\ibm\installers\WAS\updates\part1and2 3. Unzip 8.0.0-WS-WASSupplements-FP0000006-part1.zip and 8.0.0-WSWASSupplements-FP0000006-part2.zip, 8.0.0-WS-WCT-FP0000006.zip) into one directories. For example: C:\ibm\installers\WAS\updates\supplements\part1and2 4. Unzip 8.0.0-WS-WCT-FP0000006 into one directory. For example: C:\ibm\installers\WAS\updates\WS-WCT_FP6 NOTE: The CD numbers may vary between operating systems. 5. Open the Installation Manager and navigate to File > Preferences > Repositories 6. Add the repositories for the IBM Websphere Deployment Manager, IBM Http Server, and the IHS Plug-ins for example: C:\ibm\installers\DM\ repository.config C:\ibm\installers\WAS\WAS \repository.config C:\ibm\installers\WAS\updates\suplements\part1and2 C:\ibm\installers\WAS\updates\WS-WCT_FP6

7. Click OK and save your changes NOTE: The CD numbers may vary between operating systems.

Installing WebSphere Application Server Deployment Manager, IBM HTTP Server, and 8.0.0.6 updates 1. Open the IBM Installation Manager Start > All Programs > IBM Installation Manger > IBM Installation Manger. Once the dialog appears click Install.

2. Select all packages for installation; Application Client for IBM WebSphere Application Server, IBM HTTP Server for WebSphere Application Server, IBM WebSphere Application Network Deployment, Pluggable Application Client for IBM WebSphere Application Server, Web Server Plug-ins for IBM WebSphere Application Server, WebSphere Customization Toolbox.

3. Accept the licensing agreement and click Next.

4. Select the install location for the shared resources directory. Here we kept the default location. Click Next.

5. Define the installation directory for the WebSphere Application Client for WebSphere Application Server. Here we left the default location. Click Next.

6. Select the language and click Next.

7. Select the features to install. Here you see the default screen. Click Next.

8. Define the configurations for the packages. Here we left the defaults; however, for a production environment you will need to define the host name and port configuration.

9. Define the host name and bootstrap port number. In this screen, we are leaving the defaults. You will want to define the host name of your server. Click Next.

10. Define the location of Sun Java Runtime Environment. The installation requires a minimum of JRE 1.6. Click Next.

11. Fill in the configurations for the packages for the Application Client. For this installation we selected the defaults; however, for a production server you will want to define the host name and bootstrap port number for your server.

12. Review the install summary and click Install.

13. Click Finish to start the Profile Management Tool to Create a profile.

Creating a Profile a. From the WebSphere Customization Tool box click Create.

b. Highlight Cell (deployment manager and a federated application server) and click Next.

c. Select “Typical profile creation” and click Next.

d. Add the username and password for the administrative security and click Next.

e. Review the profile creation summary and click Create.

f. When the profile creation completes click the “Launch the First steps console” and click Finish.

g. To ensure the installation was successful you should see the confirmation on the command line generated.

Creating a second node 1. Create a new profile from the WebSphere Customization Toolbox. 2. Click Create > Select Typical profile creation > Click Next

3. Click Create

4. Federate the new profile with the DMGR. From the Deployment manager navigate to System administration > Nodes 5. Click Add Node 6. Select Managed node, click Next 7. Fill in the text fields as shown below, the default JMX connector port is 8880; however, in a custom environment this may be different. Click OK.

**You can verify the Dmgr port by navigating to System administration > Deployment manager > Ports.

** For additional nodes repeat steps 1 – 4. You can also run the addNode command from the new profiles bin directory. For example: addNode.bat addNode.bat l2vm103.canlab.ibm.com 8879 8. You have the option to run the nodeagent as a windows service. If you would like to run the node agent as a windows service click the checkbox and add the username and password. When you run the addNode command, you will not be provided with this option.

Create a cluster 1. After all the nodes servers are added to the Dmgr, navigate to Servers > Clusters > WebSphere application server cluster and click New. 2. Provide a name for the cluster. In this scenario I’ve used FEB_Cluster

3. Create the first cluster member, add the name of the member. In this example we used FEB_nodeserver1. 4. Click the radio button beside “Create the member using an existing application server as a template. Click Next.

5. For additional members, provide the member name (FEB_nodeserver2), Click Add Member button in the center of the page. Click Next.

6. Follow steps 1 – 5 for additional nodes.

7. Resynchronize the nodes by navigating to System administration > Nodes, check all the node servers and click Full Resynchronize.

DB2 setup for Forms Experience Builder (FEB) In a production environment, you must create DB2 database before you install IBM® Forms Experience Builder to WebSphere® Application Server. Note: Do not create a database if you want to continue using the same database with the existing user content. To set up the DB2 database: a. Create an empty DB2 database with a maximum database name of 8 characters, and a maximum page size of 32768. For example: db2 "CREATE DB FEBDB using codeset UTF-8 territory us PAGESIZE 32768" b. Connect to the database and create a User Temporary table space. Use the following settings for the temporary table space:  Large_usertemp pagesize 32K  Managed by automatic storage extentsize 16  "bufferpool-name" is the name of your DB2 large buffer pool. Each DB2 server can have a different name. For example: db2 "CREATE USER TEMPORARY TABLESPACE LARGE_USERTEMP PAGESIZE 32k MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL bufferpool-name"

Configure WAS prior to the FEB installation 1. You must enable security in WebSphere Application Server before you install Forms Experience Builder. To enable security, open the WebSphere Application Server Integrated solutions console. a. Expand the Security tree and select Global security. b. In the Administrative security section, select the check box for Enable administrative security. c. In the Application security section, select the check box for Enable application security. d. In the User Account Repository, ensure Current Realm Definition is set to Federated repositories. e. Click Apply to apply your changes. f. You must restart WebSphere Application Server after security is enabled.

2. To begin the installation, extract the software package. Run the Launchpad file for your platform. For Windows, use Launchpad.exe or Launchpad64.exe for 64bit Windows platforms. For Linux and AIX®, run launchpad.sh.

3. Note: In some Windows environments, it might be necessary to right-click Launchpad and select Run as Administrator to start IBM Installation Manager correctly. 4. Click Install in the Product Overview section. 5. Launchpad detects the presence of IBM Installation Manager, which is a wizardbased installation program that is used in many IBM products. Launchpad uses your current version of IBM Installation Manager and add the Forms Experience Builder repository automatically.

6. In the IBM Installation Manager window, click Next to install the packages for IBM Installation Manager, if you did not install it, and Forms Experience Builder. 7. Click Next and read the license agreement.

8. Read the license agreement, click I accept the terms in the license agreement radio button, and then click Next. The Select Installation Directory panel opens. 9. Select the location for the shared files and click Next. Select the directory for the Forms Experience Builder installation, and click Next.

Note: Use a short installation path. For example, use C:\FormsExperienceBuilder instead of C:\Program Files\IBM\FormsExperienceBuilder. If you exceed the 259 maximum character length, you may receive one of the following error messages during configuration or in the IBM Installation Manager log files:  The input line is too long.  The syntax of the command is incorrect.  The file name is too long. 10. Select the features that you want to install with Forms Experience Builder.  For a production environment, you must select Install IBM Forms Experience Builder with WebSphere Application Server.  For a non-production environment, select Install IBM Forms Experience Builder with WebSphere Application Server Community Edition.  To install a Forms Experience Portlet on WebSphere Portal, Install IBM Forms Experience Portlet on existing WebSphere Portal.  To install a version of Forms Experience Builder that is integrated with Connections, choose Install IBM Forms Experience Builder Connections Integrator.

11. Enter and validate the properties for your WebSphere Application Server, your database, and your mail server. Click Next





If you are integrating with WebSphere Portal, your server must be running, and you must enter the properties for it after you configure your database and mail server. If you are integrating with Connections, you must also enter the properties of the Connections server you are using.

2. A summary screen is shown. Confirm the information that is shown is correct, and click Install. Forms Experience Builder is installed into the specified directory on your system. When installation is complete, click Finish to close the installer.

Configure the IBM HTTP Server 1. Start the Web Server Plug-ins Configuration Tool. Start > All Programs > IBM WebSphere > WebSphere Customization Tool > Tools > Web Server Plug-in Configuration Tool. 2. Highlight the Web Server Plug-in and click Create.

3. Select the Server to configure. In this case we are configuring the IBM HTTP Server.

4. Select the existing IBM HTTP server httpd.conf file.

5. Create a user ID for the IBM HTTP Server Administration server authentication.

6. When the dialog Non-Administrative user configuration limitation appears, click Next.

7. Define the name of the Web Server. Here we are using the default name. Click Next.

8. Define remote or local host. For a production environment, this should be on a separate server and therefore you would select he remote configuration. Click Next.

9. Define the profile where the web server will be configured and click Next.

10. Review the summary and click Configure.

11. When the installation completes, click Finish.

12. From the command prompt, navigate to C:\IBM\WebSphere\Plugins\bin. Look for a script file with the name you gave the HTTP server in the previous step. The syntax of the file will be as follows: configure .bat (ie. configurewebserver1.bat) 13. Copy the bat file to the WAS server location C:\IBM\WebSphere\AppServer\bin 14. From C:\IBM\WebSphere\AppServer\bin run the configurewebserver1.bat file to automatically configure the HTTPServer with the WebSphere Application Deployment Manager (DMGR). 15. Log into the WebSphere Application Server administration console and navigate to Servers > Server Types > Web servers to verify the webserver1 is configured correctly.

16. Select the checkbox beside webserver1 and click Generate Plug-in 17. Select the checkbox beside webserver1, and click Propagate Plug-in 18. Restart IHS. 19. Continue navigating to Plug-in properties > Request routing and confirm the load balancing option is set to RoundRobin

20. Save the changes.

Deploy IBM Forms Experience Builder 8.5 1. Navigate to Applications > WebSphere enterprise Application > Forms Experience Builder > Manage Modules 2. Select the FEB cluster and webserver1 and click Apply

3. Resync the nodes by navigating to the System administration > nodes. Select the checkbox for your nodes and click Full Resynchronize. 4. Open the Forms Experience Builder URL. http://:/forms a message appears stating the IBM Forms Experience Builder is not completely setup. Until that occurs, all normal requests are disabled. Click on Setup to start the setup process. 5. If you get a message stating the database tables have not been created. Click fix.

6. Click Continue to Secured Setup. Log into FEB when prompted and use the WASadmin username and password to log in. When the configuration completes click Continue to Manager.

Configure the Builder_Config.properties When you install IBM® Forms Experience Builder, a Builder_Config.properties file containing sample configuration properties is also installed. You can configure the properties for optimal performance with your system. 1. Navigate to C:\ibm\Forms\extensions deploy and open the Builder_Config.properties in a text editor. 2. Open the Builder_Config.properties and configure the settings to match your system. For the purpose of this guide, we will configure the serverURI to ibm.nitro.NitroConfig.serverURI = http://l2vm103.canlab.ibm.com/forms ** Remember to uncomment the property by removing the hash tag # at the start of the line. Details of the configuration properties can be found at http://www10.lotus.com/ldd/lfwiki.nsf/xpDocViewer.xsp?lookupName=Forms+Experience+Builder +8.5+documentation#action=openDocument&res_title=Configuration_properties_FEB_8 50&content=pdcontent Test the URL listed in the Builder_Config.properties to confirm all the configurations were followed correctly.