Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment > Manage profiles on non-z/OS operating systems


Manage 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.

This task assumes a basic familiarity with the command, other application server commands, and system commands.

Before you can create and use a profile, install the product.

Create a profile, start the server of the profile, display ports used by your server, and open the admin console for your server.

This example deals with the profile environment of a standalone application server.


Procedure

  1. Create the server profile from the original installation:

    • (Windows) WAS_HOME\bin\manageprofiles.bat
    • (Solaris) (AIX) WAS_HOME/bin/manageprofiles.sh

    Assume that you create the profile by using the defaults. The following script is an example for creating an application server profile:

    • (Windows) WAS_HOME\bin\manageprofiles.bat -create -templatePath WAS_HOME\profileTemplates\default
    • (Solaris) (AIX) WAS_HOME/bin/manageprofiles.sh -create -templatePath WAS_HOME/profileTemplates/default

  2. Change directories to the PROFILE_ROOT/bin directory of the new server profile.

  3. Start the server.

    Issue the startServer command.

    (Windows)

    startServer.bat server1 -profileName profile_name
    

    (Solaris) (AIX)

    startServer.sh server1 -profileName profile_name
    

    The -profileName argument is not necessary if we have already changed to the PROFILE_ROOT/bin directory of the target profile.

  4. Display the ports.

    These are the ports assigned during profile creation.

    (Windows) Open the portdef.props file in the PROFILE_ROOT\properties directory.

    (Solaris) (AIX) Open the portdef.props file in the PROFILE_ROOT/properties directory.

  5. Open the admin console.

    The server1 admin console is defined on the WC_adminhost setting for the non-secure admin console port or the WC_adminhost_secure setting for the secure admin 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 admin console using your browser.


What to do next

Deploy an application.
manageprofiles command

+

Search Tips   |   Advanced Search