This article shows an examplar IBM UrbanCode Deploy process that can be used to automate the installation and setup of IBM Collaborative Lifecycle Management on a single server. The process also automates the installation of IBM WebSphere Application Server, and of a reverse proxy based on IBM HTTP Server.
Introduction
Topology
There are three machines in this topology:
- VM1: contains the installation of IBM UrbanCode Depoy server and one agent used for version imports
- VM2: contains the installation of IBM WebSphere Application Server, IBM Collaborative Lifecycle Management and one agent
- VM3: contains the installation of IBM HTTP Server and one agent
All machines run the Linux Operating System. The agents can run as root or as a normal user. This will determine how Installation Manager and all the products will be installed. UrbanCode Deploy impersonation using su or sudo is not supported by this process design.
Prerequisites
IBM UrbanCode Deploy processes can only be imported on exactly the same server version and plug-ins.
The attached Application process was developed on this configuration:
The following additional products were used:
It is assumed that the machines VM2 and VM3 can access the repositories where the Installation Manager repositories are located. The repository locations need to be specified as Component Environment properties as described below.
It is assumed that the machines have proper ulimits set before launching the installation process. See:
Planning to install on UNIX and Linux systems.
How to use this process
To use this process, proceed as follows:
- Make sure that you have installed the exact versions of the plugins named above
- From the Application page in UrbanCode Deploy, import the Application JSON file
- Add two agents to the Application Environment
- Add the following components to the agent on VM2:
- InstallationManagerComponent
- CLMPackageComponent
- WASPackageComponent
- OracleDriver
- WASProfile
- WASCompleteConfigForCLM
- JTSSetup
- Add the following components to the agent on VM3:
- InstallationManagerComponent
- IHSPackageComponent
- Unzip the attached workspace.zip so to create the directory
/workspace
. If you want to change this path, you will have to adjust it in the Configuration tab of each component.
- Download the IBM Installation Manager 1.8.0 installer and copy it to:
/workspace/InstallationManager/1.8.0/agent.installer.linux.gtk.x86_1.8.0.20140902_1503.zip
- Import versions of all the components
- Set up the following Environment variables:
LDAP.password |
|
LDAPJazzAdmins |
|
LDAPJazzDWAdmins |
|
LDAPJazzGuests |
|
LDAPJazzProjectAdmins |
|
LDAPJazzUsers |
|
OraclePassword |
|
WASNodeName |
WASNode01 |
WASPassword |
|
WASUser |
wasadmin |
WASProfileName |
AppSrv01 |
WASServerName |
server1 |
and the following Component Environment properties, that refer to the Installation Manager Repositories from which to install CLM, WebSphere Application Server and IBM HTTPS Server.
Process design principles
Detailed process design
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text
Heading 1
External links: