Prev
Next
Forums S3 Systems Administration

Migrate Lawson environment

Sort:
You are not authorized to post a reply.
Author
Messages
Xin Li
Veteran Member
Posts: 133
Veteran Member
1/6/2016 4:48 PM

    Due to  OS issue we need to migrate our Lawson environment to a brand new node. The new node will have same IP, hostname and same OS version. We are running Lawson on AIX 6.1, WebSphere 7 and Oracle 11g. All are on same AIX box. Our host team will copy everything over from current node to the new node. Anyone did such migration before? Were anything surprises we need to watch out?

     

     

    Kwane McNeal
    Veteran Member
    Posts: 479
    Veteran Member
    1/6/2016 5:04 PM
      I do these all the time. Make sure you know where your MF ServerExpress COBOL license keys are, as you'll need to reapply them.
      You'll also probably need to relicense BSI, since the hostid is changing, unless you're doing a new LPAR on the same physical server.

      Since everything else is the same, I don't see anything else needing to be completed, SO LONG AS, you're copying EVERYTHING (including stuff in the rootvg)
      If you aren't copying rootvg, then you'll need to grab a bunch of stuff out of the old server, and you'll need to fix some stuff in the new systems ODM for WAS7

      Kwane
      Xin Li
      Veteran Member
      Posts: 133
      Veteran Member
      1/7/2016 6:24 PM
        Kwane,

        Thank you for your reply. Do I need to worry about Bouncy Castle encryption?
        Kwane McNeal
        Veteran Member
        Posts: 479
        Veteran Member
        1/7/2016 10:11 PM
          Sorry for the delay on this, been a very hectic day...

          That depends. If you're using the system installed Java, AND you're not bringing anything over from rootvg (where it is typically installed), then yes. Otherwise, no.
          Now, depending on your LSF LDAP repository, you MAY need to change a few settings, dealing with location and startup, but I don't know enough about what you have to give you specific advice. Since the system is getting the same hostname AND IP, if the copies are done with the subsystems down, you should have nothing to do.

          The key, as I stated in my last post, is what you have in rootvg, and how you are handling the migration of it.
          Put your focus there, as the tricky bits are located on filesystems located in it.

          Kwane
          Xin Li
          Veteran Member
          Posts: 133
          Veteran Member
          1/8/2016 3:29 PM
            Thanks again for your reply, Kwane.
            To be specific, we use AD LDS for ldap running on Windows and our Web server is IIS. Both LDAP and IIS webserver stay with same windows servers. Only Websphere, Oracle database and Lawson environment plus cobol, perl, and java will be migrated to the new node. Any thing we need to pay attention to Websphere for gotcha?
            Kwane McNeal
            Veteran Member
            Posts: 479
            Veteran Member
            1/8/2016 4:01 PM
              As for LDAP, nothing I can think of, considering your position of the new system getting the same hostname and ip-address.

              WebSphere, also nothing, again based on the same presumption.

              Short of something unique to the way you're migrating the file systems and configuration that creates an issue, it should just start.

              Kwane
              You are not authorized to post a reply.