The
following process describes what happens when a Java(TM) client uses the C/S Messaging API to
communicate with the server. The process assumes that the Java client
is using a navigation controller for the view navigation and that Single Action
EJBs handle the business logic in the application logic layer.
- The user requests some action in the client user interface.
- The client initializes the client operation and its context. The client
chains the context to the appropriate context in the context hierarchy.
- The client operation uses a CSClient instance to send the request
to the server and to indicate the csReplyFormat that will returned by server
used to unformat the response data from server. The client operation definition
identifies the server operation . The CSClient creates the request and accesses
the operation context to populates the request with the required data.
- On the server, the Client/Server Mechanism handles the incoming request.
- In server side, JavaRequestHandler will take the request.
- The JavaRequestHandler calls the invoker responsible for handling
the server operation as a business process. The JavaRequestHandler passes
the data send by the client and session ID into Invoker Pattern.
- The invoker will unformat the formatted data and convert it
as parameters, then creates a process request message and sends it to the
application logic layer. Once the JavaRequestHandler has called the invoker,
the JavaRequestHandler waits until it receives a response from the application
logic layer.
- The application logic layer returns a response message. The invoker formats
the data and returns the formatted data to the presentation handler.
- The presentation handler renders the data so that the Java client
can display it properly.
- The multichannel architecture sends the rendered data to the client. The
multichannel architecture formats the data into the context hierarchy on the
client side using the csReplyFormat.
- The client displays the result data in a view.