Use this procedure to create a stand-alone server profile with
the Profile Wizard graphical user interface (GUI).
The Complete installation procedure for WebSphere Process Server
creates one stand-alone server profile named default with a server
named server1. However, to take advantage of the product's networking
capabilities, you can use the Profile Wizard to create additional profiles.
To
create a new stand-alone server profile, use the following procedure.
- 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 to create a new
runtime environment.
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. One of the following panels is displayed:
- If a WebSphere Application Server or WebSphere Application
Server Network Deployment profile exists, the Existing profile detection panel
is displayed. This procedure assumes that you want to create a new profile,
rather than augment an existing one into a WebSphere Process Server profile.
To create a new profile, select the Create a new WebSphere Process Server
profile radio button and select Next. One of the following panels
is displayed, depending on which WebSphere Application Server product is installed:
- If WebSphere Application Server is installed, the Profile name panel is
displayed. Proceed to step 5.
- If WebSphere Application Server Network Deployment is installed, the Profile
type selection panel is displayed. Proceed to step 4.
If you want to augment an existing stand-alone server profile instead,
rather than continuing to follow this procedure, see the procedure described
in Augmenting an existing WebSphere Application Server or WebSphere Application Server Network Deployment stand-alone server profile into a WebSphere Process Server stand-alone server profile,
and begin at the step in that procedure that describes the Existing profile
detection panels.
- If no profile exists and WebSphere Application Server is
installed, the Profile name panel is displayed. Proceed to step 5.
- If no profile exists and WebSphere Application Server Network
Deployment is installed, 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.
- In the Profile name panel, specify
a unique name for the profile or accept the default name. If any other profiles
exist, you can make this profile the default profile by selecting the Make
this profile the default check box. Then select Next.
Each
profile that you create must have a name. When you have more than one profile,
you can distinguish them at their highest level by this name. See Naming considerations for profiles, nodes, hosts, and cells for information on issues you must consider
when naming the profile, such as restrictions on the length of the directory
name.
- In the Profile directory panel,
either accept the default directory location for the profile or select Browse to
specify another location, then select Next.
This
directory will contain the files that define the runtime environment, such
as commands, configuration files, and log files. By default, this directory
location is:
On Linux and UNIX platforms: install_root/profiles/profile_name
On Windows platforms: install_root\profiles\profile_name
where
profile_name is the name that was specified in step
5. This directory location can be changed to any valid
directory location on the system. If the directory already exists, it must
be empty or an error will be displayed.
If you select Back and
change the name of the profile, you might have to manually change the name
on this panel when it is displayed again.
- In the Node and host names panel, specify the node and host names
for the stand-alone server, or accept the defaults, then select Next.
Use a unique name for each node that you create. See Naming considerations for profiles, nodes, hosts, and cells for information on reserved terms and
other issues you must consider when naming the node and host.
- In the Port value assignment panel, verify that the ports specified
for the stand-alone server are unique, then select Next.
On Windows
platforms: Choose whether to run the server as a Windows service. If the profile is configured as a Windows service, the product starts
Windows services for server processes started by a startServer command.
For example, if you configure a server as a Windows service and issue the startServer command,
the wasservice command starts the defined service.
To run the
server as a Windows service, perform the following steps:
- Ensure that the Run the WebSphere Process Server process
as a Windows service check box is selected.
- Choose to log on as either a local system account or a specified
user account by selecting the radio button beside the appropriate entry.
If you choose to log on as a local system account, you do not have
to specify a user ID or password. If you choose to log on as a specified user
account, you must specify the user ID and the password for the user who is
to run the service, and the startup type (default is Manual). The
user ID must not have spaces in its name, it must belong to the Administrator
group, and it must have the advanced user rights Act as part of the operating
system and Log on as a service.
If the user ID belongs to
the Administrator group, the Profile Wizard grants it the advanced user rights
if it does not already have them.
- Select Next.
To not create a Windows service, clear the check box, and select Next.
- 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.
The Common
Event Infrastructure configuration panel is displayed.
- 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.
- Accept the default value of server1 for WebSphere server
name.
- 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 13.
- 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 following topic in this information center: 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(R) system. The Business Process Choreographer
configuration panel is displayed. Proceed to step 13. 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 12.
- In 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.
If you followed the instructions in Additional database configuration information for Common Event Infrastructure, the Business Process Choreographer configuration
panel is displayed.
- 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.
- Accept the default value of server1 for 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. (Database configuration for the Business Process Choreographer
and Common Event Infrastructure components is performed separately.)
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(TM))
- DB2 Universal (DB2 Universal Database)
- DB2 Universal OS/390 V7.1 (DB2 Universal Database for OS/390(R) V7.1)
- DB2 Universal OS/390 V8.1 (DB2 Universal Database for OS/390
V8.1)
- DB2 CLI (DB2 Call Level Interface)
- Informix (Informix(R) 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 17.
- 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 16.
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 for your database product selection,
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 create 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 created. If no errors are detected, the Profile creation is complete
panel is displayed at the end of the process.
Attention: If
errors are detected during profile creation, other panels might be displayed
in place of the Profile creation is complete panel. Examples include the following:
- Profile creation is complete with warnings panel, which indicates that
a profile was created but warnings were generated.
- Profile creation is incomplete panel, which indicates that a profile was
created but exists in an unusable state.
- Profile creation failed panel, which indicates that a profile was unable
to be created.
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.
A new stand-alone server profile exists. The node within the profile
has a server named server1.
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