Example of end to end deployment using Quick Deployer
Authors: ClareCartyBuild basis: CE/CLM 6.0.4+.
This article describes the end to end process for using IBM Quick Deployer 2.0 to install and deploy an example IBM Continuous Engineering 6.0.4 topology on Websphere Application Server with a DB2 backend on Windows 2012 servers.
There are three main steps to this process: -
This is a Windows topology with a DB2 database. I’m going to modify it a bit and remove the DOORS/DWA piece since Quick Deployer doesn’t install those and I don’t need it anyway. I’m also going to use a Tivoli LDAP server since that’s what we’ve used to test Quick Deployer and I’m going to put DCC on the same server as the JTS. Note that this image is a bit out of date and VVC is no longer a separate app.
Netting this out, this gives us four server VMs: One IBM HTTPS reverse proxy server, one DB2 server, one WAS application server with LQE and one with all the other CE apps including JTS, CCM, QM, RM, RS, DCC, GC, LDX, RELM and DM.
I’m going to allocate 4 Windows 2012 VMs for these servers, each with 4 CPUs, at least 8G of RAM and minimum 100G hard drives. These will be my target VMs.
There are three other pieces I need to think about to prepare for my deployment: -
- Prepare: Decide what you are going to deploy and plan and assemble your bits and accounts.
- Setup: Setup your systems including installing Quick Deployer into UrbanCode Deploy, set up your media server (if used) with all the install bits, and set up your target VMs.
- Run: Run install Applications on Quick Deployer to install CE/CLM onto your target VMs.
A short word on accounts and URLS
The server URLs used here are not real and the accounts and passwords are also fictional but they are representative of real accounts and are used to give realistic examples.- For user accounts, I’m going to use MyUserPassword as the password, where needed it will be Base64 encoded as TXlVc2VyUGFzc3dvcmQ=
- For database accounts, I’m going to use MyDatabasePassword as the password, Base64 encoded as TXlE-YXRhYmFzZVBhc3N3b3Jk
Prepare
I’ve picked a small topology from the Recommended ALM topologies - this one: (ALM-D1) Departmental - Single application server / Windows / DB2:
This is a Windows topology with a DB2 database. I’m going to modify it a bit and remove the DOORS/DWA piece since Quick Deployer doesn’t install those and I don’t need it anyway. I’m also going to use a Tivoli LDAP server since that’s what we’ve used to test Quick Deployer and I’m going to put DCC on the same server as the JTS. Note that this image is a bit out of date and VVC is no longer a separate app.
Netting this out, this gives us four server VMs: One IBM HTTPS reverse proxy server, one DB2 server, one WAS application server with LQE and one with all the other CE apps including JTS, CCM, QM, RM, RS, DCC, GC, LDX, RELM and DM.
I’m going to allocate 4 Windows 2012 VMs for these servers, each with 4 CPUs, at least 8G of RAM and minimum 100G hard drives. These will be my target VMs.
There are three other pieces I need to think about to prepare for my deployment: - - Where the media – the zips and bits I’m going to install - are going to be.
- What LDAP server and accounts I’m going to use.
- What UrbanCode Deploy server I’m going to install Quick Deployer on.
Media Server
For media, I will need the bits for Websphere application server, DB2 install, IBM Installation Manager, IHS (IBM HTTP Server) and the install bits for CE/CLM. I’ve got a couple of options here. I could choose to download the media locally – that means downloading all the middleware and CE install zips on to each target VM. Or I could use an FTP media server that con-tains all the installers. [Note that mapped network drives aren’t supported for Quick Deployer on Win-dows]. For further details on the media server requirements you can check the Quick Deployer wiki. For simplicity, I’m going to use an existing ftp server that my team has set up with all the install bits. For the purposes of this article, I’m going to call it ftp://tompw7-qd-ftp01.ibm.com:2121/604/LDAP Server
Here I’m going to reuse the Tivoli Directory Server LDAP that we use in our Continuous Delivery pipeline. I would expect in any client environment that you would already have your own LDAP server setup to use with CE/CLM. I’m going to call this server https://clmpipeline.ibm.com for this article..UrbanCode Deploy Server
I’m going to use a new UCD server (https://ucd-15.ibm.com:8443/) and install Quick Deployer into it. The steps to install UCD are out of scope for this article but you can consult the UCD documentation for help. Quick Deployer is pushed into UCD using an installer script but there are some properties files that need to be edited before the installer is run and we’ll go through those in the Setup section. And that’s it, those are the main items I need to think about during the planning and preparation stage. Let’s move on to Setup now and start assembling our bits.Setup
First, I’ll prep my UCD Server for installing Quick Deployer.UrbanCode Deploy Server Setup
The UCD Server should have a recent version installed. For this demo I’m using 6.2.1.1.x. I’m just using the default admin account on UCD here for this article. I create an administration token using the admin account from UCD’s Settings tab. Quick Deployer’s installer uses this in qd.properties as the authentication token to install QD into UCD. * ucd_create_token.png:
Miscellaneous
Related topics: Deployment web home, Deployment web home
External links:
Additional contributors: TWikiUser, TWikiUser
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.