Prev
Next
Forums Infor / Lawson Platforms S3 Security

Copying Security from Prod to Test

 4 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
Ronald
Basic Member
Posts: 24
Basic Member
5/1/2013 8:49 PM
    I need to find a way to copy the xml file from production to test.  In my current process, I create/edit/add/remove security in production but don't always make the same changes in Test.  I need to find a better way to keep security in test the same as production.

    I heard this can be done, but I have not seen anyone do it.

    Any suggestions?
    Greg Moeller
    Veteran Member
    Posts: 1498
    Veteran Member
    5/1/2013 8:59 PM
      Can I assume that you are talking about LSSecurity? Then, yes, I have a suggestion.

      You can run lsdump at the PROFILE level... I've used this a couple times before, and at the PROFILE level it loads much, much faster than doing it at the SECCLASS level, plus gets you everything in that profile.

      When loading, make sure that you specify a -p option to lsload if you have changed profile names in test.
      Ronald
      Basic Member
      Posts: 24
      Basic Member
      5/2/2013 1:18 PM
        Yes, I am talking about LSSecurity. I am needing to update the RM part of security more than the Profile/Security Classes. Is there a different way in doing this?
        Greg Moeller
        Veteran Member
        Posts: 1498
        Veteran Member
        5/2/2013 2:09 PM
          I've never done this, and I'm SURE that it isn't supported, but you could use a tool like JXplorer, connect to your LDAP and export/import branches. Look under o=lwsn,o=lwsnrmData and you'll find your Groups, Roles, Structures branches.

          *Note: NOT supported.
          Michael
          New Member
          Posts: 1
          New Member
          5/6/2013 8:50 PM
            RM updates can be done in one of two ways.

            1)  RM Update Node in Process Flow Integrator.  Use the Data Iterator to read in a CSV file and make the updates where needed.  Test the return code for success/failure.  Note that RMID CASE matters.

            2)  loadusers.  Testing this going from LAUA to LS was not favorable, could not control in the fine grained manner we needed.  Requires some prep work with a CSV to XML generator; docs are terrible here. 

            Opted for #1.  5000 ESS, 350 MSS, 500 RQC and 200 core roles migrated in an afternoon!