XI, SLD & multiple clients for DEV & QA

Ref: Re: 3rd party tech systems for multiple business systems...
I have a question regarding the avoidance of duplicated Configuration (Collaboration Profiles, Logical Routing & Collaboration Agreements) for different clients in the DEV/QA landscape.
As we know: many projects have multiple clients in DEV and QA. Here is an example landscape:
SXD_100 - Dev XI server
SED_100 - config dev
SED_200 - ABAP dev
SED_300 - unit test
SED_400 - sandbox
[ 1 technical system : 3 business systems ! ]
LDEV Legacy system
[ 1 technical system : 1 business system ]
SXQ_100 - QA XI server
SEQ_100 - clean config QA
SEQ_200 - ABAP QA
SEQ_300 - data migration prep
SEQ_nnn - yada, yada...
[ 1 technical system : nnn business systems ! ]
LQA Legacy system
[ 1 technical system : 1 business system ]
The problem:
SED_400->LDEV is used for prototyping integration
SED_100->LDEV is used for config development
SED_200->LDEV is used for ABAP development
SED_300->LDEV is used for unit tests
Receiver Determination is able to look into the message for a dynamic receiver, but we are not able to have a sender like "SED*"
The question:
Do we really need multiple sets of configuration in the Integration Directory? Is there a way to re-use the configuration for SED_100->LDEV for the other development efforts?
Any feedback would be greatly appreciated.
Rgds,
Derek

Hi Derek,
Since there can only one business system in SLD per client in SAP R/3.
e.g
SED_100 will have lets say BS_100_Dev
SED_200 and BS_200_Dev
In QA
SEQ_100 -> BS_100_QA
SEQ_200 -> BS_200_QA
It is not possible to configure the single scenario catering the Dynamic (multiple) sender agreement to Reciever.
But for QA you can use set transport target in SLD to reflect the BS_100_Dev -> BS_100_QA, where ever used.
This doesnot solve the problem of having dynamic sender service, it is just for information.
We also faced the same problem of testing a scenario from different clients of SAP :(.
Cheers,
Satish

Similar Messages

Multiple clients in DEV and QA for CHARM setup

Blog /people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario is an excellence introduction to CHARM setup.
However in real world, we have multiple clients on DEV and QAS systems.
Could you help explain how to extend the method in above blog to multiple DEV and QAS clients?
Thanks !

Hi Diana,
Please have a look at this thread :
Kind regards,
Stéphane.

Multiple clients for a RFC sender to SOAP scenario

All,
We have a RFC to SOAP scenario in our Development server and is working.
The problem we are having is - we only have one XI server available. But there are different clients in Dev that want to use this scenario now. Though we create the new BS for each of these clients, the issue i see is in the RFC sender communication channel. it needs to have the program id.
Right now we are creating a new program id for each of the clients(which translates to different RFC destination names on the ABAP side)... but that is causing a problem on the ABAP side - since the calling function is the same and they need some logic to change the RFC destination based on the client..
Are we missing something or is there a simpler way to this?
Thanks.

we created the exact same way you told... just add another business system. complete the receiver determination, interface determination and sender agreement.
It works every other time. When we checked the communcation channel monitoring - it will go to the client 210 once, and it would work. when we call the next time - it will error with a short dump in ABAP - but the error will appear on the communication channel for 250 (though we are calling from 210).
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'UD1CLNT250'/'RFC_UD1CLNT250', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'UD1#210' returned party/service of ''/'UD1CLNT210')
Any thoughts?

RMI: multiple clients for one RMI server?

Hi,
We're thinking of making a RMI Server.
However, can multiple clients access the same RMI Server at the same moment?
So, if one client is connected to the RMI Server, what will happen with the other clients that want to work to do the same thing at the same moment ?

