on 01-22-2007 7:01 PM
If I want to migrate an SLD from one instance to another, is it a matter of exporting all the content in SLD A and importing into SLD B, and then updating all the child systems to point to the new SLD (ABAP tcode RZ70, or J2EE admin config)?
Both SLD A and B in my situation are the exactl same NW04s release/patch level. I need to migrate from A to B because B is in an HA enviornment and A is not. As a result, some production web dynpro apps that rely on the SLD don't work if SLD A (dev) is down.
I just want to do this as simply as possible.
Hi
I would suggest you to make B as central sld and divert your SLD A to B.You can do this easily.Now both SLD A and SLD B can talk.Now as you said few production web dynpro apps require HA ,you can list these servers in SLD B.You need not change any other thing.
This is just one solution which came to my mind.There can be other solutions also.
If you face any problem in making SLD A and SLD B talk.Let me know.
Please reward points:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.