After installing WebSphere Process Server,
you can create and configure one or more stand-alone server profiles.
Before you begin
Before performing this procedure:
- If you haven't already, review the general prerequisites associated with
creating and augmenting profiles in Prerequisites for creating or augmenting profiles.
- Determine if you already have a stand-alone server profile on your system,
which might save you from performing some installation tasks. If you installed WebSphere Process Server software on
your system and selected a Complete installation, a stand-alone server profile
was created for you. To find out whether you have this default profile, look
for the following directory:
On Linux and UNIX platforms: install_root/profiles/default
On Windows platforms: install_root\profiles\default
If you find this directory, you have a stand-alone server profile called default.
- During the profile creation or augmentation process, you will be configuring
the database used by the Common Event Infrastructure component and the Common
database used by other selected components. Whether you plan to create new
databases and tables, add new tables to existing databases, or postpone actual
database configuration by producing scripts that must be run manually by you
or your database administrator (DBA), you will need to know the following:
- For the Common Event Infrastructure database (event by
default):
- User ID and password for database authentication (User ID with SYSDBA
authority for Oracle).
- Directory location of the JDBC driver classpath files.
- Database server name.
- Server port.
- JDBC driver type (DB2 Universal and Oracle only).
- Database name (DB2 Universal and DB2 UDB on z/OS and OS/390 only).
- Database node name, if DB2 server remote (DB2 Universal only).
- Database instance name (sid) (Oracle only).
- Database storage group name (DB2 UDB on z/OS and OS/390 only).
- Location name of the database server (DB2 UDB on z/OS and OS/390 only).
- For the Common database (WPRCSDB by default):
- User ID and password for database authentication.
- Directory location of the JDBC driver classpath files.
- Database server host name (IP address).
- Server port.
- Database storage group name (DB2 UDB on z/OS and OS/390 only).
- Location name of the database server (DB2 UDB on z/OS and OS/390 only).
- Database instance name (Informix(R) only).
- Directory of database server installation (Informix only).
- If you plan to use DB2 on a remote z/OS machine for the Common Event Infrastructure,
Common, and Business Process Choreographer database repositories, the DBA
must create on the z/OS server four databases called event, eventcat, WPRCSDB,
and BPEDB, as well as the correct storage groups for each
(EVTSTO is the default). The DBA can use the site's standard
database definition tools and procedures to create the database and storage
groups by editing and running the default scripts provided in the following
directories:
- To create the event and eventcat databases
and associated storage groups:
On Linux and UNIX platforms: install_root/dbscripts/CEI/DB2/createCeiDb2Zos.sql.
On Windows platforms: install_root\dbscripts\CEI\DB2\createCeiDb2Zos.sql.
- To create the WPRCSDB database and associated storage
groups:
On Linux and UNIX platforms: install_root/dbscripts/CommonDB/DB2/createCommonDb2Zos.sql.
On Windows platforms: install_root\dbscripts\CommonDB\DB2\createCommonDb2Zos.sql.
- To create the BPEDB database and associated storage groups:
On Linux and UNIX platforms: install_root/dbscripts/ProcessChoreographer/DB2/createBpcDb2Zos.sql.
On Windows platforms: install_root\dbscripts\ProcessChoreographer\DB2\createBpcDb2Zos.sql.
Why and when to perform this task
You might want to configure a new stand-alone server profile if:
- You already have one or more stand-alone server profiles on a system but
you want to add another stand-alone server profile.
- You have installed WebSphere Process Server server
software on a system, but you selected Custom installation (which does not
create a stand-alone server profile) and you have now decided you want a stand-alone
server profile on the system.
This procedure assumes you are
Creating profiles using the Profile wizard or
Augmenting profiles using the Profile wizard, and have followed the instructions
in the relevant procedure. As a result, you have started the Profile wizard
and have selected to create or augment a stand-alone server profile. You must
now configure it.
Using the Profile wizard, complete the following steps
to configure a new stand-alone server profile.
Steps for this task
- Do one of the following depending on whether you are creating or
augmenting a stand-alone server profile.
- If you are augmenting a profile, much of the profile configuration will
be inherited from the WebSphere Application Server or WebSphere Application
Server Network Deployment profile. The Service Component Architecture configuration
panel is displayed. Proceed to step 7.
- If you are creating a profile, you must configure it with unique values.
The Profile name panel is displayed. Proceed to step 2.
- Specify a unique name for the profile or accept the
default name. If any other profiles exist, you have the option of making this
profile the default profile by selecting the check box next to Make this
profile the default. 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 about 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 you specified in step
2. 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 hosts name panel, specify the node and host names
for the stand-alone server profile, or accept the defaults and select Next. Try to keep the node name as short as possible, but ensure that node
names are unique within the stand-alone system or network deployment. See Naming considerations for profiles, nodes, hosts, and cells for information
about 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 profile are unique, then select Next.
On Windows platforms: Choose
whether to run the server as a Windows service and select Next. 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.
Important: 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.
- In the Service Component Architecture
configuration panel, choose to enable the Service Component Architecture to
connect to a secured bus. To do so, 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.
- Select Next.
Important: When both global security and Service Component
Architecture system bus security are turned on, proper credentials are required
to connect to the Service Component Architecture system bus to send or receive
messages. In order for the Service Component Architecture to connect to a
secured system bus, it makes use of the identity of an authorized user that
you supply in this panel. The user ID supplied must be a valid user in the
designated user registry. The user directory can be LDAP, operating system,
flat file, or any other registries that WebSphere Application Server is configured
to use for user authentication.
To set or update this user ID and
password after profile creation or augmentation, simply edit the J2C authentication
alias name "SCA_Auth_Alias" to provide the user ID and password information.
For information on how to modify this alias, see the topic Modifying authentication aliases.
For more information on the Service
Integration Bus, see the topic Service integration buses.
- In the Common Event Infrastructure configuration
panel, configure the database used by the Common Event Infrastructure component.
Refer to the topic Configuring the Common Event Infrastructure database using the Profile Wizard for
details and return to this step when you have completed the fields on the Common Event Infrastructure configuration and Additional
database configuration information for Common Event Infrastructure panels.
- Choose whether to configure a sample Business Process
Choreographer.
Restriction: Do not configure the sample Business Process
Choreographer if you plan to use this component in a production environment.
The sample configuration is for development use only. For instructions on
how to set up this component in a production setting, see the topics under
Configuring
Business Process Choreographer.
To
create a sample configuration, select the Configure 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, and select Next.
- In the Application Scheduler configuration panel,
accept the default value of server1 for the name of the server on
the node from the drop-down list and select Next.
For more information on the Application
Scheduler component, see the topic Application Scheduler.
- In the Database configuration panel, configure the Common database
used by selected WebSphere Process Server components.
Refer
to the topic Configuring the Common database using the Profile wizard for details and
return to this step when you have completed the fields on the Database configuration
and Additional database configuration information panels.
- 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 or augmented.
If no errors are detected, the Profile creation is complete or Profile augmentation
is complete panel is displayed at the end of the process.
Attention: If errors are detected, other panels might be displayed in
place of this 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.
- 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.
- Complete the stand-alone server profile configuration by doing
one of the following, depending on whether you must manually configure the Common Event Infrastructure and Common databases:
- If you completed configuration of the Common Event Infrastructure and
Common databases using the Profile wizard, ensure the check box to start the
First Steps console is selected, and select Finish to close the Profile
wizard and start the First Steps console.
- If you elected to postpone actual database configuration by producing
scripts to be run manually, do the following:
- Clear the check box to launch the First Steps console and select Finish to
close the Profile wizard.
- You or your DBA must now use your site's standard database definition
tools and procedures to edit and run the scripts the Profile wizard generated
to create or create and configure the event, eventcat,
and WPRCSDB databases (or their equivalents if they have
different names on your system). See Common Event Infrastructure database specifications and Common database specifications for the script locations. When you
have completed configuring the databases, start the First Steps console associated
with the profile, as instructed in Starting the First Steps console.
- If you plan to use the Business Process Choreographer
component in your production environment, you or your DBA must configure it,
which involves creating and configuring the Business Process Choreographer BPEDB database.
For
more information, see the topics under Configuring Business Process Choreographer.
Result
A new WebSphere Process Server stand-alone
server profile exists. The node within the profile has a server named server1.
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
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)