About this task
By selecting the Advanced option,
you can specify your own values for settings such as ports, the location
of the profile, and the names for the profile, node, host, and cell.
You can optionally choose whether to deploy the administrative console, the WebSphere Application Server sample application,
or create a Web server definition. You can optionally enable administrative
security. If your operating system and the privileges of your user
account permit, you can create a system service to run the server. You
can also specify your own configuration values for the Common Event
Infrastructure and Common databases and configure Business Space.
Important: If you plan to federate the profile to a deployment
manager, do not select the file store option for the messaging engines
or Derby Embedded for the Common Event Infrastructure, or Common
databases. The file store option and Derby Embedded database cannot
be used in a deployment environment configuration.
As
a result of following the procedure in either Augmenting profiles using the Profile Management Tool or Creating profiles using the Profile Management Tool, you are viewing either
the Administrative security panel or the Optional application deployment
panel. Complete the following steps to configure a new stand-alone
server profile with customized configuration values.
- The panel you see displayed in the Profile Management Tool
depends on whether you are creating or augmenting a profile. If you
are augmenting a profile, it also depends on whether security is enabled
on that profile and on whether the Common Event Infrastructure is
configured on the system.
If you are performing |
First step |
Advanced profile augmentation to a WebSphere ESB profile and Security is enabled on the profile
you are augmenting. |
The Administrative security panel is displayed. Proceed to
step 5. |
Advanced profile creation |
The Optional application deployment panel is displayed. Proceed
to step 2. |
- For Advanced profile creation only: In
the Optional Application Deployment panel, select the applications
that you want to deploy to the stand-alone server profile environment
you are creating, then click Next.
To
choose an application from the following list, leave the check box
beside the application selected. Clear the check box to deselect an
application.
The Profile Name and Location panel is displayed.
- For Advanced profile creation only: In
the Profile Name and Location panel, perform the following steps.
- Specify a unique name and directory path for the profile, or accept
the defaults.
Each profile that you create must have a name. When
you have more than one profile, you can tell them apart at their highest
level by this name. If you elect not to use the default 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.
The directory you specify
will contain the files that define the runtime environment, such as
commands, configuration files, and log files. The default directory
is dependent on platform:
user_data_root/profiles/profile_name

install_root/profiles/profile_name
install_root\profiles\profile_name
where
profile_name is the name you specified.
An error message is displayed if:
- The profile_name you specify is not unique.
- The directory you specify is not empty.
- Your user ID does not have sufficient permissions for the directory.
- There is not sufficient space to create the profile.
- To create the stand-alone server with configuration settings optimized
for development environments, select the Create the server
using the development template check box. The development
template reduces startup time and allows the server to run on less
powerful hardware. Do not use this option for production servers.
- You can make the profile you are creating the default profile
(so commands work automatically with it) by selecting the Make
this profile the default check box. This check box appears only
if you have an existing profile on your system.
The first profile
that you create on a workstation is the default profile.
The
default profile is the default target for commands that are issued
from the bin directory in the product installation root.
When only one profile exists on a workstation, every command operates
on that profile. If more than one profile exists, certain commands
require that you specify the profile to which the command applies.
See Profile commands in a multiprofile environment for more information.
- Click Next. (If you click Back and
change the name of the profile, you might have to manually change
the name on this panel when it is displayed again.)
The Node, host,
and cell names panel is displayed.
- For Advanced profile creation only: In the Node,
Host, and Cell names panel, specify the node, host, and cell names
for the stand-alone server profile, or accept the defaults and click Next. Try to keep the node name as short as possible, but ensure that
node names are unique within your deployment environment. See Naming considerations for profiles, nodes, hosts, and cells for information about
reserved terms and other issues you must consider when naming the
node, host, and cell.
The Administrative security panel is displayed.
- Enable administrative security.
This
screen differs depending on whether you are creating or augmenting
a profile.
If you are creating a profile, you can enable administrative
security now, or later from the administrative console. To enable
administrative security now, leave the Enable administrative
security check box selected, supply a user name and password
to log onto the administrative console, and click Next.
To disable administrative security, clear the check box. To enable
administrative security later from the administrative console, open
the console and click Security > Business Integration Security.
If you chose to deploy the WebSphere Application Server sample application
from the Optional application deployment panel in step 2, it requires an
account under which to run. Supply the password for the account. You
cannot change the user name of the account.
If you are augmenting
a profile and see this panel, the profile you are augmenting has security
enabled. You must re-enter the administrative user ID and password
for that profile.
The next step depends on the following conditions:
If you are performing |
Next step |
Advanced profile creation |
The Port values assignment panel is displayed. Proceed to
step 6. |
- For Advanced profile creation only: Verify
that the ports specified for the profile are unique and click Next.
The Profile Management Tool detects ports currently used
by other WebSphere products
and displays recommended port values that do not conflict with existing
ones. If you have applications other than WebSphere ones that use specified ports,
verify that the ports do not conflict. If you chose not to deploy
the administrative console on the Optional application deployment
panel in step 2,
the administrative console ports are not available on the Port values
assignment panel.
Ports are recognized as being in use if the
following conditions are satisfied:
- The ports are assigned to a profile created under an installation
performed by the current user.
- The ports are currently in use.
Although the tool validates ports when you access the Port values
assignment panel, port conflicts can still occur resulting from selections
you make on subsequent Profile Management Tool panels. Ports are not
assigned until profile creation completes.
If you suspect a
port conflict, you can investigate it after the profile is created.
Determine the ports used during profile creation by examining the
following file:
profile_root/properties/portdef.props

