Use commands to create a profile, start the server of the
profile, display ports used by your server, and open the administrative
console.
Before you begin
This task assumes a basic familiarity with the command,
other application server commands, and system commands.
Before
you can create and use a profile, you must install the product.
About this task
Perform the following steps to create a profile, start
the server of the profile, display ports used by your server, and
open the administrative console for your server.
This
example deals with the profile environment of a standalone application
server.
Procedure
- Create the server profile from the original installation:
app_server_root\bin\manageprofiles.bat
app_server_root/bin/manageprofiles.sh
- Change directories to the profile_root/bin directory
of the new server profile.
- Start the server.
Issue the startServer command.
startServer.bat server1 -profileName profile_name
startServer.sh server1 -profileName profile_name
Note: The
-profileName argument is not necessary if you have already changed
to the profile_root/bin directory
of the target profile.
- Display the ports.
These are the ports assigned
during profile creation.
Open the portdef.props
file in the profile_root\properties directory.
Open the portdef.props file in
the profile_root/properties directory.
- Open the administrative console.
The server1
administrative console is defined on the WC_adminhost setting for
the non-secure administrative console port or the WC_adminhost_secure
setting for the secure administrative console port.
If the
value of the WC_adminhost port for your server is 20003, for example,
specify the following Web address in your browser:
http://host_name_or_IP_address:20003/ibm/console/
If
the value of the WC_adminhost_secure port for your server is 9061,
for example, specify the following Web address in your browser:
https://host_name_or_IP_address:9061/ibm/console/
Results
You created an application server profile, augmented
the profile with the feature pack, started an application server,
and accessed the administrative console using your browser.
What to do next
Deploy an application.
Restriction: When you federate or unfederate an application
server that is enabled for CEA, the
Enable communications service attribute
is reset. After federating or unfederating an application server that
is enabled for CEA, you must re-enable this attribute before running
CEA applications on the application server.
- In the administrative console, click Servers > Server Types >
WebSphere application servers > server_name >
Communications Enabled Applications (CEA).
- Check the Enable communications service checkbox.
- Click OK to save the changes to the local configuration.
- Click Save to save the changes to the master configuration.
- Stop and restart the application server.