Originally posted by: SystemAdmin
The RMI Server is part of the 6.7.1 SDK.
If you would rather not introduce that, your choices are to install TX on the same machine as the app server and execute maps in process using the Java API, or you would need to use messaging (JMS, MQ, etc.) to get the data to the machine where TX lives.
I suggest you avoid the EJB API. It's being deprecated in Trinity. You can call maps just fine from an EJB using the Java API.
In my opinion, the RMI Server is much the better way to go. You can serve mutliple app server nodes with a single instance of the RMI Server, which has implications for you in terms of TX licensing costs.
#DataExchange#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender