I-Docs to multiple clients

HI All,
Can any one tell me how to send i-docs to different clients. My requirement is, i am generating i-doc in 200 client. here i can give only one port, i have no option to give multiple clients. But i need to send it to clients 201, 202, 203. in this scenario how i can send the same I-doc to different clients, with out regenerating it.
Regares,
Suresh Patipati.

How are you generating the IDOC? Your distribution model maintains the receivers (logical systems) for a given message type. You can maintain as many receivers (clients) as you like in the model and distribute based on that. Each logical system has a port in the partner profile, but that's not related to runtime distribution, except when it's time to push that message to the receiver.

Similar Messages

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

TES 6.1.0.x Multiple Client Managers

Hello:
I am trying to find out if there is anyone else using multiple client managers on a load balancer and if we could have a discussion regarding such a setup. We have this in our envrionment and it does work, however sometimes I see oddities with in the client - even if I log directly into one of my client managers, by-passing the load balancer completely.
Looking forward to hearing from anyone with a similar setup.
Regards,
Ceceil Rufo

We haven't done a formal load testing yet. But we have conducted training with 10 - 15 users and would experience performance sometimes people just getting kicked out. At the time though we were still finagling with server configuration settings for threads, cache and java heap. During training too what seemed to impact performance more was the browser and version, and workstation memory. For a web app, TES 6.1 uses a LOT of memory so there were some suggested tweaks that had to be done on some machines. We have more consistent performance on IE 9 (than IE 10), and Firefox 18+ was faster.
I have installed Jconsole and am planning to conduct load testing sometime this month where i could monitor server resource from Jconsole to get an idea where bog down really is.
There is a TES 6.1 presentation doc that sort of outlines approx sizing based on concurrent users - we fit in the 10 -20 concurrent users given that our CM has 12GB RAM (allocated 10GB to TES) and 4 core. So hopefully with two CMs we can have upto 40. We are open to adding more mem if needed. So what tools do you use for Load testing? Also I wonder if it was possible to automate Load Testing like with Jmeter or something. For now we just plan on getting 20 users together to perform set functions at the same time and measure that with 1 CM up and me looking in Jconsole.
I also notice the multiple connections, even see myself twice even when I only have 1 browser session. Not having had a chance to dig to deeply i was chalking it up to maybe that I didn't exit properly last time so that it has to wait 30 minuts to totally clear me (with time to live setting) out but haven't really tested formally. I will see about adding that to my testing. I would also think it would impact system in that some folks may cause the number of concurrent connections allowed to be exceeded if you have too many of these lying around but since they are not doing anything perhaps not performance as much? It will be good to confirm though that a single web session really only takes 1 connection and won't potentially spawn another somehow.
Our implementation being highly distributed with workgroups having full autonomy over their jobs - means every team needs to have access to Transporter. We have over 15 teams. Which is scary since that also takes resources from the CM - and also from a management and training perspective. We also haven't load tested the Transporter server interms of number of concurrent users that can be running Transporter on it at one time. Nor have any clear idea yet how we'll manage the mapping files. But we are also opening up Transporter to be installed by teams on their team server (only that they have to patch themselves) - I really wonder if we should just restrict Transporter access to just the servers our team manage and no one else can install it anywhere else.

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.

Connecting to multiple clients

I have a question. i have one client and one server. the server connects a client and send some data which i am able to achieve it. my question is (is there a way to connect the same server to multiple clients?) secondly i want to make a check lets say that one client machine can accept only 30 data like (Dell $30.00). once the client recieve 30 data my client should say that i am full and then the client should write the data to another client machine ? is it possible?

If you feel like getting fancy, a scalable server could use NIO: http://java.sun.com/j2se/1.5.0/docs/guide/nio/index.html

Listening to multiple clients.

how do it make a server listen to multiple clients and process them.
so far i have reached just this
while(true)
socket=serversocket.accept();
but what after this.how to handle separate each client........

how do it make a server listen to multiple clients
and process them.
so far i have reached just this
while(true)
socket=serversocket.accept();
but what after this.how to handle separate each
client........For threading go through this
http://java.sun.com/docs/books/tutorial/essential/concurrency/
while(true)
socket=serversocket.accept();You have to start a new thread for each client and then do the needful.
Say you can implement two different threads to handle the messages to be sent and the messages to be received. Get the required inputstream and outputstream for the socket and use it in each thread.
like
BufferedReader in=new BufferedReader(new InputStreamReader(clientSocket.getInputStream()));
PrintWriter out=new PrintWriter(clientSocket.getOutputStream(),true);

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

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

Multiple clients on socket connection

Hi!
I understand that it is possible that multiple clients listen to one server (on the same port) and even write to it (then it should be a multi-threaded server).
But i would like to refuse connectios, if one client is connected. How can I do that?
In my case I have a (single threaded) server. Now one clients connects. The server waits to receive data from the client and answers, without ever closing the port. that works.
Now if I connect with a second client, the openicng of the socket in the second client works fine, although the server does not seem to notice the second client. Communication is not possible between the server and the second client, and the server doesn't answer to the first client anymore, although he receives data from it.
So, since the server does not seem to notice the second client (does not accept the connection) and I don't get an exception at the second client, what can I do?
Thank you for your help!
concerned Code (if you want to take a look at it):
CLIENT:
socket = new Socket(hostname, echo_port);
SERVER:
try
ServerSocket waitingsocket = new ServerSocket(echo_port);
try
     socket= waitingsocket.accept();
     System.out.println("Client connected");
     ReaderThread reader = new ReaderThread( this, socket );
     reader.start();
catch (Exception e)
READER:
public void run()
     while (true)
          try {
               int bytesRead = inStream.read(inputBuffer,
               0, inputBuffer.length);
               readCallback.tcpUpdate(inputBuffer,bytesRead);
          catch (Exception oops)
               readCallback.tcpUpdate(null,-1);


Just to make sure this is clear: You can NOT have multiple clients on a given socket connection. You CAN have multiple clients connected to a particular port on a given server, but each client will be communicating with the server through a different of socket.
The usual approach here is to set up a listening ServerSocket on the desired port, call accept() on it, then process the communication from the returned Socket object. This is usually done by spawning a new thread and allowing it to handle the socket communication, while the ServerSocket loops around to another accept() for the next communication.
Here's an excellent intro to the concepts (the code is really ugly and poorly implemented, but it does a good job of explaining the overall concept). I used this as a starting point, and now (after a whole lot of development) have a pretty sweet extensible web server class that handles template expansion, etc... (I use this as a quick and dirty UI for some of my apps, instead of requiring the user to install a JSP container):
http://developer.java.sun.com/developer/technicalArticles/Networking/Webserver/
- K

I-Docs to multiple clients

Similar Messages

Maybe you are looking for