Use this procedure to augment an existing WebSphere Application
Server or WebSphere Application Server Network Deployment stand-alone server
profile into a WebSphere Process Server stand-alone server profile using the
Profile Wizard graphical user interface (GUI).
Before you begin
Before using this procedure, ensure that:
- You have an existing installation of WebSphere Process Server
with an underlying installation of WebSphere Application Server or WebSphere
Application Server Network Deployment. If you do not, see Installing the product for installation procedures.
- You want to augment an existing WebSphere Application Server
or WebSphere Application Server Network Deployment stand-alone server profile
to a WebSphere Process Server stand-alone server profile, and that you want
to do so interactively. The existing profile must be a WebSphere Application
Server Network Deployment, version 6.0.0.x or 6.0.1.x profile.
If you are using WebSphere Process Server, version 6.0.1,
you can also augment WebSphere Application Server or WebSphere Application
Server Network Deployment, version 6.0.2.x profiles.
See Creating and augmenting profiles by using the Profile Wizard for descriptions of other profile creation
or augmentation procedures.
- You determine if the stand-alone server profile you want to augment has
already been federated to a deployment manager. If it has, you cannot augment
it to a WebSphere Process Server profile.
- If you plan to locate the repository for WebSphere Process
Server on a remote server, that you create it before beginning this procedure.
The Profile Wizard will let you create a repository on the local server or
use an existing one on a remote server.
- You have enough disk and
temporary space to augment the profile. See Required disk space for the minimum disk space required.
- If you have enabled global security on the installation
of WebSphere Application Server or WebSphere Application Server Network Deployment
that contains the profile you want to augment, you disable it before augmenting
the profile. For information on enabling and disabling global security, see
the WebSphere Application Server Network Deployment, version 6.0 information
center at http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp.
- If you plan to use DB2 Universal Database for your repository, you perform
the following steps before augmenting the profile:
- If you are configuring a DB2 database on a DB2 client with the server
on a remote system, make sure the client system is configured to communicate
with the server and that the DB2 node is cataloged. For more information,
refer to the DB2 Universal Database documentation.
On Linux and UNIX platforms: If you are
configuring a DB2 database on a Linux or UNIX system, source the database
environment by doing the following: - Modify /etc/group and make sure root is in the same group as
the db2instance.
- Source the database environment by running the db2instance/sqllib/db2profile script
(replace db2instance with the name of your database instance).
Why and when to perform this task
To augment an existing WebSphere Application Server or WebSphere
Application Server Network Deployment stand-alone server profile into a WebSphere
Process Server stand-alone server profile, use the following procedure.
Steps for this task
- Log on as the root user on a Linux or UNIX system, or as a member
of the Administrator group on a Windows system.
- Start the WebSphere Process Server Profile Wizard.
See Starting the Profile Wizard for
descriptions of the many ways to start the Profile Wizard on various platforms.
The
wizard loads the Java 2 SDK and then displays its Welcome panel.
- In the Welcome panel, select Next.
If an unfederated WebSphere Application Server or WebSphere Application
Server Network Deployment profile exists for augmentation, one of two Existing
profile detection panels is displayed. Do one of the following, depending
on whether WebSphere Application Server or WebSphere Application Server Network
Deployment is installed:
- If WebSphere Application Server is installed, select the Augment an
existing WebSphere Application Server profile radio button, highlight
the profile to augment from the drop-down list, and select Next. Only
unfederated profiles are displayed as selections. The profile you select to
augment must be from the version of WebSphere Application Server on which
WebSphere Process Server is installed. The Service Component Architecture
configuration panel is displayed. Proceed to step 6.
- If WebSphere Application Server Network Deployment is installed, select
the Augment an existing WebSphere Application Server profile radio
button and select Next. The Profile type selection panel is displayed.
Proceed to step 4.
- In the Profile type selection
panel, select the Stand-alone WebSphere Process Server profile radio
button, then select Next.
The list of profile types will
include only those types which have valid WebSphere Application Server Network
Deployment profiles that can be augmented into WebSphere Process Server profiles.
- In the Profile augmentation selection panel, choose the profile
you want to augment from the drop-down list and select Next.
The list includes only those profiles of the type selected. Only
unfederated profiles are displayed as selections. The profile you select to
augment must be from the version of WebSphere Application Server Network Deployment
on which WebSphere Process Server is installed.
- In the Service Component Architecture
configuration panel, choose whether to configure the Service Integration Bus
in a secured mode. To configure the Service Integration Bus in a secured mode,
perform the following steps:
- Select the Configure the Service Integration Bus in a secured
mode check box.
- Enter the user ID and password, and confirm the password, used
to authenticate with a secured Service Integration Bus.
- Select Next.
To not configure the Service Integration Bus in a secured mode, leave
the check box clear and select Next.
- In the Common Event Infrastructure configuration panel, configure
the Common Event Infrastructure by performing the following steps:
- Enter the user ID and password, and confirm the password, used
to authenticate with the WebSphere Messaging queue manager.
- Enter the WebSphere server name. The default value is server1.
- Choose the database product you want to use for
your configuration, or accept the default value of Cloudscape V5.1.
- Select Next.
One of the following panels is displayed:
- If you accept the default value of Cloudscape V5.1,
the Business Process Choreographer configuration panel is displayed. Proceed
to step 9.
- If you select DB2 Universal OS/390 V7.1 or DB2 Universal
OS/390 V8.1, a message panel is displayed, informing you that you must
create your data source and database outside of the Profile Wizard. If you
still want to use one of these databases and agree to create your data source
and database outside of the Profile Wizard, select Next and review
the topic Installing > Configuring the product after installation > Configuring
the Common Event Infrastructure > Post-installation configuration > Configuring
the event database > Configuring a DB2 database on a z/OS system in this
information center. The Business Process Choreographer configuration panel
is displayed. Proceed to step 9. If you want to select another database
instead, select Back.
- If you select any other database, the Additional database configuration
information for Common Event Infrastructure panel is displayed, with fields
specific to the database you have selected. Proceed to step 8.
- On the Additional database configuration
information for Common Event Infrastructure panel, complete the fields as
detailed in Additional database configuration information for Common Event Infrastructure. Return to this step when you have followed the instructions in that
topic.
- In the Business Process Choreographer
configuration panel, choose whether to create a sample Business Process Choreographer
configuration. Create one by performing the following steps:
- Select the Create a sample Business Process Choreographer check
box.
- Enter the user ID and password, and confirm the password, used
to authenticate when connected to a Secured Service Integration Bus.
- Enter the name of the administrative group that will be allowed
to administer Business Process Choreographer.
For example,
if the domain user registry is LDAP, enter a group name for the security role
like, cn=MyGroup,o=MyCompany,c=MyCountry. If
you are using Windows group administration, enter a group name such as Administrators.
- Select Next.
To not create a Business Process Choreographer configuration, leave
the check box clear and select Next.
If you plan to use Business
Process Choreographer in a production environment, do not create the sample
configuration. To configure Business Process Choreographer for use in a production
environment, see the topics under Installing > Configuring the product
after installation > Configuring Business Process Choreographer in this
information center.
- In the Application Scheduler configuration panel, choose whether
to create an Application Scheduler configuration. To create an Application
Scheduler configuration, perform the following steps:
- Select the Create an Application Scheduler configuration check
box.
- Enter the name of the server on the node.
- Select Next.
To not create an Application Scheduler configuration, leave the check
box clear and select Next.
- In the Database configuration panel, configure database authentication
for selected WebSphere Process Server components.
Several WebSphere
Process Server components use a database, including:
- Recovery
- Relationship service
- Mediation
- Application Scheduler
- Business rule group
- Selector
The information requested on this and the following panel (if it is
displayed) correctly configure a new local or existing database for use with
these components.
Configure database authentication by performing the
following steps.
- Select to either create a new database or use
an existing one by selecting the appropriate radio button. If
you choose to create a new database, no other database by that same name can
exist or the procedure will fail.
- Choose the database you want to use, or accept
the default value of Cloudscape.
You can select the
following databases from this panel (each entry that can be selected from
the list is shown, followed by the database it represents):
- Cloudscape (Cloudscape)
- DB2 Universal (DB2 Universal Database)
- DB2 Universal OS/390 V7.1 (DB2 Universal Database for OS/390
V7.1)
- DB2 Universal OS/390 V8.1 (DB2 Universal Database for OS/390
V8.1)
- DB2 CLI (DB2 Call Level Interface)
- Informix (Informix Dynamic Server)
- MSSQL Server Embedded (Microsoft SQL Server Embedded)
- MSSQL Server Data Direct (Microsoft SQL Server
DataDirect)
- Oracle OCI (Oracle OCI client)
- Oracle Thin (Oracle Thin)
- Enter your database name or accept the default WPRCSDB.
If the database name WPRCSDB is already associated with another WebSphere
Process Server profile, you must use a different database name.
- Select Next.
One of the following panels is displayed:
- If you select the default value of Cloudscape, the
Profile summary panel is displayed. Proceed to step 13.
- If you select any other database, the Additional database configuration
information panel is displayed, with fields specific to the database you have
selected. Proceed to step 12.
Restriction: The
business rule group and selector components support only
Cloudscape,
DB2
Universal,
DB2 Universal OS/390 V7.1,
DB2 Universal OS/390
V8.1, or
DB2 CLI for their repository.
In
WebSphere Process Server, version 6.0.1, these components also support Oracle
OCI (Oracle OCI client) and Oracle Thin (Oracle Thin).
If
you select any database other than these, all components, except the business
rule group and selector components, will be configured to use the database
you specify; the business rule group and selector components will be configured
to use Cloudscape.
Restriction: You cannot create a new database if you
are using DB2 Universal OS/390 V7.1, DB2 Universal OS/390 V8.1, Oracle
OCI, or Oracle Thin as your database product. If you select
one of these combinations on the Database configuration panel, a message panel
is displayed, informing you that you must either use an existing database
or select a different database product. Select OK to close this message
panel, and make different selections on the Database configuration panel.
- On the Additional database configuration
information panel, complete the fields as detailed in Additional database configuration information for common databases, and select Next.
- In the Profile summary panel,
review the profile characteristics and select Next to augment the profile
or select Back to change the characteristics of the profile.
The Profile Wizard shows a progress panel to indicate that the profile
is being augmented. If no errors are detected, the Profile augmentation is
complete panel is displayed at the end of the process.
Attention: If errors are detected during profile augmentation, other
panels might be displayed in place of the Profile augmentation is complete
panel. Examples include the following:
- Profile augmentation is complete with warnings panel, which indicates
that a profile was augmented but warnings were generated.
- Profile augmentation is incomplete panel, which indicates that a profile
was augmented but exists in an unusable state.
- Profile augmentation failed panel, which indicates that a profile was
unable to be augmented.
Each of these panels identifies the log file to reference in order to
troubleshoot the problems. Also refer to
Recovering from profile creation or augmentation failure for troubleshooting tips.
- Ensure the check box to launch the First Steps console is selected,
and select Finish to close the Profile Wizard and start the First Steps
console.
Result
A WebSphere Application Server or WebSphere Application Server
Network Deployment stand-alone server profile is successfully augmented into
a WebSphere Process Server stand-alone profile.
What to do next
Check server operation by selecting
Start the server from
the First Steps console. An output window opens. If you see a message similar
to the following, your server is operating properly:
ADMU3000I: Server server1 open for e-business; process id is 3348