Websphere 7.0 Install in a seperated App / Webserver Env

Sort:
You are not authorized to post a reply.
Author
Messages
BBryant
Advanced Member
Posts: 23
Advanced Member

    I am being asked to create a test environment for our Lawson environment on a new set of servers.  I have never done this before and got all the prereqs set up correctly.  I am stuck on the IBM WAS install.  I located the instructions for a single server install on schronce.net and have been going through them to determine what I must do where.  The problem I have is I go through what I think is the correct install procedure, but I never see an app server listed in my services.  I have never installed IBM WAS before so sometimes I second guess myself on the install.

    Webserver - IIS /  Websphere Web Server Plugins
    Appserver - Websphere Application Server

    When I got the test environment a website was already defined in IIS for LSF9 and I went through the Lawson Environment Install Guide to make sure it had all the options it needed loaded.

    Listed below are the steps I am taking when I try to install this.

    On application server machine:

    I start the WebSphere App Server Network Deployment.

    I choose the combined Node Manager / Application Server as the type of environment.

    I enable admin security and give it the username and password.

    I make sure the path it installs to has no spaces (C:\IBM\...)

    This installs Websphere.

    According to my instructions (from the Shronce website) I am to use the Profile Management tool to do the following:

    Profile Management Tool >> Application Server >> Advanced Profile Creation >> Check all 3 Options (I only have two)

    >> Name the profile (afclsftest1 in my case)

    >> Change the install directory to match the name of the profile

    >> Make this profile the default one

    >> Changed the node name to servernameAFCLSFTEST

    >> Left host name as the default

    >> Enabled admin security (same as above)

    >> It says to leave the default ports as is, but this increments them all by one (9081 and 9444 for example)

    >> Run as windows service w/ local sys account (automatic startup)

    >> Did not create webserver definition

    * I note the profile management tool will NOT allow me to Augment an existing profile.

     

    Reboot

     

    On webserver machine:

    >> Launched Web Server Plugins install

    >> Select MS IIS6

    >> Chose Websphere App Server Machine (local)

    >> Changed install directory to match above folder structure

    >> Location of websphere app is C:\IBM\websphere\appserver

    >> Chose the afclsftest1 profile, port 80

    >> Named webserver as afclsftest1_web

    >> Used default location for plugin-cfg.xml

     

    Webserver DOES have an sePlugins subdirectory.

     

    Created associated Lawson directories:

    D:\afclsf1\gen\bin

    D:\afclsf1\gen\cgi-bin

    D:\afclsf1\law

    D:\afclsf1\db

     

    From the Websphere admin console on the app server:

    >> Servers >> Application Servers >> afclsftest1_app >> Java and Process Management >> Process Definition >> Java Virtual Machine >> Custom Properties

    >> Added values for the following:

    com.lawson.gendir

    com.lawson.lawdir

    com.lawson.ladbdir

    com.lawson.logdir

    >> Under the java virtual machine added the class paths to mimic the ones on our working server (pathing is the same, verified)

    >> Under Java and Process Management >> Process Definition >> Environment Entries, added the following variables w/ values:

    GENDIR

    LAWDIR

    LADBDIR

    COBDIR

    PATH

    LAWENVNAME

    >> Application Servers >> afclsftest1_app >> Web Container Settings >> Web Container Transport Chains (recorded ports for wcinbounddefault and wcinboundefaultsecure)

    >> Environment >> Virtual Hosts >> Added a virtual host named afclsftest

    >> Clicked on afclsftest >> Host Alias >> New >> Added following entires:

    * 80

    * 443

    * WCInboundDefault (9081)

    * WCInboundDefaultSecure (9444)

    * 5060

    * 5061

     

    Restarted application server.

    *** NODE MANAGER is not running upon reboot

    ------------------------

    I am having difficulties finding someone who has instructions on how to set this up with a seperate webserver and appserver.

    I won't go over how many times I have uninstalled/reinstalled WAS because I could not get this correct.

    I tried to start the node agent from the command line (startNode), but get this:
    The node agent on node orldw023Node01 must be started to perform the restart operation. Node agents in stopped state can not be started from the console.
     

    LSF 9.0.0.7 App 9.0.0.7 Win 2003 SP 2 Websphere 7.0 SP 5 SQL Server 2008
    MattM
    Veteran Member
    Posts: 82
    Veteran Member
      Try reinstalling and use the default app server (server1) that is set up. If the node agent will not start still, try patching the WAS install using the update installer. This will often times correct the issues with startup. The only difference with a remote web server is that you need to copy the plugin-cfg.xml from the app server to the web server. Also, have you run your 'configurewebserver' script?
      BBryant
      Advanced Member
      Posts: 23
      Advanced Member
        Where would I find the 'configurewebserver' script?
        LSF 9.0.0.7 App 9.0.0.7 Win 2003 SP 2 Websphere 7.0 SP 5 SQL Server 2008
        Jimmy Chiu
        Veteran Member
        Posts: 641
        Veteran Member
          your configurewhatever script is on your webserver websphere install directory\bin
          copy that to your appserver websphere install directory\bin and run it.
          BBryant
          Advanced Member
          Posts: 23
          Advanced Member
            Okay, it all seems to be going good now. Thanks guys!
            LSF 9.0.0.7 App 9.0.0.7 Win 2003 SP 2 Websphere 7.0 SP 5 SQL Server 2008
            You are not authorized to post a reply.