Installing IBM Integration Designer silently using the command line

You can install IBM® Integration Designer using the command line.

Before you begin

Before you install IBM Integration Designer, review the system requirements for the product.

Operating system and software prerequisite levels are particularly important. Although the installation process automatically checks for prerequisite operating system patches, review the system requirements if you have not already done so. The system requirements link lists all supported operating systems and the operating system fixes and patches that you must install to have a compliant operating system. It also lists the required levels of all prerequisite software.

Important: If you are installing IBM Integration Designer with its test environment as a non-administrative or non-root user and you intend to install the test environment, you must install DB2 before you begin the product installation. The DB2 database must be locally installed.

About this task

If you do not have the prerequisite base products necessary for IBM Integration Designer installation, you must install them as part of the silent installation. The required base products are:

Installation Manager
WebSphere® Application Server Network Deployment (if you are installing the test environment)

The silent installation performs the following tasks:

Installs Installation Manager if it is not already installed or updates it to the appropriate level if it is installed.
Installs the required base products and IBM Integration Designer.

Procedure

To silently install IBM Integration Designer, complete the following steps:

Run the following command to generate encrypted passwords using IBM Installation Manager to securely connect to DB2.
Important: If you are running Windows 7, Windows Vista, or Windows Server 2008, start your command prompt by right-clicking and selecting Run as administrator.
```
IM_location\eclipse\tools\imutilsc -silent -nosplash encryptString password_to_encrypt
```
```
IM_location/eclipse/tools/imutilsc -silent -nosplash encryptString password_to_encrypt
```
Read and accept the license terms before installing. Adding -acceptLicense to the command line means that you accept all licenses.

Run the following command:

Important: If you are running Windows 7, Windows Vista, or Windows Server 2008, start your command prompt by right-clicking and selecting Run as administrator.

extract_directory\disk1\IM_win64\tools\imcl install list_of_package_IDs -acceptLicense 
  -installationDirectory location -repositories repository -showVerboseProgress -log logName.log

Note: If you already have 32-bit Installation Manager installed, then you can run the command from the extract_directory\IM_win32\tools directory.

extract_directory/disk1/IM_linux64/tools/imcl install list_of_package_IDs -acceptLicense 
   -installationDirectory location -repositories repository -showVerboseProgress -log logName.log

Note: If you already have 32-bit Installation Manager installed, then you can run the command from the extract_directory\IM_linux\tools directory.

where:

list_of_package_IDs is a list of the IDs for the products you want to install, separated by spaces.

Table 1. Package IDs
Product	Package ID	Feature	Description
IBM Integration Designer	com.ibm.integration.designer.v85	Required: com.ibm.wid, com.ibm.rad.jre, com.ibm.wid.product, com.ibm.rad.jee5, com.ibm.rad.was80_devtools, com.ibm.rad.was85_devtools, com.ibm.rad.j2c, com.ibm.rad.birt, com.ibm.rad.transform_authoring, and com.ibm.rad.pde	Required features
		Optional: com.ibm.wid.bpm.stubs	Tools for developing applications without a local server installation
		Optional: com.ibm.wid.adapters.file	Email, Flat File, FTP and JDBC IBM WebSphere Adapters
		Optional: com.ibm.wid.adapters.cics	CICS adapter
		Optional: com.ibm.wid.adapters.domino	Domino adapter
		Optional: com.ibm.wid.adapters.ecm	ECM adapter
		Optional com.ibm.wid.adapters.ims	IMS adapter
		Optional com.ibm.wid.adapters.ios	iSeries adapter
		Optional com.ibm.wid.adapters.jde	JD Edwards adapter
		Optional com.ibm.wid.adapters.oracleebs	Oracle adapter
		Optional com.ibm.wid.adapters.peoplesoft	PeopleSoft adapter
		Optional com.ibm.wid.adapters.sap	SAP adapter
		Optional com.ibm.wid.adapters.siebel	Siebel adapter
		Optional com.ibm.wid.adapters.wat	WebSphere Adapter Toolkit
		Optional com.ibm.wid.adapters.wola	WebSphere Optimized Local Adapter
		Optional com.ibm.wid.mme	Monitor Model editor (Windows only)
		Optional com.ibm.rad.webtools_core	Web development tools
		Optional com.ibm.rad.portal.v70.tools	WebSphere Portal Server Beta development tools
		Optional com.ibm.ram.core.client	Asset repository client
		Optional com.ibm.wid.dev_tools	Additional development tools
		Optional com.ibm.wid.bpmps.user	IBM Business Process Manager Advanced - Process Server environment
		Optional com.ibm.wid.bpmpc.user	IBM Business Process Manager Advanced environment
		Optional com.ibm.wid.wesb.user	WebSphere Enterprise Service Bus environment
		Optional com.ibm.wid.wbm.user	IBM Business Monitor environment (Windows only)
		Optional com.ibm.wid.datapower.user	WebSphere Datapower environment (Deprecated)
