The RPC adapter for IBM® WebSphere® Application Server Feature Pack for Web 2.0 and Mobile is provided as a standalone package. Let us assume that <install_root> is the directory where the feature pack is installed, which is the case for WebSphere Application Server, for example, and <WASCEFEP_HOME> is the directory where the WebSphere Application Server Community Edition feature pack is unzipped.
1) Standalone Library:
The IBM RPC adapter is provided as a stand-alone library in the <install_root>/web2mobilefep_1.1/optionalLibraries/RPCAdapter
directory in the case you installed the feature pack for WebSphere Application Server 6.1, 7.0, or 8.0.
In the case of WebSphere Application Server Community Edition the libraries can be located at
<WASCEFEP_HOME>/RPCAdapter/lib. You can add the RPCAdapter.jar file to the WEB-INF/lib directory of
your Web application and use it for exposing POJO methods as services. You will also need to add the
commons-logging-1.0.4.jar and the retroweaver-rt-2.0.jar files from that directory to the
WEB-INF/lib directory. Another file that you will need to add to the WEB-INF/lib directory of your Web
application is the JSON4J.jar file from <install_root>/web2mobilefep_1.1/optionalLibraries/JSON4J. Note that you also
need to create and add a RpcAdapterConfig.xml file in the WEB-INF directory.
The standalone library can be used with Web applications or Enterprise Applications that need to invoke methods of JavaTM objects from JavaScriptTM. Installation of this library is dependent on how the application that uses it is packaged and implemented. A few general scenarios are provided.
Java Platform, Enterprise Edition (Java EE) Web application:
This is for routing all calls to the application with RPC adapter in the URL to the com.ibm.websphere.rpcadapter.RPCAdapter servlet.RPCAdapter RPCAdapter com.ibm.websphere.rpcadapter.RPCAdapter RPCAdapter /RPCAdapter RPCAdapter /RPCAdapter/*
xml TestService com.ibm.test.TestService bean provides ...