JClient accessing remote AppModule via EJB Session Fascade (BMT)?

Question

Would appreciate some "how-to" advice on bootstrapping a remote JClient like the one in the VSM example,
such that: the JClient remotely accesses OC4J-pooled AppModule instances,
rather than creating a new AppModule instance on the client side.
In the OTN VSM-JClient example code, the Bootstrap is done in
AdministrativeServiceForm::main() as follows:
JUApplication app =
JUMetaObjectManager.createApplicationObject(
"VSMJClient.AdministrativeService",
null,
new JUEnvInfoProvider() );
String appModule =
System.getProperty("jclient.service",
"VSMJClient.AdministrativeService" );
The problem with this is -
JUMetaObjectManager.createApplicationObject() is undocumented, hence may or may not facilitate remote
App-Module access?
If anyone can share a working example of JClient remote AppModule access over ORMI (talking to modules deployed on JBuilder-embedded-OC4J), or can modify the VSM-JClient to do the same - it would be greatly appreciated!
Many thanks,
Lee.

Answer 1

JUMetaObjectManager.createApplicationObject("VSMJClient.AdministrativeService",null,new JUEnvInfoProvider());
looks for the Session AdministrativeService in VSMJClient.cpx:
<Session
Name="AdministrativeService"
Package="oracle.otnsamples.vsm.services"
Configuration="AdministrativeServiceLocal" >
</Session>
<Session
Name="RemoteAdministrativeService"
Package="oracle.otnsamples.vsm.services"
Configuration="AdministrativeService9iAS" >
</Session>
Just call
JUMetaObjectManager.createApplicationObject("VSMJClient.RemoteAdministrativeService",null,new JUEnvInfoProvider() );
to access the deployed Beans with configuration AdministrativeService9iAS.