Installing WebSphere Commerce Developer silently

You can install WebSphere Commerce Developer by using a silent response file.To install silently, IBM Installation Manager requires a response file to provide the input.

Before you begin

Complete the following tasks:

Ensure that the machine on which you are installing WebSphere Commerce Developer meets all prerequisites. For more information, see Installing IBM WebSphere Commerce Developer prerequisites
Ensure that Rational Application Developer Version 9.5 Fix Pack 1 (9.5.0.1) is installed. For information about installing Rational Application Developer, see Installing Rational Application Developer or Rational Software Architect Version 9.5 or 9.6.
Ensure that WebSphere Application Server Version 8.5.5 Fix Pack 7 is installed. For information about installing WebSphere Application Server, see Installing and preparing WebSphere Application Server.
Stop any applications that are running on your machine.
Disable any Web server that is on your machine.
Ensure that you are logged on as a user with Administrator privileges.
Insert the WebSphere Commerce Developer DVD in the DVD-ROM of the Rational Application Developer machine.

Procedure

Create a response file:
If you already have a response file, skip to Step 4.
1. Copy the contents of the following directory to a temporary, writable directory (the agent_data_location).
  - drive:\Program Files\IBM\Installation Manager
    Note: If the path names are too long, you might need to use the XCOPY command to copy the files.
  For example, the agent_data_location can be C:\temp_agent_data. This folder is used by the IBM Installation Manager to read and write information about the installation that you are recording. For the IBM Installation Manager to detect previous Rational Application Developer installations, the agent_data_location must contain this copied data.
2. On a command line, go to the eclipse subdirectory in the directory where you installed IBM Installation Manager.
  For example, drive:\Program Files\IBM\Installation Manager.
3. Run the IBM Installation Manager by using one of the following commands to create a response file:
  Note: Ensure that you enter a file path that exists. Installation Manager does not create directories for the response file and the log file.
  - To create the response file and install the product:
```
IBMIM –record response_file_path
```
    For example, IBMIM –record C:\temp_agent_data\installresponse.txt.
  - To create the response file only:
```
IBMIM –record response_file_path -skipInstall agent_data_location 
```
    - The agent_data_location must be a temporary writable directory, such as c:\temp_agent_data.
    For example, IBMIM –record C:\temp_agent_data\installresponse.txt -skipInstall C:\temp_agent_data
  The Installation Manager starts.
4. Follow the steps in Installing WebSphere Commerce Developer by using the IBM Installation Manager to make your installation choices.
  
  Remember: Ensure that you set the repository preferences to the location of the WebSphere Commerce Developer installation image during the recording of the response file.
5. Click Finish, then close Installation Manager to save and finalize the response file.
Optional: Open the response file that you created, response_file_path, in a text editor.
Optional: Modify the entries in the response file to match the installation options you want.
On the command line, run the following command to start the silent installation process:
1. Go to the eclipse/tools subdirectory of Installation Manager.
2. Run the following command.
```
imcl.exe -input response_file_path -log log_file_path -acceptLicense
```
  Note: Add the -sP parameter to obtain more installation progress information.
Where:
- response_file_path is the full path of the response file.
- log_file_path is the full path of log file, for example c:\logs\fep_install.log. The full path must exist.
Ensure that the installation was successful:
- Examine the contents of WCDE_installdir/logs/setup.log for the results of setup.bat. This script creates the WebSphere Commerce Developer workspace.
  If errors appear in the setup.log file, examine the WCDE_installdir/bin/setup.bat file. Ensure that the RAD_HOME environment variable points to the correct Rational Application Developer installation location.
- Check the log that you specified by using -log in Step #4 to see whether there are any errors or warnings. If the log file for the -log parameter is empty, then the installation was successful. For example,
```
<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>
```
  You can also review the IBM Installation Manager log files for any important information or errors. The timestamped logs can be found in the following default locations.
  - drive:\Program Files\IBM\Installation Manager\logs
  Alternatively, you can view the logs in the IBM Installation Manager interface under File > View Log.
Note: You might notice java.lang.RuntimeException: Unable to aquire PluginConverter service during generation errors in the setupPlugins.log file. You can safely ignore these errors.
For example: C:\Documents and Settings\Administrator\Local Settings\Temp\wc_toolkit.log
Update WebSphere Application Server to Fix Pack 8.5.5.22 or greater.
Update WebSphere Commerce Developer to the latest maintenance package, WebSphere Commerce Version 8 Mod Pack 4 Fix Pack 30 (8.0.4.30).
For more information, see
- List of available maintenance packages.
- Installing maintenance for WebSphere Commerce Developer.
Optional: If you installed IBM WebSphere Commerce Developer Version 8.0 on a machine that also has IBM WebSphere Commerce Developer Version 7.0, Version 8 replaces any Version 7.0 Windows shortcut icons. Create new shortcuts for IBM WebSphere Commerce Developer Version 7.0 if necessary.

What to do next

If needed, you can change the development database type.
Important: If you are migrating WebSphere Commerce Developer from a previous version, ensure that you use the same database type in your new development environment. To change the development database type to prepare for migration, see Changing the development database type by using the setdbtype command.