Installation Manager	com.ibm.cic.agent	agent_core	Installation Manager core content
Installation Manager	com.ibm.cic.agent	agent_jre	Installation Manager JRE

location is the path to the directory where you want to install the products.
repository is the path to the repository where you have extracted the files, one or more of the following directories:
```
extract_directory/disk1/IM_win64
extract_directory/disk1/IM_linux64
extract_directory/disk1/diskTag.inf
```
For more than one repository, separate the repository locations with commas.
logName is the name of the log file to record messages and results.

Running this command installs the product with the default features. If you want to install specific features or make other changes, see the reference link for the command-line arguments for imcl.

If you also want to install the test environment, run the same command again with a different installation directory and the required package IDs and keys:

extract_directory\disk1\IM_win64\tools\imcl install list_of_package_IDs 
    -acceptLicense -testInstallationDirectory location -repositories repository 
    -properties key=value,key=value -showVerboseProgress -log logName.log

Note: If you already have 32-bit Installation Manager installed, then you can run the command from the extract_directory\IM_win32\tools directory.

extract_directory/disk1/IM_linux64/tools/imcl install list_of_package_IDs 
    -acceptLicense -testInstallationDirectory location -repositories repository 
    -properties key=value,key=value -showVerboseProgress -log logName.log

Note: If you already have 32-bit Installation Manager installed, then you can run the command from the extract_directory\IM_linux\tools directory.

where:

list_of_package_IDs is a list of the IDs for the products you want to install, separated by spaces.

Table 2. Package IDs for test environment
Product	Package ID	Feature	Description
IBM Business Process Manager Advanced - Process Server	com.ibm.bpm.PS.v85	AdvancedProcessServer. NonProduction	Development, test, or staging use Must specify this feature or bpmAdvPS.prod
IBM Business Monitor	com.ibm.websphere.MON.v85	wbm.core.feature	IBM Business Monitor core runtime. Must always select this feature.
		wbm.server.feature	IBM Business Monitor server runtime. Must always select this feature.
		wbm.profile.feature	Stand-alone development Business Monitor profile (qmwas)
		wbm.wps.profile.feature	Stand-alone development Business Monitor on Process Server profile (qmbpmaps)
		wbm.esb.profile.feature	Stand-alone development Business Monitor on WebSphere Enterprise Service Bus profile (qmesb)
WebSphere Application Server Network Deployment	com.ibm.websphere.ND.v85	core.feature	Required WebSphere Application Server core content
		ejbdeploy	pre-EJB 3.0 modules
		thinclient	standalone thin clients and resource adapters
		embeddablecontainer	embeddable EJB container
		samples	sample applications feature
		com.ibm.sdk.6_64bit	64-bit SDK
Installation Manager	com.ibm.cic.agent	agent_core	Installation Manager core content
Installation Manager	com.ibm.cic.agent	agent_jre	Installation Manager JRE
DB2 for Linux	com.ibm.ws.DB2EXP.linuxia64	N/A	DB2 must match the system OS
DB2 for Windows	com.ibm.ws.DB2EXP.winia64	N/A	DB2 must match the system OS
IBM Cognos® Business Intelligence	com.ibm.ws.cognos.v1021.winia64	N/A	Must match the system OS

location is the path to the directory where you want to install the products.
repository is the path to the repository where you have extracted the files:
```
extract_directory/repository/repos_64bit
```
For more than one repository, separate the repository locations with commas.

key=value is a list of the keys and values you want to pass to the installation, separated by commas. Do not put spaces between the commas.

Table 3. Keys for test environment
Key	Description
user.db2.admin.username	Windows only. User name with authority to access the DB2 database. The default value is bpmadmin.
user.db2.admin.password	Windows only. Password for the user name above. Choose a password that complies with the password policy of your system (for example, Windows 2008).
user.db2.port	Port for the DB2 database. The default value is 50000.
user.db2.instance.username	Linux only. DB2 instance user name.
user.db2.instance.password	Linux only. Password for the user name above.
user.db2.fenced.username	Linux only. Fenced user name.
user.db2.fenced.password	Linux only. Password for the user name above.
user.db2.das.username	Linux only. Administration server (DAS) user name.
user.db2.das.password	Linux only. Password for the user name above.

logName is the name of the log file to record messages and results.

Running this command installs the test environment with the default features. If you want to install specific features or make other changes, see the reference link for the command-line arguments for imcl.

Results

Installation Manager installs the list of products and writes a log file to the directory that you specified.

What to do next

After you have installed the product, create the deployment test environment and profile using the BPMconfig command.