on 05-21-2008 9:19 AM
We have a requirement to Integrate around 30 non SAP applications to SAP. For this purpose how do we design the SLD, with respect to creating Products, SWCV's, TS and BS for the Third Party/Legacy applications?
Are ther any Best Practice available for the same?
What are the advantage and disadvantages of making only one Third party SWCV and one Business System, keeping in mind that our landscape is very dynamic (applictions changing as well as moving in and out frequently).
Hi,
This holds good for development server.
For this purpose how do we design the SLD, with respect to creating Products, SWCV's, TS and BS for the Third Party/Legacy applications?
Products and SWCV are independent on Business Systems.
whereas technical and business systems are dependent on product and SWCV.
According to your requirement create
one product, one Software component under that product
Or u can use existing product and Software component.
Create technical system as third party in technical system assign that product and SWC.
Create a business system and assign that technical system to that business system.
In integration directory u can use same business system for all
30 non sap systems.
Are there any Best Practice available for the same?
Hope this link will help you better.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/workingwithSystemLandscapeDirectory+%28SLD%29&focusedCommentId=52775#comment-52775
Regards,
Pradeep A.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We found multiple TS and BS suitable for our landscape, but are going with single SWCV.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you all for your answers, but I'm not looking at Planning Guides or Transport Strategy for SLD. We have already sorted that problem.
What I want to know is that is a good idea to, just keep just one SWCV and one business system to represent all Third Party systems. We don't want to create SWCV and BS for all Third Party systems because of future maintainance and huge number of dependencies when dealing with large number of them.
So my question is that, will one SWCV and one BS cause any limitation, in future if our organization landscape change (impacting the interfaces, either they become obsolete or change) or while configuring the Integration Scenarios.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
So my question is that, will one SWCV and one BS cause any limitation, in future if our organization landscape change (impacting the interfaces, either they become obsolete or change) or while configuring the Integration Scenarios.
They will not cause any impact, u can configure with one SWCV and one BS on development.
But in production we have to configure with one SWCV and N BS giving their original host names.
Even though if organization structure change it will not affect any interfaces (IR objects).it will affect only ID objects.
Regards,
Pradeep A.
Hi,
We can define in one Product and SWCV's, we can use the one technical system also if all are belongs to same category.
means :
Web as ABAP -
> For SAP applications.
Web as JAVA -
> For Enterprise java applications on J2EE stack.
Third party -
> For People soft, BAAN, JDEdwords, ...........
Standalone Java -
> For File system/Databse system/Mail server/HTTP server.
SLD -
> For Business to Business systems(i.e. its for external SLDs).
Business system specifies the role of the technical system,If we are using the same type of data then we use the same business system.
To handle SLD stuff
Configuration of central SLD
/people/praveen.mayalur/blog/2007/05/31/configuration-of-cms-in-central-nwdi-sld-to-transport-xi-objects
Best practice
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/workingwithSystemLandscapeDirectory+%28SLD%29&focusedCommentId=52775#comment-52775
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Avishek
depending upon your requirement follow these guides
Planning Guide - System Landscape Directory.
Technical infrastructure guide
https://websmp108.sap-ag.de/~sapidb/011000358700005531212005E.pdf
regards
sandeep
if helpful kindly 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 |
---|---|
91 | |
10 | |
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.