SLD Migration

Hi All,
Currently we have central SLD configured in solman system. Our EP development system is connected to the backend system using JCo via SLD in solman. Under this circumstances if we shutdown the solman system in order to upgrade it (hardware migration and EHP 1 upgradation) our EP development system and production system stops working as connection to SLD is lost. So we have only one solution :
Create local SLD in EP dev and PRD and point EP servers to their local SLD. We did this activity in EP dev and local SLD in EP dev is working fine. Now I have following questions,
1) after changeing the SLD information in SLD data supplier in J2ee admin tool all the JCO information in EP is lost. we have almost 25 JCo s in EP dev. The error has been identified. This local SLD does not contains all CIM data as it was in solman's SLD. So how do I export SLD data from Solman to local SLD created in EP dev?
2) Is there any way to change SLD while keeping all Jco data intact in side EP system?
Any help would be highly appreciable.
Thanks and regards

Hi All,
My first issue is resolved. I was able to export data for all technical system and landscape as well. But currently my biggest concern is that information for all JCo connection, those were working before moving SLD, are lost. So in "content administration -> webdynpro -> maintain JCo connection" all JCo are in the initial stage, ie, Test, Ping, Edit, Remove buttons are disabled. So only option is to create all the JCo once again. Is there any way we could change SLD without tampering JCo connections? I have an idea my my mind...probably we could retain the Jco data while moving SLD if we follow the below mentioned order..
1) Target SLD should not be in running mode.
2) create necessary user for SLD administration
3) Import all technical data and SLD data from old SLD to New SLD.
4) Run new SLD
5) Configure SLD bridge
6) Change SLD data supplier in J2ee Admin and point it to new SLD
This way we may ensure that our New SLD contains all the technical information, as was in old SLD, before changing the SLD information in SLD data supplier. Could somebody verify the same?

Similar Messages

NWDI & SLD migration to NW7.3

Dear all,
We are running NWDI 7.01 SP10 and are planning to upgrade to NW CE7.3 with usage development infrastructure.
Can NW CE7.3 be installed first and then can the tracks be exported from the old nwdi and imported to new NWDI CE?
In this scenario, we are also planning to install or upgrade the SLD's (version 7.0) to NW7.3. What should the sequence be, first SLD and then NWDI or does it matter? In the case of the SLDs, can the SLD repositories also be exported and imported to new environment?
Is there any relevant documentation on this kind of migration?
Thanks!
Neeta

Hi,
I can suggest the NWDI system copy guide:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70ee5ab2-8d7a-2c10-d88b-dbe2fdf666e7?QuickLink=index&overridelayout=true
Best Regards,
Ervin

SLD Migration question

Hi Team,
We recently did SLD migratin as per note :- 720717 ( Reduce the number of System Landscape Directories (SLD) ).
Now when we execute tx.code SXMB_IFR -
> It opens a page with XI tools like integration builder, SLD etc---->after clicking to the SLD it points to the old SLD.
Please let me know if nybody has idea how to change it?
Best Regards,
Tushar.

Hi Tushar
Firstly I highly recommend backing up the source SLD with a full backup, export ALL and individual exports of each export line LD, CR etc and keeping it alive it until migration is complete
Its possible that the old SLD location is still cached - was the cached cleared ?- were all locations where the SLD URL was defined in XI, API, data supplier connections and business systems (and business system definitions)
changed to reflect the new SLD URL ?
Was the target SLD already live and being used with other ABAP clients or has it been freshly installed and empty - at the same time was any import made into the target SLD (from source SLD) - other than CIM from /swdc?
Best wishes
Stuart

SOLMAN 3.2 LIS to SLD Migration

Are there any notes on this? We'd like to move from LIS to SLD. Other than needing the Java stack is there any other gotchya's?
M.
Message was edited by: Michael Brierley

Hi stefano
Try this link. Found it to be usefull info for us.
http://help.sap.com/saphelp_nw04s/helpdata/en/11/0dfe55e0c8fc4e910706a47ca6859b/content.htm

Migration of local SLD to Central SLD on different host.

