[AIX Solaris HP-UX Linux Windows][IBM i]

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

  1. Create the server profile from the original installation:
    • [Windows] app_server_root\bin\manageprofiles.bat
    • [Linux][HP-UX][Solaris][AIX] app_server_root/bin/manageprofiles.sh
    • [IBM i] 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:
    • [Windows] app_server_root\bin\manageprofiles.bat -create -templatePath app_server_root\profileTemplates\default
    • [Linux][HP-UX][Solaris][AIX] app_server_root/bin/manageprofiles.sh -create -templatePath app_server_root/profileTemplates/default
    • [IBM i] app_server_root/bin/manageprofiles.sh -create -templatePath app_server_root/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
    [Linux][HP-UX][Solaris][AIX]
    startServer.sh server1 -profileName profile_name
    [IBM i] 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.
  4. Display the ports.

    These are the ports assigned during profile creation.

    [Windows] Open the portdef.props file in the profile_root\properties directory.

    [Linux][HP-UX][Solaris][AIX] Open the portdef.props file in the profile_root/properties directory.

    [IBM i] 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.
  5. 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.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 08:46 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=tpro_setup
File name: tpro_setup.html