Express (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository > Virtual member manager
Install virtual member manager
Virtual member manager is installed as a WebSphere system application during the installation of WAS. See the WAS documentation for installation instructions.
About this task
We can optionally deploy the virtual member manager service EJB and the compatibility EJB onto a target. Run the following wsadmin commands to deploy the EJB.
In a network deployment environment, the EJB on the managed server node must be first looked up with the absolute path of the context (for example, cell/nodes/IBM-19D40CACAF4Node01/servers/server1/ejbna where ejbna is the JNDI name of the virtual member manager EJB on the managed server, server1).
To deploy onto the Deployment Manager target (dmgr):
$AdminApp install WAS_HOME/systemApps/wim.ear {-appname wim -server dmgr -systemApp}To deploy onto a server target (for example, server1 on node1):
$AdminApp install WAS_HOME/systemApps/wim.ear {-appname wim -node node1 -server server1 -systemApp}To deploy onto a cluster target for example, cluster1:
$AdminApp install WAS_HOME/systemApps/wim.ear {-appname wim -cluster cluster1 -systemApp}In a multiple security domain environment, deploy virtual member manager EJB on each target server, where the server scope is associated with that security domain, to get a reference to the virtual member manager instance in that domain.
To deploy virtual member manager EJB in a multiple security domain environment (for example, ejbdomain1 for target server1):
$AdminApp install WAS_HOME/installableApps/wimperdomain.ear {-appname wimperdomain –BindJndiForEJBNonMessageBinding {{wim.ejb WIMService wimejb.jar,META-INF/ejb-jar.xml ejbdomain1/com/ibm/websphere/wim/ejb/WIMServiceHome}} -MapModulesToServers {{wim.ejb wimejb.jar,META-INF/ejb-jar.xml WebSphere:cell=myCell,node=myNode,server=server1}} -systemApp}This procedure enables you to call virtual member manager APIs through EJB for a specific domain. Only users with the required access roles for virtual member manager APIs or superusers in that domain can call the respective APIs.
Limitation: If a virtual member manager EJB is deployed on a managed node, it results in failure of configuration, schema, or file registry update operations.
After deploying the EJB onto a target, either a server or a cluster, that target must be restarted.
See the wsadmin command documentation for "$AdminApp install" in the reference section of the WebSphere information center for the complete command syntax information.
Examples
$AdminApp install WAS_HOME/systemApps/wim.ear {-appname wim -cell MyCell -cluster mycluster -systemApp} $AdminApp install WAS_HOME/systemApps/wim.ear {-appname wim -cell MyCell -server server1 -systemApp}