Managing profiles using commands

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
- app_server_root/bin/manageprofiles
Assume that you create the profile by using the defaults. The following script is an example for creating an application server profile:
- app_server_root\bin\manageprofiles.bat -create -templatePath app_server_root\profileTemplates\default
- app_server_root/bin/manageprofiles.sh -create -templatePath app_server_root/profileTemplates/default
- app_server_root/bin/manageprofiles.sh -create -templatePath app_server_root/profileTemplates/default
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
```
The server name is the same name as the profile, which, in this case, is profile_name.
```
startServer -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.
Use the dspwasinst QShell script to display the ports for your new profile:
```
app_server_root/bin/dspwasinst -profileName profileName
```
The WC_adminhost and WC_adminhost_secure ports listed are the nonsecure and secure administrative console ports, respectively.
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, started an application server, and accessed the administrative console using your browser.

What to do next

Deploy an application.