Discover resources for a portal cell and use
plug-in steps to deploy artifacts.
Before you begin
- The UrbanCode Deploy agent must be installed on the system that
hosts the Portal Node.
- 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 the WebSphere
Topology Discovery step.
- Go to .
- Add a property named wsadmin.path.
- Set wsadmin.path to the fully qualified path
to the wsadmin script (including the script name).
Procedure
- Install the WebSphere Portal
plug-in.
- In UrbanCode Deploy, go to .
- Click Load Plugin.
- In the dialog, click Choose File, then
choose the WebSpherePortal-<version>.zip file.
- Click Submit.
.
- Install the Application Deployment for WebSphere® plug-in. Skip this step if it is already installed.
- Add an agent.
- Hover over the row for the resource group, click Actions,
and select Add agent.
- Wait 10 to 30 seconds, then click Refresh. A twisty is now next to the agent. When you expand it, there
is a sub-resource cell, WebSphereCell.
- Hover over the row, then click Edit.
- Enter values for the following properties.
- WebSphere Profile
Path
- WebSphere User
- WebSphere Password.
If this value is left blank, soap.properties is used
to locate the password for the user.
Leave the Cell Name property blank.
- Click Save.
- Set Auto configure options for WebSphereCell.
- Hover over the row for WebSphereCell,
click Actions, then click Auto Configure.
- Click No auto configure for resource.
- Check Websphere Topology Discovery box.
- Click OK.
- Click Save.
- Wait 30-60 seconds, then click Refresh. A twisty is now next to WebSphereCell.
Expand it and make sure the resource tree matches your WebSphere Application Server topology.
It will contain deployable artifacts for WebSphere Portal (theme, PAA, WAR, ConfigEngine
command, XMLAccess script)
- On the WebSphereCell entry, click Edit. Check that Cell Name was filled in and
is correct.
- Define properties for resources. Click on the
resource, then the Configuration tab, then Resource
Properties.
- For ND topology, define the properties for Portal Cluster, Portal
Primary Node, and Portal Secondary Node resources.
- For stand-alone topology, define the properties for the Portal
Node resource.
Define the following properties:
- portal.home: Portal installation directory
- portal.profile.home: Portal profile directory
- portal.admin.user: Portal administrator user
name
- portal.admin.password: Portal administrator
password
- portal.config.port: Portal configuration
port
- websphere.password: WebSphere administrator password
- Create components for the resources. You need
one component for each resource to deploy.
- Add the components to the resources.
- Go to the resource.
- Choose
- Select the component to use.
- Create the application.
- Go to Applications.
- Click Create New Application (if
one does not exist). You can also use an existing application
that is attached to the cell to manage.
- Enter an application name, then click Save.
- Click the Components tab, then
add the component that was created by the template generation procedure.
- Create an application environment.
- In the Resources tab, click Create
New Environment.
- Enter an environment name, then click Save.
- Go to the environment editing page.
- Click on the environment name, then click Add
Base Resource. Choose the group for your exemplar
cell and environment.
- Edit the environment properties for the component. Click . In the Component Environment
Properties list, enter values for each property shown.
Note that values are already filled in with default values if you
provided them above.
- Create an application process of type Deployment for
configuration and deployment.
- Click the Processes tab.
- Add a deploy step.
- Drag and drop the Install Component step
onto the process editor.
- Select the component to use. You created this component for the
resource. For example, you created a component to contain a Portal
WAR file to be deployed.
- Choose the process for the component. For example, you would choose
Deploy Portal WAR file for a Portal WAR file component.
- Click Save.
- Save the process.
- Run the process to test the newly created component.