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.

Similar Messages

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

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

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

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

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/]

Multiple Client Logon in JCO

Dear All,
We import an RFC as a Model and the names used for the connections are used to create JCO connections in the WEB AS.
However we have a need where we will know the SAP Client number only on the runtime. This means that the JCO connections can not be pre created in the WEB AS.
To solve this i tried the following solution:
I created 2 JCO connections for 2 different client Numbers in WEB AS. After importing the RFC i went to the class file where the connection name is mentioned. I applied a condition by coding to choose one of the JCO Connections which i created programatically. However when i rebuild the project this complete code is overwritten to the connection name specified in the wizard during the RFC model import.
Can anyone suggest answers for the following ?
- How can i manipulate the connection name of the JCO in code without being overwritten during rebuild ?
- Do you know of any other ways other of achieving my objective of connecting to multiple clients and deciding the connection name on the runtime?
Kind Regards,
Mukesh

Hi Mukesh,
   If you already have a JCo connection created based on the LDAP credentials, you can fetch the details like this:
try {
IWDJCOClientConnection clientCon = WDSystemLandscape.getJCOClientConnection("<name of the JCO connection>");
String clientName      = clientCon.getClientName();
String lang          = clientCon.getLanguage();
String passowrd          = clientCon.getPassword();
String sysID          = clientCon.getSystemIdentifier();
String user          = clientCon.getUser();
//etc...
} catch (WDSystemLandscapeException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
Is this what you are looking for?
Regards,
Satyajit.
Message was edited by: Satyajit Chakraborty

One Server Multiple Clients

Hello,
This server code accepts only one client connection at a time. However, I have several lines that are specifically for the server to accept more than one client. What do I need to do in addition for the server to recognize that it can accept more than one client at a time?
import java.io.EOFException;
import java.io.IOException;
import java.io.ObjectInputStream;
import java.io.ObjectOutputStream;
import java.net.ServerSocket;
import java.net.Socket;
import java.awt.BorderLayout;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import javax.swing.JFrame;
import javax.swing.JScrollPane;
import javax.swing.JTextArea;
import javax.swing.JTextField;
import javax.swing.SwingUtilities;
import java.util.concurrent.Executors;
import java.util.concurrent.ExecutorService;
import javax.swing.JFrame;
public class ServerTest
   public static void main( String args[] )
      Server application = new Server();
      application.setDefaultCloseOperation( JFrame.EXIT_ON_CLOSE );
      application.runServer();
class Server extends JFrame
   private JTextField enterField;
   private JTextArea displayArea;
   private ObjectOutputStream output;
   private ObjectInputStream input;
   private ServerSocket server;
   private Socket connection;
   private int counter = 1;
   private ExecutorService serverExecutor;
   private MultiServer clients[];
   public Server()
      super( "Server" );
      enterField = new JTextField();
      enterField.setEditable( false );
      enterField.addActionListener(
         new ActionListener()
            public void actionPerformed( ActionEvent event )
               sendData( event.getActionCommand() );
               enterField.setText( "" );
      add( enterField, BorderLayout.NORTH );
      displayArea = new JTextArea();
      add( new JScrollPane( displayArea ), BorderLayout.CENTER );
      setSize( 300, 150 );
      setVisible( true );
   public void runServer()
      serverExecutor = Executors.newCachedThreadPool();
      try
         server = new ServerSocket( 12345, 100 );
         while ( true )
            try
               waitForConnection();
               getStreams();
               processConnection();
            catch ( EOFException eofException )
               displayMessage( "\nServer terminated connection" );
            finally
               closeConnection();
               counter++;
      catch ( IOException ioException )
         ioException.printStackTrace();
   private void waitForConnection() throws IOException
      displayMessage( "Waiting for connection\n" );
      connection = server.accept();
      serverExecutor.execute( new MultiServer(server, connection));
      displayMessage( "Connection " + counter + " received from: " + connection.getInetAddress().getHostName() );
   private void getStreams() throws IOException
      output = new ObjectOutputStream( connection.getOutputStream() );
      output.flush();
      input = new ObjectInputStream( connection.getInputStream() );
      displayMessage( "\nGot I/O streams\n" );
   private void processConnection() throws IOException
      String message = "Connection successful";
      sendData( message );
      setTextFieldEditable( true );
      serverExecutor.execute(new MultiServer(server, connection));
      do
         try
            message = ( String ) input.readObject();
            displayMessage( "\n" + message );
         catch ( ClassNotFoundException classNotFoundException )
            displayMessage( "\nUnknown object type received" );
      } while ( !message.equals( "CLIENT>>> TERMINATE" ) );
   private void closeConnection()
      displayMessage( "\nTerminating connection\n" );
      setTextFieldEditable( false );
      try
         output.close();
         input.close();
         connection.close();
      catch ( IOException ioException )
         ioException.printStackTrace();
   private void sendData( String message )
      try
         output.writeObject( "SERVER>>> " + message );
         output.flush();
         displayMessage( "\nSERVER>>> " + message );
      catch ( IOException ioException )
         displayArea.append( "\nError writing object" );
   private void displayMessage( final String messageToDisplay )
      SwingUtilities.invokeLater(
         new Runnable()
            public void run()
               displayArea.append( messageToDisplay );
   private void setTextFieldEditable( final boolean editable )
      SwingUtilities.invokeLater(
         new Runnable()
            public void run()
               enterField.setEditable( editable );
class MultiServer extends Thread
public MultiServer(ServerSocket servers, Socket connection)
      servers = server;
public void run(){System.out.print("Yes");}
}

Check out the "Supporting Multiple Clients" bit here: http://java.sun.com/docs/books/tutorial/networking/sockets/clientServer.html
Start a Thread for each client. I'd recommend you create a class:
class Client
    Socket socket;
    ObjectOutputStream out;
    ObjectInputStream in;
    ...any other client-specific data you need...
    public void sendMessage(String s) { ...send to this client...; }
   ...any other client-specific methods you need...;
}Create one of those when accept() gets a new connection, then start the thread for that client.
You may want to keep a LinkedList that contains all the Client objects. E.g. if you want to send a message to all clients you'd loop over the LinkedList and send to each in turn. Synchronize the list appropriately. Removing clients from the list when they close down can be interesting :-) so be careful.

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.

Send data to multiple clients from a server

My problem statement is this:
A server is created, say X. Multiple clients are created, say A, B & C. If X sends a message to A it should reach only A and should not go to B or C. Similarly if X sends message to B it should not reach A or C. I made a one to one communication with the following code:
//Server
import java.io.*;
import java.net.*;
class X
public static void main(String args[])throws Exception
ServerSocket ss=new ServerSocket(4321);
try
Socket s=ss.accept();
BufferedReader in = new BufferedReader(new InputStreamReader(System.in));
DataOutputStream out = new DataOutputStream(s.getOutputStream());
String str=in.readLine();
out.writeBytes(str+"\n");
s.close();
ss.close();
catch (IOException e){}
//Client A
import java.io.*;
import java.net.*;
class A
public static void main(String args[])throws Exception
try
Socket s=new Socket("localhost",4321);
BufferedReader in=new BufferedReader(new InputStreamReader(s.getInputStream()));
System.out.println(in.readLine());
s.close();
catch(Exception e){}
}But i dont know how to keep track of each client. Because all the clients sockets are created at the same port, ie. 4321. I think thread will help. But even then i dont know how to identify each client. Somebody please help. Thanks in advance.
Edited by: sowndar on Dec 5, 2009 1:21 AM

