To deploy WebSphere® configurations
and applications, you use plug-ins to read information about a live
deployment into a model in Resources. You then define components,
applications, environments, and processes to automate deployments
that create new instantiations of the modeled WebSphere environment.
Before you begin
The following setup and preparation is required.
- Select or set up a WebSphere cell
to use. The configuration template you create will use its configuration.
- Install an UrbanCode Deploy agent on the appropriate WebSphere host. Note that you need the
agent name during the procedures.
- For ND deployments, install the agent where DMGR is running.
- For server deployments, install the agent where Base is running.
- Determine what tokens you need. Tokens are used to represent information
that is different among deployment environments. For example, you
might specify a different database server or JDBC resource in each
of a development, test, and production environment. For each token,
you need a name and an initial value. You are prompted to enter the
names and values at the end of the process. See Using custom properties when deploying WebSphere configurations and applications
- If WebSphere Application
Server is deployed in a directory other than the default directory,
you must set a property on the agent before you can run a process
to deploy a WebSphere cell.
- Go to .
- Add a property named wsadmin.path.
- Set wsadmin.path to the fully qualified path
to the wsadmin script (including the script name).