Use this procedure to create a custom profile using the Profile
Wizard graphical user interface (GUI).
Before you begin
Before using this procedure, ensure that:
Why and when to perform this task
The Complete installation procedure for WebSphere Process Server
creates one stand-alone profile named default with a server named server1.
However, to take advantage of the networking capabilities of the product,
you can use the Profile Wizard to create additional profiles.
To create
a new custom 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.
Draft comment: See
if supported for March.
- 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, depending on whether a WebSphere
Application Server Network Deployment profile exists:

Draft comment:
I removed "version 6.0.1.2" from "If a WebSphere
Application Server Network Deployment, version 6.0.1.2 profile exists, the
Existing profile detection panel is displayed."
If a 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. The Profile
type selection panel is displayed. If you want to augment an existing profile
instead, rather than continuing to follow this procedure, see the procedure
described in
Augmenting an existing WebSphere Application Server Network Deployment custom profile into a WebSphere Process Server custom profile,
and begin at the step in that procedure that describes the Existing profile
detection panel.

- If no profile exists, the Profile type selection panel is displayed.
- In the Profile type selection
panel, select the Custom profile radio button, then select Next.
- In the Federation panel, determine
whether to federate the custom node into a deployment manager.
If you choose to federate the node, specify the host name or IP address
and SOAP port of the deployment manager and select Next to continue.
The Profile name panel is displayed.
Attention: Federate
the custom node at this time only if all of the following are true:
- The deployment manager is running.
- The deployment manager is a WebSphere Process Server profile.
- Security is not enabled on the deployment manager node.
- The deployment manager uses the default SOAP JMX connector type and the
connector is enabled.
Do
not federate the custom node at this time if any one
of the following is true:
- The deployment manager is not running or you are not sure if it is running.
- The deployment manager is a WebSphere Application Server Network Deployment
profile that has not yet been augmented into a WebSphere Process Server profile.
- Security is enabled on the deployment manager node.
- The SOAP connector is disabled.
- The deployment manager is reconfigured to use the non-default remote method
invocation (RMI) as the preferred Java Management Extensions (JMX) connector.
(Select System administration > Deployment manager > Administration services in
the administrative console of the deployment manager to verify the preferred
connector type.)

Draft comment:
Changes for
303445
If you attempt to federate a custom node when the deployment
manager is not running or is not available for other reasons, a warning panel
prevents you from continuing. If this warning panel appears, select
OK to
exit from it, and then make different selections on the Federation panel.


If you attempt to federate a custom
node when the deployment manager is not running or is not available for other
reasons, the Profile creation failed panel is displayed. Select
Finish to
exit this panel but do not follow its instructions to delete the profiles
directory.

If you choose not to federate the node, select the Federate this
node later using the addNode command check box and select Next to
continue. The Profile name panel is displayed. See Federating custom nodes to a deployment manager for more information on how to federate
a node by using this command.
- In the Profile name panel, specify
a unique name for the profile or accept the default name. If 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
6. 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 custom profile, or accept the defaults, then select Next.
Use a unique name for each custom 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.
One of the following panels is displayed, depending on whether
you elected to federate the node on the Federation panel in step
5:
- If you elected to federate the node later by selecting the Federate
this node later using the addNode command check box on the Federation
panel, the Database configuration panel is displayed. Proceed to step 10.
- If you did not elect to federate the node later on the Federation panel,
the Port value assignment panel is displayed. Proceed to step 9.
- In the Port value assignment
panel, verify that the ports specified for the custom node are unique, then
select Next.
When federating a custom profile, the addNode command
uses non-conflicting ports. This means that you can take the default port
assignments as you create the profile, and let the addNode command
specify non-conflicting ports as you federate the node. Port assignments must
be unique on a machine. Server processes on different machines can use the
same port assignments without conflict.
- In the Database configuration
panel, configure database authentication.
Configure database
authentication by performing the following steps.
- Choose the database that matches the database used on the deployment
manager to which this custom profile will be federated. Select the database
from the list, or accept the default value of DB2 Universal.
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):
- 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)
If your selection is other than MSSQL Server Embedded,
you must also provide the location of the JDBC driver class path files for
the database. If your selection is DB2 Universal, you can accept
the default value of install_root/universalDriver_wbi/lib on
Linux and UNIX platforms or install_root\universalDriver_wbi\lib on
Windows platforms.
- Select Next.
One of the following
panels is displayed:
- If you select the default value of DB2 Universal, or the databases DB2
Universal OS/390 V7.1, DB2 Universal OS/390 V8.1, or DB2
CLI, the Profile summary panel is displayed. Proceed to step 12.

The business rule group and selector components support only
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, a warning panel is displayed, which
explains this restriction. Proceed to step 11.
Remember: This warning
panel is displayed only the first time you select a database other than these.
If you select Back, select another database other than these, and then
select Next, the warning panel is not displayed.

In the warning
panel, if you intend to use the business rule group and selector components
and you still want to use a database for the other components that the business
rule group and selector components do not support, you have to configure the
repository database for the business rule group and selector components manually. Select OK to keep your selections or Back to return to
the Database configuration panel to change your settings. For information
on configuring the repository database for the business rule group and selector
components manually, see the following topic in this information center: Administering
WebSphere Process Server > Administering applications and application services
> Business rules > Installing the business rules dynamic repository for network
deployment. This procedure assumes you select OK.
- 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.
Result
A new custom profile exists. The node within the profile is empty
until you federate the node (if you have not done so during profile creation)
and use the deployment manager to customize the node.
What to do next
Federate the node into the deployment manager cell if you have not
already done so as you created the custom node. See
Federating custom nodes to a deployment manager for details.