profile_root/properties/portdef.props
profile_root\properties\portdef.props
Included in this file are the keys and values used in setting
the ports. If you discover port conflicts, you can reassign ports
manually. To reassign ports, see the topic
Updating ports in an existing profile in the WebSphere Application Server
Network Deployment, version 6.1 information center and run the
updatePorts.ant file
through the
ws_ant script.
The next step depends on your
platform and whether you are installing as a root (Administrator)
or non-root user.
If you are installing |
Next step |
On a Linux® platform and
are running the Profile Management Tool as the root user |
The Linux service
definition panel is displayed. Proceed to step 8. |
On a Windows® platform and
have Administrator group privileges |
The Windows service
definition panel is displayed. Proceed to step 7. |
On any other platform or as a non-root user on a Linux or Windows platform. |
The Web server definition panel is displayed. Proceed to step 9. |
For Advanced profile
creation only: Choose whether to run the server as a Windows service and click Next.
The Windows Service
Definition panel is displayed for the Windows platform only if the ID that installs
the Windows service has
the Administrator group privilege. 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 Log
on as a service and Act as part of the operating system.
If the user ID belongs to the Administrator group, the Profile Management
Tool grants it the advanced user rights if it does not already have
them.
During profile deletion you can remove
the Windows service that
is added during profile creation.
IPv6 considerations
when running profiles as Windows services
Profiles created to run as a Windows service fail to start when using
IPv6 if the service is configured to run as Local System. Create a
user-specific environment variable to enable IPv6. Because this environment
variable is a user variable instead of a Local System variable, only
a Windows service that runs
as that specific user can access this environment variable. By default,
when a new profile is created and configured to run as a Windows service, the service is set to run
as Local System. When the WebSphere ESB Windows service
tries to run, the service is unable to access the user environment
variable that specifies IPv6, and thus tries to start as IPv4. The
server does not start correctly in this case. To resolve the problem,
when creating the profile specify that the WebSphere ESB Windows service
runs as the same user ID under which the environment variable that
specifies IPv6 is defined, instead of as Local System.
The Web
server definition panel is displayed.
For Advanced profile
creation only: Choose whether to run the server as a Linux service and click Next.
The Linux Service Definition panel
is displayed only if the current operating system is a supported version
of Linux and the current user
has the appropriate permissions.
WebSphere ESB attempts
to start Linux services for
server processes that are started by a startServer command.
For example, if you configure a server as a Linux service and issue the startServer command,
the wasservice command attempts to start the defined service.
By
default, WebSphere ESB is
not selected to run as a Linux service.
To
create the service, the user who runs the Profile Management Tool
must be the root user. If you run the Profile Management Tool with
a non-root user ID, the Linux service
definition panel is not displayed, and no service is created.
You
must specify a user name under which the service runs.
To delete
a Linux service, the user
must be the root user or have proper privileges for deleting the service.
Otherwise, a removal script is created that the root user can run
to delete the service on the user's behalf.
The Web server definition
panel is displayed.
- For Advanced profile creation only: If
you want to include a Web server definition in the profile now, perform
the following steps:
Note: On i5/OS®,
do
not create the Web server definition using the Profile Management
Tool. Therefore, do not enable this option on the Web server definition
panel. You will need to use the IBM® HTTP
Server for iSeries® configuration
and administration forms, which create the Web server definition and
an HTTP server instance. They also correctly associate the HTTP server
to this Web server definition. For more information, see the topic
Configuring an HTTP server instance in the WebSphere Application Server
Network Deployment for i5/OS,
version 6.1 information center.
- Select the Create a Web server definition check
box.
- Specify the Web server characteristics on the panel, and click Next.
- Specify the Web server characteristics on Part 2 of the panel
and click Next.
If you use a Web server to route requests to WebSphere ESB, you need to include a Web server definition. You can include
the definition now, or define the Web server to WebSphere ESB later. If you define the Web server definition during the
creation of this profile, you can install the Web server and its plug-in
after you create the profile. However, you must install both to the
paths that you specify on the Web server definition panels. If you
define the Web server to WebSphere ESB after you create this profile, you must define the
Web server in a separate profile.
- On the Business Space Configuration
panel, select the Configure Business Space check
box to set up Business Space powered by WebSphere,
an integrated user experience for application users across the IBM Websphere Business Process Management
portfolio and then click Next. Configuring Business Space sets up an
integrated GUI for the business users of your application for this
profile.
Important: Business Space is supported
with the following database products: Derby Embedded, Derby Network
Server, DB2® Universal, DB2 Universal Runtime Client, DB2 for i5/OS, DB2 for z/OS®, Oracle 9i, Oracle 10g, and
Oracle 11g.
If the database you use for WebSphere ESB does
not match the supported databases for Business Space, a Derby Embedded
database is selected for the Business Space configuration.
You cannot federate this profile into a deployment environment later,
because Derby Embedded is not supported for deployment environments.
The Database Configuration
panel is displayed.
- In the Database Configuration panel, configure
both the Common database and the database used by the Common Event Infrastructure component used
by selected WebSphere ESB components.
Refer to the Configuring the Common database and the Common Event Infrastructure database using the Profile Management Tool topic for details and return
to this step when you have completed the fields on the Database Configuration
panel and the Database Configuration (part 2) panel.
The Profile
summary panel is displayed.
- In the Profile summary panel, click Create or Augment to
create or augment the profile or Back to change
the characteristics of the profile.
When
the profile creation or augmentation is complete, the Profile complete
panel is displayed with the message The Profile Management tool
created the profile successfully or The Profile Management
tool augmented the profile successfully.
- 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 Management Tool, select Launch the First
steps console, Create another profile,
or both; click Finish to exit. Use the First
steps console to start the server. Use the Create another
profile option to restart the Profile Management Tool
to create additional profiles.
- If you chose to postpone actual database configuration by producing
scripts to be run manually, perform the following steps:
- Clear the check box to launch the First steps console and click Finish to
close the Profile Management Tool.
- Use your site's standard database definition tools and procedures
to edit and run the scripts the Profile Management Tool generated
to create, or create and configure, the event, eventcat,
and WPRCSDB databases (or their equivalents if they
have different names on your system). You identified the location
for these scripts in step 2 of
the topic Configuring the Common database and the Common Event Infrastructure database using the Profile Management Tool. Also see
the topics that describe manually creating new databases or new tables
in existing databases:
When the databases are configured, start the First steps console
associated with the profile, as described in Starting the First steps console.
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 message, your server is operating properly:
ADMU3000I: Server server1 open for e-business; process id is 3348
You can also check server operation by running
the Installation Verification Test (IVT) from the First steps console
or running the wbi_ivt command. This test is to
verify that your deployment manager or stand-alone server installation
is operating properly. For a stand-alone server profile, it also runs
a Health Monitor check and generates a report.