Migrating to new Domains

 8 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
mikebiggers
New Member
Posts: 2
New Member
    I am quite new to being a Law Sys Admin and was wondering how painful/painfree it was to migrate from an existing domain into a new domain as my organization is splitting away from the parent company.

    Both our dev and prod environments were installed using DNS and not ip addresses.

    Just so ya' know, we are using LCT 9.0.1

    Thanks~
    John Henley
    Posts: 3353
      Wow, that's a GREAT question!
      Since LSF is a fairly new product, I haven't seen any official documentation on doing this in particular, but I'll give you my ideas.

      I can think of following places you will need to look at:
      1. The easiest change is the "Users Group" on the Environment Configuration.
      2. If you're using ldapbind for AD authentication, you'll need to change that.
      3. The toughest part is the NT00xxxxx user mappings, etc. which is stored in the LDAP repository. You'll need to change those so they remain with the same NT000xxx names, but pointing to a different DOMAIN\USERNAME. You can do that by creating an XML file and running thru "ldifgen xmltosdataldif" / ldapmodify / ssoconfig.

      I would also assume that you'd want to dump/reload your LDAP repository so that it has a different DN/CN naming convention...
      Thanks for using the LawsonGuru.com forums!
      John
      Ganesh R
      Basic Member
      Posts: 16
      Basic Member
        Well, the LDAP is more painful. It is quite simpler if you have IBM Tivoli is used than ADAM.

        I know I've come across an article that explains on how to change the IP address. May be you need to have a look into it to get some clue.

        Meanwhile I'll try to think few more steps.

        Regards
        Ganesh .R
        Regards
        Ganesh .R
        ---------------------------------------------------------------------
        Lawson 8.0.3 Installation Certified
        Lawson 8.0.3 IOS & Portal Administration Certified
        Ganesh R
        Basic Member
        Posts: 16
        Basic Member
          Ok, this is what we discussed...
          0. Do a stoplaw & stop WAS
          1. Stop WAS, uninstall the applications (IOS, Lawsec & BPM)
          2. Uninstall WAS & IBMIHS and install them on this new domain, so that there aren't issues with these third parties.
          3. LDAP
          a. Export the LDAP content pertaining for this instance of Lawson. Open a text editor & change the values pertainaing to the domain & import back the values.
          b. Or manually search for all values pertaining to this domain & change the values.
          4. Change the domain values for the domain in install.cfg under $LAWDIR/system directory.
          5. Do a startlaw & check if things are OK
          6. Configure a new WAS application server for this instance of Lawson & install Lawsec, BPM & IOS respectively.

          Did this work?

          Regards
          Ganesh .R
          Regards
          Ganesh .R
          ---------------------------------------------------------------------
          Lawson 8.0.3 Installation Certified
          Lawson 8.0.3 IOS & Portal Administration Certified
          Barry Ghotra
          Veteran Member
          Posts: 63
          Veteran Member
            Ganesh, any pointers/docs on setting up LDAP using ADAM or Tivoli for LSF 9.0.

            Thanks.
            lawson_novice
            New Member
            Posts: 4
            New Member

              Ganesh,

              I see that you've had some previous experiencve changing domain names in Lawson.  In todays, version (LSF9) do you know of any documentation in regards to changing domain names and does lawson still certiify the product if this work is performed by our in house staff

              John Henley
              Posts: 3353
                Re: Migrating to new Domains <!-- Converted from text/plain format -->

                I have never heard of Lawson needing to come back in to recertify anything once it is installed. (And don't get started on that topic...) What you do with your system is your business.

                When you say "changing the domain name", that's not hard (it involves dumping and reloading via ssoconfig and some changes to Websphere and possibly your web server) as well as changing servenv.js on Portal, Studio, PSA, LBI (if you have those on separate servers).
                John Henley

                Thanks for using the LawsonGuru.com forums!
                John
                Kwane McNeal
                Veteran Member
                Posts: 479
                Veteran Member
                  John,
                  It's a bit more than that, if they are a Windows client. Your NTID-to-SID mappings would be broken too.

                  Kwane
                  954.547.7210
                  John Henley
                  Posts: 3353
                    Re: Migrating to new Domains <!-- Converted from text/plain format -->

                    Kwane, good point about the SIDs. I was thinking FQDNs vs. NT domains! 
                    John Henley

                    Thanks for using the LawsonGuru.com forums!
                    John