Websphere 7.0 ND installation

 55 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Page 3 of 3 << < 123
Author
Messages
SP
Veteran Member
Posts: 122
Veteran Member
    I am in the same boat as Colleen (Windows 2003).

    Tom, can you send me your documentation? I have David's, but really need assistance with this in a Windows setting.
    Sampath S
    Basic Member
    Posts: 17
    Basic Member
      Hi John,

      Can you please share the steps for COBOL and Bouncy Castle...

      Thanks in advance.
      Sam
      Greg Moeller
      Veteran Member
      Posts: 1498
      Veteran Member
        I know that this is a particularly old thread, but to answer brihyn's question about getting the node and server1 to be services under windoze:

        Start a command line, navigate to %WAS_HOME%\AppServer\bin
        execute
        wasservice.exe -add "nodeagent" -serverName "nodeagent" -profilePath "D:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01" Making sure that you specify the profilePath correctly.

        Do the same for server1:
        wasservice.exe -add "server1" -serverName server1 -profilePath "D:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01" Again, make sure you specify the profilePath correctly.
        Skippy
        New Member
        Posts: 1
        New Member
          I've found with Windows, rather than creating a service to start the application server, it's best to go into the properties of the application server, under 'Java and Process Management', click 'Monitoring Policy', and check off 'Automatic Restart', and set 'Node restart state' to 'Running'.  What this will do is when the Node Agent service starts, it will start any JVM's that have 'Node restart state' set to 'Running'.  Also, in the event of a JVM crashing, the node agent will detect that it has gone down and attempt to restart it.
          Phil Romov
          Veteran Member
          Posts: 44
          Veteran Member
            Posted By DavidV on 08/11/2010 07:31 AM
            I think you'll find Tom's is much better than mine, but here you go.

            David, thanks, that helped a lot.

            For the record, I was able to skip a lot of steps, and streamline the process, only because I was working off my own experience before I got stuck (didn't realise IBM HTTP was a separate install from WAS) and took a look at your doc

            Basically, what I did to upgrade WAS from 6.1 to 7.0 (on AIX 6.1) is:

            Download websphere app server ND from lawson (filenames/links could be different depending on your platform)

            IBM® WebSphere® Application Server ND (64bit) Network Deployment V7.0 for AIX on PowerPC 64-bit (1 of 2) C1G15ML.tar.gz https://mylawson.lawson.c...wnload?dwnldID=55686

            IBM® WebSphere® Application Server ND (64bit) ND v7.0 for AIX PowerPC 64-bit (2 of 2) C1G2QML.tar.gz https://mylawson.lawson.c...wnload?dwnldID=58288

            WebSphere Application Server Network Deployment v7.0 for AIX on PowerPC 64-bit C1G2SML.tar.gz https://mylawson.lawson.c...wnload?dwnldID=58289

            IBM® WebSphere® Application Server Installation Factory v7.0, AIX 64-bit C1G2RML.tar.gz https://mylawson.lawson.c...wnload?dwnldID=55685

            Not sure if every one of these downloads was required, but I picked the safe side

            I ftped them all over to my server, gunzip and untar each of them in the same directory

            Got my xwindows all set up with the DISPLAY variable, and went to WAS/, ran the install there to install was.  Then installed the three ear files in the was console (:9060/ibm/console or :9062 if you have to webspheres, etc) as per KB 559370

            Then went to IHS/ ran the install there to install http server.  Then created its entry stub in the ibm console, then generated and propagated the plugin.  Now, the http server wouldn't start from ibm console, but I was able to start it manually using apachectl start.  Once it got running, ibm console was able to stop and start it.

            Now, before all this, I had also installed java 6 and set up bouncy castle successfully there (kb 550334)  And now I have portal working, so everything seems to be running.  However, I am aware that bouncy castle should also be set up on the was java, and I haven't done this step yet, so I'm curious how everything is working (edit: I actually had to do this step as well).

            (Also, I learned after update 5.3 -> 6.1 you need to reinstall lawson core, kb 5431593 )
            Phil Romov
            Veteran Member
            Posts: 44
            Veteran Member
              Update - you DO need to install fixpacks for was!

              Parts of lawson will not work with WAS 7.0.0.0 (even though some parts will) for me it was batch job submission, servlet/ioscacherefresh failing. Upgraded to 7.0.0.23 and they work now
              Page 3 of 3 << < 123