Hello Experts,
We have migrate the local SLD existing on the SAP PI System to a new Central SLD on a different host on SAP Solution Manager system.
I followed the OSS Note 720717, which contains the description of the changes that have to be exectued in the SAP XI/PI Environment, during the SLD Migration. This note does not give any details of the description of changes for the other SAP Systems such as SAP ECC, BI etc registered in the SLD.
Can anyone provide the OSS Notes, SAP Doc URL or the steps on how to migrate the local SLD existing on SAP XI/PI System to the new Central SLD on the SAP Solution Manager system.
Thanks for help in advance.
Best Regards,
Haleem

Firstly
I recommend to avoid having 1 SLD for multiple clients - like Solution Manager, BI, ECC
This is because clients may end up having conflicting requirements for the same SLD
- for example the small user group for Solution Manager may have a flexible and easy going policy on J2EE downtime
- but if you take down the Solution Manager J2EE that houses the SLD and PI uses this SLD - then you could have a severe affect on PI useage
Secondly
Although you can migrate content - this still does not guarantee the target landscape will work
- you may still need to manually re-implement target landscape configuration
let me give you an example
SLD 1 is being moved to SLD 2
Portal 1 is pointing to SLD 1
Even if you migrate the content of SLD 1 - including the ECC and Portal technical system landscape information
Portal 1 is still pointing to SLD 1 - this then needs to be manually re-pointed to SLD2
and that might not be all the complete steps either !
The complete steps of migration from the client side may not be available (I have found only steps to
migrate SLD content not migrate client use of the SLD)
- they may only be available as the documentation for the original configuration steps required to step SLD and the client
- therefore when migrating SLD you must go through the client setup documentation for SLD and check your
target landscape is consistent
Lastly - other considerations include
Lets say you also export model and CIM content from SLD 1 to SLD 2 - this means SLD 2 has an import line from SLD 1
- if you decomission SLD1 then you need to switch the import line which is not recommended - this could cause severe problems and may require you to create a new import line to upload content from SAP /swdc (which you need to keep the SLD bug free and latest definitions)
Just a few thoughts on issues you may encounter
Best wishes
Stuart

SLD/JCo Migration to new host

Dear Experts,
I have gone through many posts but still not able to understand fully the procedure to migrate SLD from one host to another. So its my humble request you to read my issue and guide me.
We have a situation that we have moved from physical to virtual host on our SLD. But when I shutdown the previous host, my ESS/MSS on Portal stops functioning.
My Landscape is : Portal 7.1 - Old SLD -- Was serving as both Solution Manager and SLD (for around 20-30 systems)
Now we want to move the OLD SLD to a new host, -- New SLD -- Will serve as SLD for all systems.
There is one production Portal system which has ESS/MSS with Jco's, it is currently pointing to OLD SLD. When I login to OLD SLD and search for my Production Portal, I can see that it has few Jco Destinations and few "deployed objects" as shown in screenshot below
These are the steps I have followed in my new SLD.
1. Went to Visual Admin of my Portal system -- Changed SLD Data Supplier (CIM) to NEW SLD. Restarted Portal
2. Logged in to new SLD and created JCO Destinations (exactly same as in OLD SLD)
This is my NEW SLD, I cant see the "deployed objects" but i have created the JCO destinations (manually)
But then, I am getting errors in ESS/MSS Applications for Jco related.
Can someone please help me in figuring out what I am missing ??
1. Importing CIM data in new SLD from old SLD ??
Any guidance on this will be helpful.
Thanks,

Hi Rajat,
Take a look at More on System Landscape Directory. There are several blogs there that talk about migrating from one SLD to another. (Especially Switching between 2 SLD Systems in Sync with an LMDB or a 3rd SLD).
It sounds to me like you changed the setup for the data supplier side, (so your new SLD has the correct data) but you haven't changed the SLD-client setup of the portal (so your portal doesn't know to look at the new SLD for data). Take a look at this SAP help document, Synchronizing the System Landscape Directory with the Portal, and see if you can find what you need there.
I hope this helps!
Best regards,
--Tom

Migrating from one SLD to another

Hello,
We are trying to migrate from an SLD on 6.40 to an SLD on 7.0. The SLD 6.40 will remain until all systems are on the 7.0 box. Can we do an export/import of the Technical and Business Landscapes, or doe we have to re-register each system using RZ70 on the new SLD?
thanks,
Eric

Hello,
It's better to use export / Import to get the same UID define on XI System.
And then you can re-register all your systems to this new SLD.
Best regards,
Chris

