Collaboration

Components under this category enable you to collaborate across different platforms by communicating through conversations.

chat

chat component is a Java-based component that demonstrates sending messages from one chat window to another through input and output ports. The font and color of the messages can be configured in the Configuration Property Sheet (CPS) of the component.

This component can also be used with other components like SMTP and DB. To use it along with those components, provide the Name and Email ID in the User Information panel in CPS, and map the route (Route Transformation) accordingly.

Figure 1: User information to couple with components other than the chat component

This component cannot be launched in-memory of the peer server.

c#Chat

csChat is a native Csharp-based component. CS Chat uses the .Net framework for its GUI (chat window). The CS Chat component uses the Csharp runtime which is a wrapper on C++ native runtime for running the application.

• To run csChat component, make sure DOT NET 2003 or above is installed on the machine where peer server is running.
• This component is not configurable and hence does not open the Configuration Property Sheet (CPS).
• This component cannot be launched in-memory of the peer server.

vbchat

Vbchat is built upon JNI-based CPP client library which uses fmq-cpp-client-msg-adapter.lib for running the component. Vbchat uses Microsoft ActiveX controls for its GUI (chat window).

• To run vbChat component, make sure DOT NET 2003 or above is installed on the machine where peer server is running.
• This component is not configurable and hence does not open the Configuration Property Sheet (CPS).
• This component cannot be launched in-memory of the peer server.
  

vcChat

vcChat is a native C++ based component. VC Chat uses the MFC library for its GUI (chat window). VC Chat uses the c++ native runtime library for running the application.

• To run vcChat component, make sure Microsoft Visual Studio 6.0 or above is installed on the machine where peer server is running.
• This component is not configurable and hence does not open the Configuration Property Sheet (CPS).
• This component cannot be launched in-memory of the peer server.