Quick Info
Description
The WebSphere Commerce plug-in enables you to do the following on the WebSphere Commerce cells: Download, configure and deploy a server deployment package to a WebSphere Commerce server. Use this plugin to deploy customizations to a WebSphere Commerce instance. This plugin does not provide installation or configuration processes for WebSphere Commerce.Quick Info
6.1100872 
Summary
Usage
StepsSummary
The WebSphere Commerce plugin includes steps to install, configure, and deploy a server deployment package to a WebSphere Commerce server on a WebSphere Commerce cell.
A typical deployment includes the following procedures:
- Create resources. To deploy a server deployment package to a WebSphere Commerce server, you must populate resources manually. You can view the resources that you create in the Resources view. Each resource corresponds to the WebSphere Commerce server.
- Define components, applications, and environments to automate deployment.
- Deploy.
This plugin includes one or more steps, click Steps for step details and properties.
Compatibility
This plugin also requires version 80 or later of the WebSphere Application Server Deployment plugin.
The HCL Launch plugin for WebSphere Commerce works with WebSphere Commerce versions 7.0 and earlier. All editions are supported, including the Express, Enterprise and Professional editions.
The steps in this plugin run on any agents that the HCL Launch server supports.
Installation
See Installing plugins in HCL Launch for installing and removing plugins.
History
The following table describes the changes made in each plugin version.
| Version | Description |
|---|---|
| 6 | Minor enhancements |
Usage
To use the WebSphere Commerce plugin the HCL Launch agent must be installed on the system that hosts the WebSphere Commerce server.
To create resources and define deployment processes for use with commerce servers, complete the following steps.
- In HCL Launch, create a resource that represents the WebSphere Commerce server.
- Add the agent that is installed on the system hosting the WebSphere Commerce server to the resource group.
- Hover over the row for the resource group, and then click Actions > Add agent.
- Create components for the resources. Create one component for each resource to deploy. Specify the Deployment type for the component process.
- Add the components to the resource.
- Navigate to the resource.
- Click Actions > Add Component, and then select the component to use.
- Create an application.
- Navigate to the Applications page.
- Click Create Application. (You can also use an existing application that is attached to the cell to manage.)
- Enter an application name, and then click Save.
- Click the Components tab, and then add the component that was created in the previous step.
- Create an application environment.
- On the Resources page, click Create New Environment.
- Enter an environment name, and then click Save.
- Navigate to the environment editing page.
- Click the environment name, and then click Add Base Resource. Select the group for the Process Center environment.
- Create an application process of the Deployment type.
- Click the Processes tab.
- Add a deploy step.
- Drag and drop the Install Component step onto the process editor.
- Select the component that you created for the resource. For example, select the component that contains the process application to deploy.
- Select the process for the component. For example, select Profit Margin package deployment process.
- Click Save.
- Run the process to test the new component.
Step palette
To access this plugin in the palette, click Application Server > Java > Commerce > WebSphere Commerce.
Steps
The following process steps are available in the WebSphere Commerce plugin.
- Configure server deployment settings (Deprecated)
- Install server deployment package (Deprecated)
- Run server deployment process
Configure server deployment settings (Deprecated)
Configures the customization package deployment settings (Deprecated)
| Name | Type | Description | Required |
|---|---|---|---|
| ANT home | String | The ANT installation directory on the runtime machine | No |
| Deployment settings | String | Comma separated list of properties to apply as deployment settings. Each property must be of the form propName=propValue. | Yes |
| Deployment settings private properties file | String | The name of the properties file that contains runtime server user credentials | No |
| Deployment settings properties file | String | The name of the properties file corresponding to the deployment settings | No |
| Private deployment settings | String | Comma separated list of properties to apply as private deployment settings. Each property must be of the form propName=propValue. | No |
| Target Environment/Customization name | String | The name of the customization to deploy. This is also referred to as the Target Environment. | Yes |
| WAS home | String | The WAS installation directory on the runtime machine | No |
Install server deployment package (Deprecated)
Extracts the customization package archive (ZIP) on the target machine (Deprecated)
| Name | Type | Description | Required |
|---|---|---|---|
| Build Label | String | The build label or name of the customization to deploy | Yes |
Run server deployment process
Triggers the customization package deployment process on the target machine
| Name | Type | Description | Required |
|---|---|---|---|
| ANT build script | String | The name of the ANT built script file containing the deployment instructions | No |
| ANT executable | String | The name of the ANT executable | No |
| Deployment batch or script file | String | The name of the batch file or the script file that triggers the deployment | No |
| Target Environment/Customization name | String | The name of the customization to deploy. This is also referred to as the Target Environment. | Yes |
Related Plugins
Automation , Continuous Deployment 
