Note: AutoDeploy must be installed and started by the system user that operates Connections (e.g.: wasuser).
Note: If the HCL Connections installation is running on Windows, Cygwin must be installed on each node. You need to install the prepackaged Cygwin image that is provided here. Additionally, the AutoDeploy documentation provides a guide for setting up Cygwin.
Download the latest AutoDeploy release archive and upload it to the DeploymentManagers filesystem (e.g.: /tmp)
ssh <youruser>@target-machine ... sudo su - wasuser cd /tmp tar xfz autodeploy-5.0.4-73be5ee.tar.gz ./install-autodeploy.sh /opt/IBM/autodeploy
Start AutoDeploy
sudo su - wasuser /opt/IBM/autodeploy/app/console.sh --profilepath /path/to/WebSphere/AppServer/profiles/Dmgr01
If AutoDeploy is started for the first time, it exports all information of the cell. Afterwards, it needs to be configured by setting the stage attribute
vi-environment.xmi
Search the attribute stage and set a proper value (e.g. DEV, TEST, PROD)
<?xml version="1.0" encoding="ASCII"?> <autodeploy:Environment xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:autodeploy="http://environment.model.autodeploy" xsi:schemaLocation="http://environment.model.autodeploy java://autodeploy.model.environment.EnvironmentPackage" name="Connections-Cell" stage="DEV"> <cell name="Connections-Cell" adminUserId="wasadmin" adminPassword="{xor}Fz5pFQ8YMCYFKjdmFS8YNC1qazY=" wasVersion="6.1"> <customProperty name="com.ibm.websphere.management.launcher.options" value="displayServerInFront"/>
In order to ease the AutoDeploy startup, create an alias in the .bash_profile file of the wasuser
alias ad_start="/apps/autodeploy/app/console.sh --profilepath /path/to/WebSphere/AppServer/profiles/Dmgr01"
Ensure that all Pre-Installation steps are executed or verified.
If you created the DPTK server/cluster right after the AutoDeploy setup, the environment must be updated. Execute following AutoDeploy command to populate the created server to the AD environment:
ad_exportCell
Copy the DPTK deployment archive to the Deployment Managers filesystem (e.g.: /tmp)
Start AutoDeploy
sudo su - wasuser ad_start
Update the release configuration
ad_updateConfig /tmp/dptk.deployment-1.9.6-dist.zip vi-deploy.cfg
Note: If you install DPTK for the first time, AutoDeploy will ask for the following installation scope definitions. In most cases, the dptk-targetCell is cell. If this is not the case (or cell is not listed in the available scopes/multiple cell scopes are listed), find the target cell by navigating to the WebSphere cell configuration path: /path/to/WebSphere/AppServer/profiles/Dmgr01/config/cells. Here you should see the cell to define as your target cell. For the dptk-targetServer, use the cluster name set during the Pre-Installation.
WARN [main] autodeploy.releaseArchive.ReleaseArchive - Missing target-to-scope mapping for target [dptk-targetCell] Available scope: DPTKCluster, ICCluster, cell, connectionsCellManager, connectionsCellManager_dmgr, connectionsNode, connectionsNode_nodeagent, connectionsNode_webserver1 Please enter the corresponding scope for target [dptk-targetCell]: WARN [main] autodeploy.releaseArchive.ReleaseArchive - Missing target-to-scope mapping for target [dptk-targetServer] Available scope: DPTKCluster, ICCluster, cell, connectionsCellManager, connectionsCellManager_dmgr, connectionsNode, connectionsNode_nodeagent, connectionsNode_webserver1 Please enter the corresponding scope for target [dptk-targetServer]:
Search & Replace all values that are UNDEFINED
Note: Checkout the configuration page and verify if the default configuration values must be updated, or not
Validate the release
ad_validateRelease /tmp/dptk.deployment-1.9.6-dist.zip
Activate the maintenance mode
ad_maintenance -e "DPTK installation"
Deploy the release
ad_deployRelease --norestart /tmp/dptk.deployment-1.9.6-dist.zip
Note: Add the option --norestart in order to disable server restarts after the deployment has been finished.
Restart the DPTK cluster/server (execute ad_listServers for retrieving the cluser and server names)
ad_restartCluster DPTKCluster
or
ad_restartServer DPTKCluster_server1@?
Note: If it is an initial installation the webserver plugins must be generated and propagated
Ensure that all Post-installation Tasks steps are executed or verified. Refer to this document for first steps as well.