Installation

Installation: Installing Websphere Commerce Server involves below steps:

Downloading Websphere Commerce: Go to Passport Advantage site http://www.ibm.com/software/howtobuy/passportadvantage/

Ø  Websphere Commerce eAssemblies: Websphere Commerce product consists of multiple offerings such as Professional, Express and Enterprise. Each offering logically divided into subpackages which are called electronic Assemblies or eAssemblies. It’s a group of software devoted to a particular platform or environment.


For e.g.



Ø  Checksum verification for e-Assemblies.
Ø  Verify the download package verifying md5 sum
Ø  Burning backup copies of Websphere Commerce : DVDs. 

Installing WebSphere Commerce Developer: There are 2 types of installation options available depending on the size of organization.
-          Setting up a common central repository which can be used by multiple identical development environment
-          Install Websphere Commerce Developer on each individual workstation.

Setting up a common central repository: Involves:
Ø  Overview of IBM Packaging utility
Ø  Creating a central repository
Ø  Making central repository available over local internet
Ø  Maintaining the central repository
Ø  Installing software onto multiple developer workstations.

Overview of IBM Packaging utility:
It is used to copy software package repository from various sources (like CD/DVD or Internet) on servers. It can also copy latest fix packs and fixes of packages onto servers.
Download the packaging utility (http://www.ibm.com/support/docview.wss?uid=swg24028744 ) onto the host where we need central repository to be present  and run install.exe
Creating Central Repositry:
Ø  Using eAssemblies:
o   Download following product eAssemblies from IBM Website to the server
§  RAD v7.5.4
§  WAS Test Environment (WTE) v7.0
§  Websphere Commerce Developer Version v7.0
§  Most recent fix and feature pack.
o   Extract each package to temp location
o   Download latest version of IIM and extract it to temp location
o   Procedure:
§  Run IBM Packaging utility
§  Click copy packages
§  Click open repository
§  Browse to IIM installation location and select repository.config and click OK
§  Add RAD v7.5.4 and WTE v7.0 (RAD_WTE_image_location\RAD_SETUP and select diskTag.inf) and click OK.
§  Add Websphere Commerce Developer v7.0 (WCDE_image_location and select repository.config) and click OK
§  Add fix pack (FP_image_location and select repository.config) and click OK
§  Add feature pack (FEP_image_location\developer and select repository.config) and click OK
§  Select all the required products necessary
§  Click Next
§  Accept the licence agreement
§  Select location on server where we need to install Central Repository
§  Click Next
§  Review Summary page and click on COPY
§  Finish J

Ø  Using Physical Media:
o   Download following product eAssemblies from IBM Website to the server
§  RAD v7.5.4
§  WAS Test Environment (WTE) v7.0
§  Websphere Commerce Developer Version v7.0
§  Most recent feature pack.
§  Fix pack are not available in Media so we need to download them explicitly from IBM Website
o   Procedure:
§  Insert the CD/DVD
§  Run IBM Packaging utility
§  Click open repository
§  Browse to IIM installation location and select repository.config and click OK
§  Add RAD v7.5.4 and WTE v7.0 (RAD_WTE_image_location\RAD_SETUP and select diskTag.inf) and click OK.
§  Select all required products -> Click next
§  Review licence agreement and click Accept
§  Select a location on the server where you want to create the central repository-> Next
§  Review the summary page and click Copy to begin creating the central repository. Insert appropriate disks as prompted by the utility.
§  After the repository is successfully created, click Finish and close the IBM Packaging Utility.
§  Insert the DVD for WebSphere Commerce Developer V7.0 
§  Click copy packages
§  Open repository
§  Add Websphere Commerce Developer v7.0 (WCDE_image_location and select repository.config) and click OK
§  Add fix pack (FP_image_location and select repository.config) and click OK
§  Add feature pack (FEP_image_location\developer and select repository.config) and click OK
§  Select all the required products necessary
§  Click Next
§  Accept the licence agreement
§  browse to common_repo and click Next
§  Review summary page and click Copy
§  Click finish
§  Insert DVD for feature pack
§  Copy packages
§  Open repository
§  Add Websphere Commerce Developer feature pack
§  Select all the required products necessary
§  Click Next
§  Accept the licence agreement
§  browse to common_repo and click Next
§  Review summary and click on Copy
§  Finish

Maintaining Central Repository: It includes below features:
Ø  Adding new software packages: It can come in DVD or a zip file. Insert CD/DVD to the central repos server or extract zip file on central repos server and extract it
o   Run IBM Packaging utility
o   Copy packages
o   Open repository
o   Browse to diskTag.inf or else repository.config and click on OK
o   Ensure the correct version of software is being selected
o   Click Next
o   Review summary page and click on Copy
o   Finish

Ø  Removing Software packages
o   Run IBM Packaging utility
o   Copy packages
o   Open repository
o   Browse to repository.config and click on OK
o   Select the products which you need to delete and click Next
o   Review summary page and click on delete
o   Finish

Ø  Adding updates:
o   Run the IBM Packaging Utility.
o   Click Copy Packages.
o   Click Open Repository.
o   Browse to the location of your central repository, select repository.config, and click OK.
o   Select the software package that you wish to update and click Check for Updates.
o   The utility will display the latest version available for the selected product. If you wish to see all versions available, select the Show All radio button.
o   Select the version you want to add to the central repository and click Next.
o    Review any license agreements and click Accept.
o    Browse to the location of your central repository.
o    Click Next.
o    Review the summary page and click Copy to begin creating the central repository. Insert appropriate disks if prompted by the utility.

o    Once successful, click Finish and exit the utility.


Installing software onto Multiple Developer Workstation:
Ø  Installing Software using IIM
o   Launch IIM
o   Menu -> File Preferences
o   Click on Add Repository -> Enter URL to repository
o   Ensure that repository you added is selected and click on OK
o   Click Install

Ø  Installing software using Enterprise Deployment Utility: It quickly replicates a custom Websphere Commerce installation onto multiple workstations. It can
o   Install WebSphere Commerce Developer Version 7
o   Install and enable the latest fix pack and feature pack
o   Include custom projects in the workspace.

Setting up the Enterprise Deployment Utility:

 

Ø  Download and install latest version of IIM

o   Change the default installation location of IIM. Open the IM_UNZIP/install.xml and insert below element:

<profile kind='self' installLocation='IM_HOME' id='IBM Installation Manager'>
<data key='eclipseLocation' value='IM_HOME\eclipse'/>
</profile>

IM_HOME= Installation location of IIM

Ø  Configure the EDU

o   Open the WCDE_installdir/Enterprise Deployment/build/properties/install.properties file in an editor. Add the URLs of all the repositories and install locations of all products that you are installing.

Ø  Replicating Env into multiple workstations

o   Open CMD prompt and change directory to WCDE_installdir/Enterprise Deployment/bin

o   Run deploy.bat: It takes 2 argument:

§  IM_HOME is installation loc of IIM; value should be same as the one mentioned in install.xml

§  IM_UNZIP is the location where IIM is extracted.

"C:\IBM\Enterprise Deployment\bin\deploy.bat" “C:\IBM\InstallationManager\eclipse" "C:\agent.installer.win32.win32.x86_1.3.3"

Customizing the Enterprise Deployment Utility to perform additional steps: Enterprise Development Utility provides extension points that one can leverage to include additional custom deployment steps.

Following topics will be covered during this phase:

Ø  Changing DB to DB2/Oracle instead of Apache Derby

Ø   Adding Custom Projects

Ø  Upgrading RAD or WAS

Ø  Deploy Websphere Commerce Customizations



Changing DB to DB2/Oracle instead of Apache Derby

 

Pre-requisites:

Ø  Set enable_ALL.properties under WCDE_installdir/Enterprise Deployment/build/properties/install.properties to false

Ø  Ensure the database that you want to use is installed and configured on the workstations to which you are replicating the development environment.

It calls below scripts:

WCDE_installdir/setdbtype.bat -> WCDE_installdir/updatedb.bat -> WCDE_installdir/enableFeature.bat ->

 

Procedure:
Ø  Determine parameters which we need to pass in updated.bat and enableFeature.bat by running them w/o any parameter and add them in custom.properties
Ø  Add target for each 3 scripts in WCDE_installdir/Enterprise Deployment/custom/build.xml
Ø  Add property for each target in WCDE_installdir/Enterprise Deployment/custom/properties/custom.properties.
Ø  Replicate the env onto multiple workstations.

Adding Custom Projects

Procedure:
Ø  Extract the source of the custom projects from your Software Configuration Management repository or import them from the compressed files or local file system.
Ø  Compile the custom project files in the workplace.
Ø  Follow the examples in WCDE_installdir/setup/setup.xml to add similar targets in the WCDE_installdir/Enterprise Deployment/custom/build.xml file.
Ø  Replicate the environment onto multiple workstations.

Upgrading Rational Application Developer or WebSphere Application Server

 

It has normal steps which we use to upgrade WAS using IIM

 

Deploying WebSphere Commerce customizations

 

It facilitates automation of Websphere Commerce customization build and deployment processes. It also provides a robust customization framework to extend the Websphere Commerce build and Deployment tool based on project needs.  

 

Creating a toolkit deployment package: It consists of a build process, a server deployment process, & a toolkit deployment process. The build process extracts the Websphere Commerce customization source code from a software configuration management (SCM) system.

 

Pre-requisites:

Ø  Review:
o   The SCM used by the customization project
o   Deployment and execution of Apache Ant scripts
o   Deployment of customized WebSphere Commerce configuration, database, and EAR assets
o   Configuration and application update of WebSphere Application Server, particularly using the wsadmin tool and Jython scripting
o   Remote file transfer protocols such as FTP, SCP, and SFTP
Ø  Configure and Run the build process:
o   If set to run, extract source code with the user-provided Ant script.
o   Consolidates all Java source code from the source, compiles, and creates a global JAR that is used to compile each module individually. This is to help resolve classpath circular dependencies during the compilation phase using javac.
o   For each connector module set to build, compile and create an expanded resource archive (RAR).
o   For each Enterprise JavaBean (EJB) module set to build, compile, deploy, and create an EJB Java Archive (JAR) file.
o   For each Java utility module set to build, compile and create a JAR file.
o   For each Web module set to build, compile and create an expanded Web Archive (WAR).
o   For each OpenLaszlo Web module set to build, compile and create an expanded Web Archive (WAR).
o   If set to run, create a server deployment package by consolidating assets from source, archived modules and the Build and Deployment tool.
o   If set to run, create a toolkit deployment package by consolidating assets from source, archived modules and the Build and Deployment tool.
o   If set to run, unzip the server deployment package and run the server deployment process.
o   If set to run, clean the working directory.

Ø  Pre-configure the toolkit deployment settings:
o   Copy WCBD_deploy_toolkit_dir/wcbd-setenv.bat.template as WCBD_deploy_toolkit_dir/setenv.bat.
o   Copy WCBD_deploy_toolkit_dir/wcbd-deploy.private.properties.template as WCBD_deploy_toolkit_dir/deploy-target-env.private.properties, where target-env is an identifier for the target environment.
o   Copy WCBD_deploy_toolkit_dir/wcbd-deploy.properties.template as WCBD_deploy_toolkit_dir/deploy-target-env.properties.
o   Open WCBD_deploy_toolkit_dir/setenv.bat with a text editor and set the following:
o   WCDE_HOME to WCDE_installdir
o   Open WCBD_deploy_toolkit_dir/deploy-target-env.private.properties with a text editor and configure the properties in the file
o   Open WCBD_deploy_toolkit_dir/deploy-target-env.properties with a text editor and configure the properties in the file
Ø  Customize the toolkit deployment process:
o   Customizing the Enterprise Deployment Utility to deploy WebSphere Commerce customization
o   Configuring the customized Enterprise Deployment Utility
Customizing the Enterprise Deployment Utility to deploy WebSphere Commerce customization: