Problem: My application modules are currently executing on the same
node (on one SBC) and communicating using message queues. In order to
deploy them on different nodes (different processors/different
OS/different SBC's) we wanted to make a communication adaptor which
will make interaction between processes location independent. i.e., if
both processes are running on the same node, then they will
communicate using message queues and if during compilation and code
generation (in rhapsody) i decide to make them run on different nodes,
then i will change the deployment diagram of the components and make 2
separate binaries (exe's) and they will communicate thro TC/IP. The
adaptor component was to be some inbetween (wrapper) class, which will
be used if there needs to be TC/IP comm.
Interestingly, rhapsody does not have direct provision for socket
communication (except for communication between instrumented code and
rhapsody itself..)
Request:
So we were wondering if anybody has typecasted any interface or port
and have made code generation transformation rules, so that, if i use
that port between 2 blocks or components, the code that is generated
by rhapsody is a TCP/IP socket connection between the blocks.
if such a thing does not exist, then we have to continue using the
same procedure of handcoding the socket connection using traditional
C/C++ method code as a function or class and call it , which
effectively, does not bring the power of UML modeling of ports and
interfaces to RPC or broadcast/multicast requirements.
Therefore, can u, pse...
(a) Find out if any such kind of stereotyping / model transformation
exists for socket communication in Rhapsody?
(b) Any material available for integrating socket communication with
other IPC's for this requirement?
Pse DO NOT refer me this reference :
http://www-01.ibm.com/support/docview.w ... wg21398197(c) Any other suggestion of how to go about implementing such a feature
