Multiple Clients in SCM 7.0

Dear All,
    Can we have multiple clients in SCM 7.0?
What is pro's and con's of having multiple clients???
Thanks,
Siva.

Hi Siva,
For non BI-based applications such as PP/DS you can use multi-client landscape in the same manner as in ERP system.
For DP, SNP etc. see sapnote 522569 (it's relevant for 7.0 as well)
Regards,
Alexander

Similar Messages

  • Multiple Clients in SCM-APO?

    In a Development SCM-APO 5.0 environment, can we have multiple clients?  For instance, can we have a unit test client(with master and transactional data), a security client, and a golden configuration client.
    We have heard that there may be issues with having more than one client, but we are not sure if this is correct.  Our SCM-APO unit test client would be the only one that is connected to a BW (3.5) Development client and a R/3 (4.7) Development client.  The security and golden config client would not be connected to external systems.  Is this landscape possible and supported by SAP?

    I do not have a good answer but it seems APO-DP uses BW as Data Mart which results in some restriction in using multiple client. See SAP Note 522569 for details. Moreover in the Multi-client Whitepaper (attached to SAP Note 31557) the table in page 23 mentions Multi-client Status for APO with DP : Not OK and APO w/o DP : Restricted OK.
    Hope this is of some help.
    somnath

  • Importing to Multiple clients in SCM

    Hi,
    We are using SCM,while importing a transport request,can we import it to multiple clients?We have 5 quality clients and i want to import to all the clients.
    Thanks in advance

    Dear all,
    We can import to multiple clients by defining the clients in the system landscape of the maintenance project.
    Thanks and Regards,
    Avinash.

  • Multiple Clients in SCM/APO 51.

    Hello,
    1.Is it possible to create Golden master client & Testing client in a single SAP SCM/APO5.1 instance and work simultaneously with the BI and APO commands (e.g. RSA1) in both the clients?
    2.Can we have two live cache servers on a single physical hardware?
    3.Can a single live cache server can be connected to two different SAP instance DEV and QAS?
    Regards
    Riya
    SAP basis Consultant

    I do not have a good answer but it seems APO-DP uses BW as Data Mart which results in some restriction in using multiple client. See SAP Note 522569 for details. Moreover in the Multi-client Whitepaper (attached to SAP Note 31557) the table in page 23 mentions Multi-client Status for APO with DP : Not OK and APO w/o DP : Restricted OK.
    Hope this is of some help.
    somnath

  • SCM and CRM Multiple Clients in one system

    Dear all,
    I want to ask a question regarding Multiple clients in SCM 5 - IDES and CRM 5 -IDES.
    I installed the system and plan to have multiple clients in a system with copying client 800 (IDES) to others.
    I heard opinion that it can't possibly be done because if during the exercise the Administrator Workbench is executed it will search to the source client (800) and probably affect the exercise.
    Would you mind giving me more suggestion about this?
    Thank you.
    Fausto

    Hi Fausto,
    Could you be more specific about what you need to achive?
    You can always creat a new client, logon to the client and do a client copy with TCod SCCL.
    If you logon to other IDES clients then You'ld overwrite the content of the client which have been pre-configured.
    Check the status of the client you need to overwrite from TCod scc4.
    Also to verfiy the status of the target client for TCod se06 -system change option.
    Regards,
    Tolulope

  • 640 SID With BW Layer - Multiple Clients?

    My company installed SRM (SRM_SERVER 500 SP #7) with the BW layer (BW 350 SP # 14) does it make sense to have a multiple client strategy in the non-productive SRM SIDs?  Does anyone have any SAP white papers on client strategy on the new dimension products (BW, CRM, SCM/APO, EP, etc.)?  Since I am not a BW developer I am uncertain as to why in BW it only makes sense to have 1 client which I would guess if a new dimension SID has the BW layer active then it would make sense to only have 1 client as well?  Any information would be most appreciated.

    Hi Ken,
    SAP NetWeaver BI cannot use multiple client because the objects it creates and uses are client independent. In fact only SAP NetWeaver AS ABAP (usage type AS ABAP) based system offer the potential of a multi- client solution. AS JAVA based applications do hot have a client concept, they tend to have multiple instances (i.e. one per client).
    I'm having a little difficulty understanding one part of your question ".. would guess if a new dimension SID has the BW layer active then it would make sense to only have 1 client as well?...". Can you elaborate on the question?
    Are you asking, if the SAP NetWeaver capability one has one client, does it make sense to have only one client in the ABAP based application too?
    Cheers,
    Mike.

  • Multiple clients in SAP BI possible to create?

    Hi,
    I already have a SAP BI system on client 150. Is it possible to create a different client for the same system? In R/3 we do the developement and import it through SCC1. If I want similar scenario in BI then is it possible?
    Regards.
    Shailesh Naik

    Technically, you can have multiple clients. SAP does support it. It has its own limitations though. Refer the below note:
    Note 522569 - BW: Working in several clients (especially APO 4.x/SCM 4.x)
    But advise is not to do it unless its a testing environment.
    Regards,
    Jazz

  • Accessing the same stateful session bean from multiple clients in a clustered environment

    I am trying to access the same stateful session bean from multiple
              clients. I also want this bean to have failover support so we want to
              deploy it in a cluster. The following description is how we have tried
              to solve this problem, but it does not seem to be working. Any
              insight would be greatly appreciated!
              I have set up a cluster of three servers. I deployed a stateful
              session bean with in memory replication across the cluster. A client
              obtains a reference to an instance of one of these beans to handle a
              request. Subsequent requests will have to use the same bean and could
              come from various clients. So after using the bean the first client
              stores the handle to the bean (actually the replica aware stub) to be
              used by other clients to be able to obtain the bean. When another
              client retrieves the handle gets the replica aware stub and makes a
              call to the bean the request seems to unpredictably go to any of the
              three servers rather than the primary server hosting that bean. If the
              call goes to the primary server everything seems to work fine the
              session data is available and it gets backed up on the secondary
              server. If it happens to go to the secondary server a bean that has
              the correct session data services the request but gives the error
              <Failed to update the secondary copy of a stateful session bean from
              home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
              to the primary server will not reflect changes made on the secondary
              and vice versa. If the request happens to go to the third server that
              is not hosting an instance of that bean then the client receives an
              error that the bean was not available. From my understanding I thought
              the replica aware stub would know which server is the primary host for
              that bean and send the request there.
              Thanks in advance,
              Justin
              

              If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
              do you?
              Except of course if you switch ejb containers. Oh well.
              Mike
              "FBenvadi" <[email protected]> wrote:
              >I've got the same problem.
              >I understand from you that concurrent access to a stateful session bean
              >is
              >not allowed but there is a
              >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
              >that
              >does exactly what I need.
              >What you mean 'you'll get a surprise when you go to production' ?
              >I need to understand becouse I can still change the design.
              >Thanks Francesco
              >[email protected]
              >
              >"Mike Reiche" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> Get the fix immediately from BEA and test it. It would be a shame to
              >wait
              >until
              >> December only to get a fix - that doesn't work.
              >>
              >> As for stateful session bean use - just remember that concurrent access
              >to
              >a stateful
              >> session bean is not allowed. Things will work fine until you go to
              >production
              >> and encounter some real load - then you will get a surprise.
              >>
              >> Mike
              >>
              >> [email protected] (Justin Meyer) wrote:
              >> >I just heard back from WebLogic Tech Support and they have confirmed
              >> >that this is a bug. Here is their reply:
              >> >
              >> >There is some problem in failover of stateful session beans when its
              >> >run from a java client.However, it is fixed now.
              >> >
              >> >The fix will be in SP2 which will be out by december.
              >> >
              >> >
              >> >Mike,
              >> >Thanks for your reply. I do infact believe we are correctly using
              >a
              >> >stateful session bean however it may have been misleading from my
              >> >description of the problem. We are not accessing the bean
              >> >concurrently from 2 different clients. The second client will only
              >> >come into play if the first client fails. In this case we want to
              >be
              >> >able to reacquire the handle to our stateful session bean and call
              >it
              >> >from the secondary client.
              >> >
              >> >
              >> >Justin
              >> >
              >> >"Mike Reiche" <[email protected]> wrote in message
              >news:<[email protected]>...
              >> >> You should be using an entity bean, not a stateful session bean
              >for
              >> >this application.
              >> >>
              >> >> A stateful session bean is intended to be keep state (stateful)
              >for
              >> >the duration
              >> >> of a client's session (session).
              >> >>
              >> >> It is not meant to be shared by different clients - in fact, if
              >you
              >> >attempt to
              >> >> access the same stateful session bean concurrently - it will throw
              >> >an exception.
              >> >>
              >> >> We did your little trick (storing/retrieving handle) with a stateful
              >> >session bean
              >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
              >sfsb's
              >> >were not
              >> >> replicated as yours are.
              >> >>
              >> >> Mike
              >> >>
              >> >> [email protected] (Justin Meyer) wrote:
              >> >> >I am trying to access the same stateful session bean from multiple
              >> >> >clients. I also want this bean to have failover support so we want
              >> >to
              >> >> >deploy it in a cluster. The following description is how we have
              >tried
              >> >> >to solve this problem, but it does not seem to be working. Any
              >> >> >insight would be greatly appreciated!
              >> >> >
              >> >> >I have set up a cluster of three servers. I deployed a stateful
              >> >> >session bean with in memory replication across the cluster. A client
              >> >> >obtains a reference to an instance of one of these beans to handle
              >> >a
              >> >> >request. Subsequent requests will have to use the same bean and
              >could
              >> >> >come from various clients. So after using the bean the first client
              >> >> >stores the handle to the bean (actually the replica aware stub)
              >to
              >> >be
              >> >> >used by other clients to be able to obtain the bean. When another
              >> >> >client retrieves the handle gets the replica aware stub and makes
              >> >a
              >> >> >call to the bean the request seems to unpredictably go to any of
              >the
              >> >> >three servers rather than the primary server hosting that bean.
              >If
              >> >the
              >> >> >call goes to the primary server everything seems to work fine the
              >> >> >session data is available and it gets backed up on the secondary
              >> >> >server. If it happens to go to the secondary server a bean that
              >has
              >> >> >the correct session data services the request but gives the error
              >> >> ><Failed to update the secondary copy of a stateful session bean
              >from
              >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
              >> >> >to the primary server will not reflect changes made on the secondary
              >> >> >and vice versa. If the request happens to go to the third server
              >that
              >> >> >is not hosting an instance of that bean then the client receives
              >an
              >> >> >error that the bean was not available. From my understanding I
              >thought
              >> >> >the replica aware stub would know which server is the primary host
              >> >for
              >> >> >that bean and send the request there.
              >> >> >
              >> >> >Thanks in advance,
              >> >> >Justin
              >>
              >
              >
              

  • We have created shared folder on multiple client machine in domain environment on different 2 OS like-XP,Vista, etc. from some day's When we facing problem when we are access from host name that shared folder is accessible but same time same computer when

    Hello All,
    we have created shared folder on multiple client machine in domain environment on different 2 OS like-XP,Vista, etc.
    from some day's When we facing problem when we are access from host name that shared folder is accessible but same time same computer when we are trying to access the share folder with IP it asking for credentials i have type again and again
    correct credential but unable to access that. If i re-share the folder then we are access it but when we are restarted the system then same problem is occurring.
    I have checked IP,DNS,Gateway and more each & everything is well.
    Pls suggest us.
    Pankaj Kumar

    Hi,
    According to your description, my understanding is that the same shared folder can be accessed by name, but can’t be accessed be IP address and asks for credentials.
    Please try to enable the option below on the device which has shared folder:
    Besides, check the Advanced Shring settings of shared folder and confrim that if there is any limitation settings.
    Best Regards,
    Eve Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • WDS 2012 R2 - Cannot PXE multiple clients at the same time

    Hello All,
    This is my first post on here so I apologize if this is the wrong place.  I work for a school district and we are implementing WDS 2012 R2.  We've been extremely satisfied with the speeds and ease of use through unattend files.  However, for
    the past month I've been looking for a possible answer to a problem that has plagued us from day one of implementation.
    So here's the problem:
    I have a stand alone WDS server which is not a domain controller and is not our DHCP server.  I have IP helpers and broadcast forwarders setup on the network.  As well as option 66 and 67 in DHCP.  So far so good right!
    Well that's partially right.  When we boot one client at a time to the WDS server.  Everything works as intended.  We can TFTP the necessary files from the WDS server.  Everything boots up and we're off and running.
    However, if we boot up two or more clients at the same time.  The WDS server never responds to the traffic.  The clients get their DHCP information.  They start the referral and download from the WDS server, but get no response.  I'm
    really hoping that someone on here would have some insight of something I can try.  I've about exhausted my list of peers and contacts.  They're all stumped as well and were smart enough to stay with 2008 WDS.
    I would prefer to stick with 2012 R2 since it's setup and working for the most part.  With only this one hiccup.
    Thanks in advance for any guidance!

    Hello Daniel,
    I appreciate the reply and apologize for taking so long to get back to this.   Things have been a little hectic over here.
    I have tried everything on this forum and I am still unsuccessful in PXE booting multiple clients at the same time.
    Multicast is enabled on the server, and it works for the clients.  However, as stated in the original post.  I cannot boot multiple machines at the same time.  I can start them from the image selection screen around the same time though.  So,
    that appears to be working fine.

  • How to use multiple clients within JCO?

    Hi,
    I'm pretty new to configuring Web Dynpro's with it's JCO connections. I have the following question.
    We are using one portal (SAP EP 6.0_640 SP15) and one R/3 system (SAP ECC 5.0) with multiple clients (multiple customers who are all using the same portal).
    Do I have to deploy a web dynpro for each client and maintain it's JCO connection for each client?
    Or is there another way how I can set this up?
    Thanks in advance.
    Kind regards,
    Dave Arends

    Hi Dave,
    <b><i>Do I have to deploy a web dynpro for each client and maintain it's JCO connection for each client?
    Or is there another way how I can set this up?</i></b>
    You dont need to deploy a web dynpro for each client . You can use same JCO connection for multiple User ID's  ( multiple Clients mean multiple user ID's on the same portal ).
    If this is the case then single JCo connection is enough to pull data from R/3 and show on portal page .
    Thanks,
    Nanda

  • How to control one server with multiple clients via TCP/IP

    I am wanting to control a single server with multiple clients.  Only one client would be active at a time, so there would be no conflict.  I want to use TCP/IP.  So far, I have programmed a cluster that passes data back to the server with no problems.  The challenge come in when a second client is added to the mix.  I have't been able to figure out how to turn each client on and send the appropriate data and then turn it off so it doesn't keep sending the same data to the server. 
    Here are the things that I have considered and did some preliminary testing, but don't really know how to impliment:
    1.  Send a numeric on the front of the cluster packet that tells the server that data is on the way.
    2.  Send a boolean on the front of the cluster packet to somehow turn the server TCP/IP on.
    The problem I have found is that LabVIEW TCP/IP doesn't like to be turned on and off.  If it doesn't get the data it expects, it goes into a reset mode and that kills the response time.
    Any help?

    You should consider implementing a set of simple one-byte commands that can be sent back and forth between the Server and the Clients. You can base all of these ideas off the example in the Example Finder under Networking >> TCP and UDP called Multiple Connections - Server.
    You will have two loops in the server VI: one to wait for new connections, and one to send and receive data from the existing connections. For instance, after one of the clients connects, it can request control of the server to send data to it by sending the character "R" for request. Every time the send/receive loop of the Server executes, the first thing it can do is to check all the existing connections to see if any of the clients have sent a control request ("R"). If so, it will create a buffer (array) of control requests. This could be in the form of Connection IDs or indexes in the array for a particular Connection ID. Your choice.
    After the Server receives a request for contol, if it is not already under control by another client, then it can send a response to the first client on the control request list. For instance, the server could send the first client a "S" command for send. Note that after the clients send their control request, they should execute a TCP Read and wait indefinitely for the server to respond with the one-byte "S" command. Then, once the client in control is finished sending data to the server, it could send the character "X" telling the Server to release it from control.
    The example I mentioned above already does a similar thing. Note how when a client wants to disconnect, they send the letter "Q". You can see this in the Multiple Connections - Client VI. The Server then checks each individual connection to see if it's received this one-byte command, and if it has, it closes the connection to the client. This is what you would want to implement, but instead of having just one command, you'll have to distinguish between a few and build up a buffer of control requests.
    Finally, if a client does decide to disconnect in your application, they could send the command "Q" just like the example above. At this point, close the connection and remove that Connection ID from the array of connections. You will also have to handle the case that this client was in the request control waiting line when it disconnected, in which case you need to delete it from that array as well.
    This will definitely work for you, but it will take some work. Best of luck!
    Jarrod S.
    National Instruments

  • 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

  • Is it possbile to have multiple clients on our Production instance

    We have our Production system with client 101
    Our abapers want me to create another client 500 (config only - not easy to accomplish)  to be used for our Mexican users.
    I told them to create another company code for Mexico, but they do not know how to do this.
    DO I have any other options, of yes
    Pros and cons of having multiple clients in same production instance.
    I know that any independent code is going to effect all clients.
    THanks
    Joe

    Hi Jo,
    you CAN create a new client, but mostly this is not done, because the effort to maintain multiple clients is mostly higher than just different company codes. Yes, ABAPs are client indpendent and therefore valid for all clients.
    So, the argument, to "not know" how to create different company codes is not valid to me !
    Regards
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

  • Saving string  from multiple clients on a server data structue

    I have a server which receives updates from multiple clients ( in this example, football scores which are updated periodically by the clients.)
    When the server receives the scores it needs to store them and at certain time intervals send the complete list of scores to multiple terminals at various locations.
    I am approaching this task in stages...
    stage 1.
    ..create the clients and server ...test the clients can send the data and the server can receive the data and output to screen..
    this is completed
    stage 2...
    a/ on the server side store the received scores in a data structure (ArrayList<String> is what I'm thinking.)
    b/ periodically output all scores to the screen (maybe every 30 seconds) and empty the ArrayList..am looking at the Timer class for this part..
    stage 3
    create the monitors and output scores to monitors periodically..
    ======================================================
    right now I'm at stage 2a ie trying to store the received scores in a data structure.
    i've created a method saveScore in the StoreScore class which is called by the StoreScore run method...
    The saveScore method creates an ArrayList and adds the score to it...
    Question
    does every thread create a new instance of storedScores and therefore the scores are stored in a multitude of data structures?
    I think the answer is yes and if so then this is not the solution...
    What I'm thinking is , as all scores can be outputted to the server screen via System.out.println, is there not a way of saving all these scores in a single data structure?
    The code below is the server code..
    any advice much appreciated....thank you
    /*=============================================================== */
    import java.io.*;
    import java.net.*;
    import java.util.*;
    import java.util.concurrent.*;
    class ScoresServer1{
    final static int portNum = 1234; // any number > 1024
    final static int numThreads = 10;
    static ExecutorService pool;
    public static void main(String[] args){
    pool = Executors.newFixedThreadPool(numThreads);
    System.out.println("Server running ...");
    try{  
    ServerSocket servesock = new ServerSocket(portNum);
    // for service requests on port
    while (true){ 
    // wait for a service request on port portNum
    Socket socket = servesock.accept();
    // submit request to pool
    pool.submit(new StoreScore(socket));
    }catch(IOException e){}
    class StoreScore implements Runnable {
    BufferedReader reader;
    Socket sock;
    public StoreScore(Socket clientSOcket) {
    try {
    sock = clientSOcket;
    InputStreamReader isReader = new InputStreamReader(sock.getInputStream());
    reader = new BufferedReader(isReader);
    } catch (Exception ex) { ex.printStackTrace(); }
    public void run() {
    String message;
    try {
    while ((message = reader.readLine()) != null) {
    // System.out.println("latest score: " + message);
    saveScore(message);
    } catch (Exception ex) { ex.printStackTrace(); }
    public void saveScore(String message){
         ArrayList<String> storedScores = new ArrayList<String>();
         storedScores.add(message);
         Iterator<String> t = storedScores.iterator();
              while(t.hasNext()){
                   String s = t.next();
                   System.out.println(s);
    }

    does every thread create a new instance of storedScores and therefore the scores are stored in a multitude of data structures?
    I think the answer is yes and if so then this is not the solution...The answer is yes. However, threads can share data, if they were properly synchronized. You should read the threading tutorial before creating a lot of hard to debug mistakes.
    [http://java.sun.com/docs/books/tutorial/essential/concurrency/]

Maybe you are looking for