YoungWinston wrote:
sowndar wrote:
Ok. I think i have to attach an unique ID to each client message. So that, with the help of that ID, the server can identify each client. Have i caught ur point?If you don't mind using a port per client, you could do something like a receptionist taking incoming calls (on 4321 only).
- Hi I'm Client xyz.
- Hi Client xyz, please call me back on port abcd and I'll put you straight through to our server.
Since 4321 is an "open line" you might have to have some sort of ID so that Clients know which return messages are meant for them, but messages on the other ports would all be direct Client to Server. Also, the Server is then is charge of port allocation and communication on the "open" port is kept to a minimum.4321 is the socket that the server is listening to. It's not what the actual communication will be carried out over. Run this, then telnet to port 12345 a few times
public class TestServerSocket {
public static void main(String[] args) throws Exception {
          ServerSocket server = new ServerSocket(12345);
          while (true) {
               Socket socket = server.accept();
               System.err.println(socket.getPort());
}Notice how each inbound connection is allocated a unique outbound socket.

Networking: problems servering multiple clients

hi all
i'm writing a simple client server system, with a multithread server, in order to serve multiple clients.
the client's requests to connect to the server arrive to a port (ie 1025), and then the server, through a method returns to the client another port number, and then the comunication between them starts through the new port.
all work very fine, but i tried, with 2 computers, to start two clients at the "same time" (with a gap of few milliseconds), and my system "crashes".
i think that is a problem due to the second request that arrives while the comunication of the port from the server to the client happens.
is there a way to "queue" the requests arriving to the 1025 port of my server?
if i wasn't clear i can post some code
thanx in advance
sandro

Yes, teh code I posted does nothing more then listen for incoming conections and create a new Thread wich gets the Socket created by the accept to play with. This will happen for any incoming connection on the right port and will always be handeled the same.
As you'll see in the code i posted, there is some time between ServerSocket.accept returning a Socket and ServerSocket.accept being started again. This time shouldn't be to long to be sure the serversocket is listening for incoming connections when they arrive, so don't do to much inside the loop. If your system should handle a lot of connections simultaneously wou might have to optimise this be doing thing like having a few ClientThreads created allready to save the time of creating a new Thread. This becomes more important if you ClientThread is complex and slow to create. But when handelin less the say 25 clients you should be fine with this.

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);
}

