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 188.8.131.52 fixes (8.0.0-WS-WAS-FP0000006-part1.zip- 8.0.0-WS-WAS-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-WS-WASSupplements-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_FP6NOTE:
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:
7. Click OK and save your changes
The CD numbers may vary between operating systems.
Installing WebSphere Application Server Deployment Manager, IBM HTTP Server, and 184.108.40.206 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 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"
Installing Forms Experience Builder 8.5 in a 2-node cluster - Table of Contents