Migrate SLD

Hi all,
is here anyone who has experience with migrating a SLD?
I have succeeding situation:
I installed a development NetWeaver system with a SLD. A few months later I installed the production NetWeaver system with a SLD, too. Now I want to migrate the development SLD to production SLD and after that I want to delete the development SLD. Are there any tutorials or help documentation's how I can execute this?
Thanks
Florian

Hi,
Please take a look at SAP Note 935474.
Regards

Possible to migrate installation w/ SLD to new system using 'tar'/'untar'?

I have a CRM installation with TREX, that I need to move from one unix system to another (same patch level). As SLD is setup, can I 'tar' the entire installation on the old system, 'untar' the bundle on the new system, and bring the SAP setup back into function mode? It should be doable if SLD is not setup. But since there is SLD bundled in the setup, I am not sure if 'tar' is the way to port the installation. I can give the new system the same hostname, but ip address would be different. Any pointer is highly appreciated! Many Thanks!

Hi,
You can perform asystem copy, even SLD can be set up later accroding to your need.
Regards,
Vamshi.

Defining an SLD Strategy for XI Migration using CMS

Can the following scenario occur? Please explain if any of my assumption are incorrect.
-> An XI DEV, QA, and PRD environments each with a separate "slave" SLD.
-> A separate "master" SLD that contains all XI dimensions (i.e. transport, solution, and technical).
-> This "master" SLD will deploy all relevant SLD components (Products (versions), SC (versions), Technical Systems, and Business Systems) to the specified SLD "slave" environment. For instance, the master SLD will provide only DEV SLD components to the DEV "slave" SLD specific instance. No QA or PRD SLD relevant components will be stored on the DEV "slave" SLD.
-> All Integration Repository (IR) and Integration Directory (ID) objects will be exported from DEV "slave" SLD and imported into the "master" SLD.
-> All ID components will have transport targets defined in the master SLD for DEV to QA and QA to PRD, respectively.
-> CMS will perform all transports from DEV to QA and from QA to PRD for both IR and ID components by defining "tracks" for specific SC and development configurations for each of the development states of an SC.

The following scenario can occur. That's what we're doing at our customer site.
-The only thing is that you can import QA and PRD relevant components to DEV. If you want to define the transport targets between the systems, then this information will need to be the individual SLDs (slave SLDs).
I hope this helps.
Regards,
Jay Malla
SAP XI Consultant
Licensed To Code

Migrate local SLDs to a centralized SLD

We are in a big SAP project with one full landscape for each new SAP product (e.g. SRM, ECC, EP, BI, etc.)
We have a centralized SLD on a SM7.0.
We have 2 options when installing each system:
1) use the centralized SLD for each new install
2) use the local SLD for each new install, then change all local SLDs to the centralized SLD.
What will be the pros and cons of each option?
Thanks!

Hello Linda,
Eventually ,you want to register your systems to the central SLD.
You can do it in both ways,but during installation when you select the option of Configure a Local SLD SAPinst says that it will take longer time ,thats it no other issues.
So best is that you register your systems to Cenral/Remote SLD.The remote SLD should be running and available at that time.
Have a look at this blog /people/boris.zarske/blog/2008/03/21/sld-general-recommendation-how-to-set-up-the-system-landscape-directory , it will give you more wider view of planning the SLD.
Regards
Ajay

Two PI systems in same SLD when upgrading PI 7.4

We are upgrading SAP Process Integration (PI) from 7.11 to 7.4 with option new installation and phase out. We are going from dual stack to single stack and will have the two PIs running parallel for a longer period.
Which are the issues we can run into using same System Landscape (SLD) for both PI systems?
We found that it is not possible to have two Business Systems (BS) connected to the same ABAP Technical System with the same client. Will it be possible to reuse the existing BS, which is then still connected to the PI 7.11, for PI 7.4?
WIll it be possible in production SLD to switch the Integration Server for backend ABAP BS?
How did you setup the SLD when new installation?
Best regards,
Maria S. L.

