Once the WebSphere Application Server (WAS) is installed, you must create a profile to make the product functional. In this part of the post you will see,  How to create WAS Standalone Application Server Profile in WAS 8.5 named as AppSrv01 with the Profile Management Tool in the WebSphere Customization Toolbox. The type of the profile is Standalone Application Server. The Profile Management Tool is added to the WebSphere Customization Toolbox during the installation of WAS.

To install WAS on Ubuntu follow How to Install WAS 8.5 on Ubuntu. Also if you want to Install IBM Installation Manager on Ubuntu check How to Install Installation Manager on Ubuntu

As per the IBM’s documents of supported Linux distributions, Ubuntu is not supported for IBM products. For evaluation purpose you can install it on Ubuntu, but it is not recommended for production environment. Also you can see it as a reference document to install on another supported Linux distributions.

Followings are the bullet points of How to Create WAS Standalone Application Server profile.

  1. Understand what is profile?
  2. Prepare system before creating profile.
  3. Create WAS Standalone Application Server profile using Profile Management Tool.
  4. Verify creation of WAS Standalone profile.
  5. Start and Stop the WebSphere Application Server.
  6. Understand directory structure.
  7. Check log files.
  8. Access default Application.

This tutorial use two variables to define various installation paths. They are as follows

  • <was_root>: /app/IBM/WebSphere/AppServer
  • <profile_root>: /app/IBM/WebSphere/AppServer/profiles
  1. What is profile?
    A profile is a set of configuration files used to create application server runtimes. This set includes static product files as well configuration files used to prepare and control runtime environment.
    After the core product files for WebSphere Application Server are installed, you must create a profile to make the product functional.
    At least one profile must exist to run the WebSphere product. In this post we will see how to create WAS Standalone Application Server Profile. Standalone Application Server profile is used to create a standalone application server. The purpose of standalone server is to prepare runtime environment which works independent to other application server instance and is managed independently using its own console. Although, this profile can later be added to deployment manager (DMGR) to become a part of bigger deployment, but normally it is used to prepare standalone application deployment. When you create this profile, a default application server instance named as server1 automatically gets created.
  2. Prepare system before creating profile.
    WebSphere Application Server relies on TCP/IP networking, so we must have TCP/IP correctly configured, and it is important that the host name of the computer remains unchanged.
    Login as a root equivalent user.
    Take the backup of the host file by running following command in terminal.

    sudo cp -rip /etc/hosts /etc/hosts.orig

    How to Create WAS Standalone Application Server profile
    Open the /etc/hosts file and ensure that proper host entry is present against your hostname
    How to Create WAS Standalone Application Server profile
    In below techinote is my machine hostname and 192.168.1.100 is machine ip.
    How to Create WAS Standalone Application Server profile
    Do the relative changes in your host file and save it. 

  3. Create WAS Standalone Application Server profile using Profile Management Tool.
    For Creating WAS Standalone Application Server Profile we will be using the Profile Management tool in the WebSphere Customization Toolbox.

    1. Open a terminal by pressing CTRL + ALT + t of your keyboard and navigate till utility location by running following command
      cd /app/IBM/WebSphere/AppServer/bin/ProfileManagement

      How to Create WAS Standalone Application Server profile

    2. Enter the following command to start the WebSphere Customization Toolbox:
      ./pmt.sh

      How to Create WAS Standalone Application Server profile

    3. The WebSphere Customization Toolbox opens to the Profile Management Tool. Notice that there are no profiles in the list. Click Create.
      How to Create WAS Standalone Application Server profile
    4. In the Environment Selection panel, select Application server to create WAS Standalone Application Server profile and click Next.
      How to Create WAS Standalone Application Server profile
    5. In the Profile Creation Options panel, select Advanced profile creation. This selection is where you can specify your own values for some settings. Click Next.
      How to Create WAS Standalone Application Server profile
    6. In the Optional Application Deployment panel, keep the default selections. Click Next.
      How to Create WAS Standalone Application Server profile
    7. In the Profile Name and Location panel, make the following modifications:
      Profile name: AppSrv01
      Profile directory: /app/IBM/WebSphere/AppServer/profiles/AppSrv01
      Click Next.
      How to Create WAS Standalone Application Server profile
    8. In the Node and Host Names panel, enter the following values
      Node name: techienoteNode01
      Server name: server1
      Host name: techienote
      Click Next.
      How to Create WAS Standalone Application Server profile
    9. The Administrative Security panel specifies whether to use initial administrative security. If selected, you specify an initial administrative user name and password, which are used for administrative activities such as console access.
      Verify that Enable administrative security is not selected and click Next.
      How to Create WAS Standalone Application Server profile
    10. In the Security Certificate (Part 1) panel, accept the default selection. Click Next.
      How to Create WAS Standalone Application Server profile
    11. In the Security Certificate (Part 2) panel, accept the default selection. Click Next.
      How to Create WAS Standalone Application Server profile
    12. In the Port Values Assignment panel, accept the default values.
      Note down port values of following. We need them afterwards
      Administrative console port
      Administrative console secure port
      HTTP transport port
      HTTPS transport port
      SOAP Connecter port

      How to Create WAS Standalone Application Server profile
      Click Next.
    13. In the Web Server Definition panel, accept the default value. Do not create a web server definition. Click Next.
      How to Create WAS Standalone Application Server profile
    14. Review the Profile Creation Summary panel. Click Create.
      How to Create WAS Standalone Application Server profile
    15. The profile creation completes successfully in several minutes. In the Profile Creation Complete panel, clear the check box for Launch the First steps console and click Finish.
      How to Create WAS Standalone Application Server profile
    16. The newly created profile is listed in the Profile Management Tool.
      How to Create WAS Standalone Application Server profile
  4. Verify creation of WAS Standalone Application Server profile.
    The First steps console is where you can start or stop the server, access the WebSphere Information Center, and start various tools. Each application server profile has an associated First steps console.

    1. To start the First steps console for AppSrv01 open a terminal window, navigate to the following directory:
      cd /app/IBM/WebSphere/AppServer/profiles/AppSrv01/firststeps

      How to Create WAS Standalone Application Server profile

    2. Enter the following command to start the First steps console:
      ./firststeps.sh

      How to Create WAS Standalone Application Server profile

    3. Verify that the server is created and starts properly by clicking on Installation verification.
      How to Create WAS Standalone Application Server profile
    4. The installation verification test tool runs and displays messages to indicate the verification status. Use the scroll bar to view all messages. At the bottom of the message list are the messages (some errors and warnings before the final success messages are expected):
      How to Create WAS Standalone Application Server profile
    5. Close the First steps output – Installation verification window.
    6. From the First steps console, click Administrative console to start the administrative console for AppSrv01. The application server from AppSrv01 is started in the previous step during the installation verification test. Since the server is started, the administrative console is able to connect to the running application server.
      How to Create WAS Standalone Application Server profile
    7. An WebSphere Application Server 8.5 Admin Console window will get open.
      Click Log in button to log in into the Admin console.
      Note that the default structure of AdminConsole URL is as follows:
      http://hostname:administrative_console_port/ibm/console
      Administrative console port is the port which I have asked you to note down earlier.
      How to Create WAS Standalone Application Server profile
    8. The main page for the WebSphere Integrated Solutions Console is displayed and looks like the following screen.
      How to Create WAS Standalone Application Server profile
    9. Using the administrative console navigation tree, click Servers > Servers Types > WebSphere application server. This will show the name of the server. In our case it is server1
      How to Create WAS Standalone Application Server profile
  5. Start and Stop the WebSphere Application Server.
    We can start and stop the WebSphere Application Server in AppSrv01 profile through command line. There are a number of command-line scripts that help you manage the application server.
    Three of the most useful are startServer, stopServer, and serverStatus.

    1. Check the status of the application server using serverStatus
      Open a terminal and navigate to the bin directory of AppSrv01

      cd /app/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

      How to Create WAS Standalone Application Server profileUse following command to verify that server1 is running

      ./serverStatus.sh server1

      How to Create WAS Standalone Application Server profile

    2. Start the application server.
      Open a terminal and navigate to the bin directory of AppSrv01

      cd /app/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

      How to Create WAS Standalone Application Server profileUse following command to start that server1

      ./startServer.sh server1

      How to Create WAS Standalone Application Server profile
      After the authentication is complete, the server status is displayed indicating that
      server1 is started.
      How to Create WAS Standalone Application Server profile

    3. Stop the application server.
      Open a terminal and navigate to the bin directory of AppSrv01

      cd /app/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

      How to Create WAS Standalone Application Server profileUse following command to start that server1

      ./stopServer.sh server1

      How to Create WAS Standalone Application Server profile
      In the case of successful stop of the server you will see the following on the screen
      How to Create WAS Standalone Application Server profile

  6. Understand directory structure.
    Whenever we create a profile following directories get created.
    bin: This is for programs, scripts, and DLLs
    config: This is for configuration files
    configuration: This is for configuration settings
    etc: This is for dummy key ring, key files, plug in keys
    firststeps: This is for firststeps utility
    installableApps: This is for applications that can be installed
    installedApps: This is for applications that are installed in application server
    installedConnectors: This is for installed resource adapters installedFilters
    logs: This is for trace and log files
    properties: This is for configuration property files that WebSphere uses
    servers: This is for server configuration
    temp: This is for temporary area for files that are created during JSP processing
    tranlog: This is for transaction log files
    wstemp: This is for temporary area for events
  7. Check log files.
    A number of log files are created during the installation and profile creation process. Click the image to see it in better resolution.
    How to Create WAS Standalone Application Server profile
  8. Access the default Application.
    As we have choose to install default Application, we can access snoop page.
    Before accessing the page ensure that Default Application is started. To check the same, access the Administrative console. Navigate to Applications > Application Types and click on WebSphere Enterprise Applications.
    How to create WAS StandAlone Application Server
    Ensure that Default Application is in start mode. (If you see the green icon in application status against Default Application, it means that Application is started. Red icon means that application is shutdown.) If it is not started, select the Default Application and click on Start button.
    How to create WAS Standalone Application Server

    Once the application is started you can access snoop page by accessing following url:
    http://techienote:9080/snoop
    In above 9080 is the HTTP Transport port. The page looks like below:
    How to Create WAS Standalone Application Server

Hope you have liked this tutorial. Do comment and let me know in case of any issues or error.

If you find any missing point in here, please let us know in comment section or tweet us at @techienotecom. To get more articles like this, subscribe to our RSS feeds.

How to Create WAS Standalone Application Server

One thought on “How to Create WAS Standalone Application Server

  • February 6, 2016 at 11:07 pm
    Permalink

    Your website is very useful.

    Thanks !!!!

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.

Recommend on Google