Making a chat server that supports multiple clients!

This is what I got so far:
import java.net.*;
import java.io.*;
public class Server{
     public static void main(String [] args){
          ServerSystem ssys = new ServerSystem();
          ssys.ServerMethod();
class ServerSystem{
     static ServerSocket ss;
     public void ServerMethod(){
          try{
               ss = new ServerSocket(27700);
               boolean listening = true;
               for(;listening;){
                    ClientThread ct = new ClientThread(ss.accept());
                    ct.start();
                    ss.close();
          }catch(Exception e){
               System.exit(0);
class ClientThread extends Thread{
     ServerSystem ssys = new ServerSystem();
     ServerSocket ss = ssys.ss;
     public void run(){
          try{
               BufferedReader in = new BufferedReader(new InputStreamReader(ss.getInputStream()));
               PrintWriter out = new PrintWriter(ss.getOutputStream(),true);
          }catch(Exception e){
               System.out.println(e);
}3 Errors:
ClientThread ct = new ClientThread(ss.accept()); CONSTRUCTOR : CANNOT RESOLVE SYMBOL
BufferedReader in = new BufferedReader(new InputStreamReader(ss.getInputStream())); METHOD : CANNOT RESOLVE SYMBOL InputStream
               PrintWriter out = new PrintWriter(ss.getOutputStream(),true); METHOD : CANNOT RESOLVE SYMBOL OutputStream
First of all, how do I fix those. Second, am I on the right track for a server that supports multiple clients? Please help me with this.
Thanks!

well, since I feel kinda bad for just re-posting the link to the API docs previously posted by supermicus I shall elaborate - though, since my reading for comprehension skills are clearly lacking, I will not attempt to teach you to read.
This conversation should be held in the "New to Java Technology" forum, BTW.
Java derives a lot of its power from the huge library of classes that ships with it, which is called the API. These classes are grouped into packages roughly along functional lines, so you should expect to see some relationship between the classes found in a given package - the java.net.* classes all pertain to networking. The API documentation describes three things about each class - fields that are available, constructors that you can use, and methods that you can call. Basically, anything at all that you can do with a given class (ThreadGroup, for instance) can be found in the documentation for that class. Typically (for non-static classes), you call the constructor that seems most appropriate via the "new" keyword, and, using the reference returned from that, you call the method that does what you want. It's all outlined in the docs.
If you don't get what you need from the docs, then read the appropriate Tutorial (also in the list of links to the left of your screen) find the one on Threads and off you go.
I hope this helped.
Lee

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
          >>
          >
          >

Importing to Multiple clients in SCM

Similar Messages

Maybe you are looking for