all over the same port?
so for example, 100 clients can work simultaneously on this simple server?
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface OkServer extends Remote {
    public String getOk() throws RemoteException;
import java.rmi.server.UnicastRemoteObject;
import java.rmi.RMISecurityManager;
import java.rmi.RemoteException;
import java.rmi.Naming;
public class OkServerImpl extends UnicastRemoteObject implements OkServer {
    public OkServerImpl() throws RemoteException {
    public String getOk() {
     return "ok";
    public static void main (String args[]) throws Exception {
          System.setSecurityManager(new RMISecurityManager());
          OkServerImpl OkSvr = new OkServerImpl();
          Naming.bind("OkServer", OkSvr);
}

Defining SLD Target Systems for DEV, QAS & PRD

In a 3 tier XI landscape (DEV, QAS, PRD) which of the following two scenarios is best?
1. In the SLD define each DEV Business System with a target of the corresponding QAS Business System and define each QAS Business System with a target of the corresponding PRD Business System.
DEV ---> QAS ---> PRD
This means that we export ID objects from DEV and then import them into QAS. The objects then need to be exported from QAS for import into PRD
2. In the SLD define the DEV Business Systems with 2 target systems relating to corresponding QAS and PRD Business Systems.
DEV --> QAS
DEV --> PRD
This means that the same export from DEV can be used for import to both QAS and PRD.
Currently we have scenario 1 implemented but I am thinking of changing this to scenario 2 which I believe is a better solution as only one export is required and it is guaranteed that the same objects are being imported into QAS and PRD.
Any thoughts or comments?

Hi Mark,
I dont think thats a good thing to go with. When you are exporting, how are you going to control in CMS as to which environment you are going to export?
CMS itslef works on the principle of Develop->QA->PRD. This way, when you are in QA and found some bugs and fix them, you can export them all to QA. Finally you assemble them at QA and finally import them to PRD. This way, all the chaged objects later on would also get imported to PRD automatically.
Also As per my knowledge, in SLD, one target bus sys can have mulitple sources but the converse is not true.
VJ

Solman CHARM: adding multiple clients for quality/Production systems in Solar_project_admin

Dear Colleagues
We are using Solution manager 7.3. When we setup system landscape under a solution manager implementation project, we can only select one development and one quality/testing system.
Our scenario is that,
Development System:
D40 - 010 : (both workbench and customizing changes being done in same client)
Quality System:
Q40 - 010 : for customizing changes
Q40 - 000 : for work bench imports
So the querry is that, how we can add these two separate rows in Solar_project_admin and under tab systems:
ie D40-010 --> Q40-010 and D40-010 --> Q40-000.
Regards
Renjith

Hi Renjith
Please check below
Change Request Management scenario: Usual questions and known errors
Question no. 2 is more relevant for you
hope this answer ur query
Regards
Prakhar

Multiple clients in CRM Dev/QA system

Hi All-
I've seen in various places that it is recommended to only have one client in a CRM system. I have worked at many sites that have several CRM clients in a system without issues.
Can any one point me to an SAP Note or document that recommends only one client per CRM system? I realize that there are possible issues with the CRM pricing and cross-client customizing downloads but these can usually be worked around. What other issues are a concern?
Any SAP document about this would be great.
Thanks!
Tim

Tim,
Unless you are going to have multiple back ends or some business scenario that requires multiple clients in CRM Production, then don't do it in CRM Dev/QA.
The reason why don't do multiple clients in a CRM system that is connected to an ERP backend is the following:
CRM configuration is dependent on downloaded configuration from the ERP system.
A normal CRM system should only have one backend connection.
Now why would you want want to have a Dev and QA system that does not reflect how your production system works. In fact in the case of CRM you are making more work and creating systems that do not accurately mirror production.
The whole gold client concept in CRM is honestly a bad idea when you have single ERP backend, because it just causes more work for people and it my opinion its a way of people trying to stay busy than add real value.
Now if you really want to keep busy maintaining middleware and keeping things in sync, go for multiple clients in Dev/QA. The best part is when something in Prod breaks you won't have any environment that mirrors Prod correctly from a middleware perspective. In my opinion if you are that concerned about configuration and master data mixing then you probably need a CRM sandbox instance to try things out.
Take care,
Stephen

Purpose of Multiple Clients in Development Server

can anybody tell me the advantages and
disadvantages of having multiple clients in a
development server?

I don't think there is disadvantage when we have multiple clients for development system
DEV SAP system may have multiple clients..
Main pupose : Changes can be client dependent or client independent
Client-independent effects some clients.
Client-dependent effects all clients.
Let me say one example : Dev system has two clients
100 - Here we can write the code
200 - Testing will be here ( customizing will done here)
http://help.sap.com/saphelp_nw04/helpdata/en/8d/933d3c3a926614e10000000a11402f/frameset.htm
http://www.sap-img.com/general/what-is-sap--landscape.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/96/8a99386185c064e10000009b38f8cf/content.htm
Thanks
Seshu

BW can have multiple client?

Hello Experts,
is it possible to have multiple client for the BW System?
if yes please guide me in creating the one more client to our BW System. ( BW 3.0B).
and also give information about setting i want to ensure before creating client.
thanks in advance.
VHE.

Hello Vishwanath,
You can not work with multiple clients in BW.
OSS note 522569 gives the following explanation regarding the same.
In BW, master data IDs and dimension IDs are taken from number ranges. The BW objects against which the number range intervals are client-specific are cross-client objects. As the IDs must be unique, these may only be determined in one client. This means that BW can only operate in one client.
The BW objects are cross-client. They can be accessed and changed to the same extent in all clients. BW is displayed identically in all clients. In particular, there is only one Myself source system as this is used to generate the change log for ODS objects. Therefore, when the Administrator Workbench is started, the system checks to see whether you are working in the same client in which the Myself source system was created.
Regards,
Praveen

Working with one SLD for Dev, test

We have one SLD for dev, test enviroment.
We have 2 instance of XI(dev, test). Each XI system must be registered in SLD.
But how Adapter Engine, Integration Engine of SAP system (ABAP Proxy) will determine to with XI system to connect?
Is it right design?

hi Denis,
>>>>Is it right design?
one SLD is advisable for ALL XI instances
so don't worry it will work
refere to:
https://websmp104.sap-ag.de/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf
and
720717 - Reduce the number of System Landscape Direcotries (SLD)
>>>>>SAP system (ABAP Proxy) will determine to with XI system to connect?
have a look at : SXMB_ADM -> integration engine config
do you see the address ?
you always point one r3 client to only one XI instance
here
BTW
but having one SLD and many XI server is something different
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

What are the possible approches for hosting a product(custom SP application) for multiple clients on a single SharePoint farm?

We have a product which is a custom application based on SharePoint Foundation 2010. Right now, for each of our client we create a dedicated server and host the application in the standalone deployment. Now, the requirement is to host multiple clients in a
farm deployment.
Challenges are: 1. The product has same name for the wsp that is deployed on different client servers as of now. How to distinguish for different clients on same farm
Currently the product specific css and jquery is in 14 hive. These files will be of difefrent versions for different client. How to segregate that?
How many web applications is recommend to be created in a single SPF 2010 farm? What are the challenges?
There are a couple of DBs created in SQL for the application. What is the best way to separate those for the client?
Essentially its the same product but with different versions for each client that we want to deploy in a single farm. What is the best practice to tackle this?

For the most part, these are not SharePoint questions per se, but product-specific questions you'd better ask the vendor about. To get in some more detail:
1. It totally depends on the scope of the solution. If its global, then you're out of luck and any changes you make affect all instances that use it. Better ask the vendor about it.
2. Not that many, let's say < 10, assuming you're web applications have separate application pools. Check out http://technet.microsoft.com/en-us/library/cc262787(v=office.14).aspx#WebApplication for
more info.
3. This is very application specific and really should be answered by the vendor. Not related to SharePoint at all.
4. Again, really depends on the product so better ask the vendor.
Good luck!
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

Client strategy for DEV system in an implementation proj

Hi,
Can some one advise a good client strategy for an impl project? here's and example and questions i have. if you have a better strategy, pls advise. We want to follow this on ECC 6 DEV system -
10 - Sandbox (play around before doing config - no transports)
20 - Golden client (do real config here, and do development here - transports will start from here)
30 - Test client (for SCC1 testing)
I am assuming I should do DEVELOPMENT in the same golden client - does that make sense? Else, which should i have a new client? in that case, how will transports move?
Thanks for all your help

Hello Jerryp,
Our customer has similar setup:
100 - Sandpit
200 - Dev and Cust
300 - Testing
400 - Sandpit 2
Whenever we need to do any unit tests in client 300, we copy over customizing by using SCC1 transaction (client copy via transport request).
For example whatever development (code or customizing) we do in 200 is copied over to 300 by SCC1. This ensures the client dependent customizing is in sync with client 300 without destroying data.
Also, periodically we refresh client 100 and 400 and with data and customizing from 300. No development client independent changes are possible in the sandpit and testing clients.
Regards,
Siddhesh

Any plug-in for multiple clients

Is there any plugin for multiple client access to a given environment?
For example:
I have 50 clients to access the data on the server.
Should I do a layer of manual socket connection to handle the database reads and insertions?
Or is there a way to connect directly on the environment from clients to server?

It is unclear in your question what database you are talking about. Berkeley DB is an embedded database and not a client server database. It does not have a client plugin.
thanks
mike

Generate clients for multiple WSLDs using 'clientgen' task.

Issue -
I am trying to generate WS clients for multiple Services(WSDLs). I am using 'clientgen' task. But a 'clientgen'task accepts only one WSDL. If I have more one that one 'clientgen' task, some of the
common classes (generated) are overwritten.
For eg.
WSDL for Contract 1
<s:element name="executeResponse">
<s:complexType>
<s:sequence>
<s:element ref="soa:CancelOrderResponse"/>
</s:sequence>
</s:complexType>
</s:element>
<message name="executeSoapOut">
<part name="parameters" element="s0:executeResponse"/>
</message>
<portType name="CancelOrderSoap">
<operation name="execute">
<input message="s0:executeSoapIn"/>
<output message="s0:executeSoapOut"/>
</operation>
</portType>
<service name="CancelOrder">
<port name="CancelOrderSoap" binding="s0:CancelOrderSoap">
<soap:address location="http://localhost:7001/CoreWSProject/sync/CancelOrder.jws"/>
</port>
</service>
WSDL for Contract 2
<s:element name="executeResponse">
<s:complexType>
<s:sequence>
<s:element ref="soa:CancelOrderResponse"/>
</s:sequence>
</s:complexType>
</s:element>
<message name="executeSoapOut">
<part name="parameters" element="s0:executeResponse"/>
</message>
<portType name="CancelOrderSoap">
<operation name="execute">
<input message="s0:executeSoapIn"/>
<output message="s0:executeSoapOut"/>
</operation>
</portType>
<service name="CancelOrder">
<port name="CancelOrderSoap" binding="s0:CancelOrderSoap">
<soap:address location="http://localhost:7001/CoreWSProject/sync/CancelOrder.jws"/>
</port>
</service>
GENERATED CODE
A class ExecuteResponse will be generated for each service. This class gets overwritten if you use
multiple 'clientgen' tasks.
Question
Is there way to specify multiple WSDLs in 'clientgen' task so that i should be able to package
all the clientcode in one jar without any namespace issues ?
- Sandeep V

If the classes have the same namespace, by default, the same Java package name will be created. There is a packageName attribute on the clientgen Ant task, which provides some control over the Java package name that is used.
There is no way to specify multiple WSDLs to the clientgen Ant task. This makes sense if you subscribe to the notion that a WSDL represents a Web Service. It sounds like you can achieve what you want by:
1. Running clientgen on the first WSDL,
2. Use Ant to extract the contents of the generated JAR into a directory (with a name like clientgen),
3. Running clientgen on the next WSDL,
4. Use Ant to extract the contents of the generated JAR into the same clientgen directory,
5. etc, etc.
Afterwards, you would just need to use Ant to JAR up the clientgen directory. Again, you'll want to specify a different packageName attribute for each WSDL.
HTH,
Mike Wooten

1 server, multiple oracle_homes for each instance (dev, test, uat, etc)...

Hello,
We have one beefy server to hold our dev and test and maybe more non-production databases. My plan was to install separate oracle_homes for each so that I can patch and only affect one instance at a time. Is anybody else doing this? Does this sound right? Any gotchas that you have run into with this type of environment?
I read something about you should only have one active listener...
Same concept, but with the ASM instance. Can I also install multiple oracle_homes for each asm instance on the same box? Is anybody else doing this? Again any gotchas people have run into to? For ASM, should I also have only one active listener?
Am I right that the only thing that affects all instances is at the OS, hardware level such as Linux patches, anything to do with users, groups, shared folders, nics, etc?
Thank you for your input!

For ASM, should I also have only one active listener?ASM does NOT require any listener & none should exist for ASM.

XI, SLD & multiple clients for DEV & QA

Similar Messages

Maybe you are looking for