I've never tried that scenario ( two PI environments ->one SLD) but why don't you handle them separately as it's a new installation.
I believe you will be decommissioning existing PI landscape(SLD) post migration.
Don't change any SLD connections until you completely migrate to newer version of PI.
1) Export the SLD content from existing system to new system(TS,BS,SWCV etc)
2) In the back-end system maintain separate connections to required environment at interface level.
Refer to below blog to know how to maintain IS_URL paramter at interface level.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?overridelayout=t…
3) once you migrate all your interfaces change then change SLD pointers to new PI landscape.

Random JCO Communication Failure Error after Hardware Migration

Greetings experts,
we had a migrated our XI server to new hardware and had couple of SLD related issues which were solved by the migration team. However, we are getting JCO communication failure very frequent whenever we use JCO from JAVA to call an RFC. The weird thing, if you restarted the message it will be successful.
The error message in the message monitor :
"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection"
Any idea to solve this random issue?

Hi again,
the number of connection was increased to 200 but with no effects. Also, the user used to connect is a system user which does not need a ticket.
This is my connection code
               mConnection = JCO.createClient("600", // Client
          "USER", // Username
          "PASSWORD", // Password
          "EN", // Language
          "hostname", // Host
          "01"); // System Number
do I need to add anything else if I am using a clustered system?

PI 7.0 DB migration

Hi
We are using PI 7.0 (Windows environment).This is HA/Distributed environment
PI Application and DB both are running on different host with Microsft Cluster technology for HA
We wanted to move DB instance (only DB as we do not want to make any change into Application) on Linux or Solaris Server
Do we just need to use statndard OS/DB Migration system copy Guide for DB instance move to another server? We also want to have HA for DB after moving to new server
In addition to DB migration do we need to make any changes for below configuration after DB move to new server?
1. Change in PI Exchange profile file
2. SLD Configuration Changes
3. JCO Connection configuration Change
4. Visual and Configtool related changes
I appreciate expert opinion on this
Thanks in advance
Thanks
Deelip

Hi Deelip,
You need to use standard OS/DB migration, though in this case you are just migrating your DB and not application, but it is advisable to run sapinst on both servers because I am assuming that generally hostname naming convention for Windows and Unix/Linux changes plus your listener settings on application server will also change,
....but if you do not wish to run migration sapinst on your app server then you need to do manual changes on app. server for listener and your DB hostname should not change.
Then you need to check "R3trans -d" for ABAP part and you need to check Configtool is getting connected or not.
Let say you will be successful in making your java up in that case also you need to send your new data to SLD, check your SMSY, LMDB for correctness of DB server information.
When your java will be up, then VA and JCo should not be an issue.
Unless you don't have enough time to go through this experimental process. Please run migration on both servers and follow PI db copy documents also for few missing post steps.

XI 2.0 to XI 3.0 migration

Hi,
We are currently migrating our Xi 2.0 landscape to our new XI 3.0 system. (we are following the "Component Upgrade Guide - SAP Exchange Infrastructure 3.0.pdf" Guide)
While doing the point "Import of the Integration Directory" of the "Integration Builder Migration from XI 2.0 to XI 3.0" step in the data migration tool, we good the following error:
-04-13 15:57:11)
The following import entities will be imported: "XI2_0_Endpoints_Security.tpt", "XI2_0_Mapping.tpt", "XI2_0_Scenario_Routing.tpt" (2005-04-13 15:57:11)
Starting import of import entity: XI2_0_Endpoints_Security.tpt (2005-04-13 15:57:11)
Data import canceled: Unable to migrate end point to communication channel (, TSTFTP, MigratedReceiverChannel_XIConnectivity_0): No SLD elements of type SAP_XIAdapterFramework found (2005-04-13 15:57:14)
I have found SAP Note: 742694, which seems to have the solution for this, but this does not solve the problem.
I dont see 13 associations in: http://<sld host>:<sld j2ee port>/sld --> Administration --> Content Maintenance --> Select 'XI Adapter Framework'.
Does anyone had similar problems while the migration of XI 2.0 to XI 3.0?
Thanks in advance for any hints.
Nesimi Buelbuel

Hi Ashish,
when you are logged into the SAP Service Marketplace just goto Release & Upgrade Info, Installation & Upgrade Guides, SAP Netweaver, Release 04, Upgrade, Component Upgrade Guide - SAP Exchange Infrastructure 3.0
HTH
regards
Nesimi

SLD Migration

Similar Messages

Maybe you are looking for