+

Search Tips   |   Advanced Search

Establishing custom adapters for federated repositories

Out of the box adapters for federated repositories provide File, LDAP, and Database adapter for our use. These adapters implement the com.ibm.wsspi.wim.Repository software programming interface (SPI). Custom adapters for federated repositories need to implement the same SPI.

Refer to the Repository SPI implementation information in the related references for information about the custom adapters for federated repositories SPI.

Refer to the sample custom adapter code that is available in the vmmsampleadapter.jar file. The JAR file contains the sample customer adapter code in the src/ directory. The vmmsampleadapter.jar can be downloaded at this location: http://www.ibm.com/developerworks/websphere/library/samples/vmmsampleadapter.html

Custom adapters for federated repositories must not depend on any WebSphere Application Server components, such as data sources and enterprise beans. These WebSphere Application Server components require that security is initialized and enabled prior to startup. If our implementation of the virtual member manager custom adapter needs to use data sources to connect to a database, we need to use Java database connectivity (JDBC) to make the connection during server startup. Then, at a later time, switch to using the data sources when the data source is available.


Tasks

  1. Build your implementation.

    EMF JAR files contain version number in their names, such as v200607270021. Make sure to change the version number to reflect the installation. To compile your code, we need the following JAR files in the classpath:

    • app_server_root/plugins/com.ibm.ws.runtime_6.1.0.jar
    • app_server_root/plugins/org.eclipse.emf.commonj.sdo_2.1.0.v200607270021.jar
    • app_server_root/plugins/org.eclipse.emf.ecore_2.2.1.v200607270021.jar
    • app_server_root/plugins/org.eclipse.emf.common_2.2.1.v200607270021.jar
    • app_server_root/plugins/org.eclipse.emf.ecore.xmi_2.2.0.v200607270021.jar
    • app_server_root/plugins/org.eclipse.emf.ecore.sdo_2.2.0.v200607270021.jar

    Here is an example:(Dist) (ZOS) 

    app_server_root/java/bin/javac -classpath 
app_server_root/plugins/com.ibm.ws.runtime_6.1.0.jar;
app_server_root/plugins/org.eclipse.emf.commonj.sdo_2.1.0.
v200607270021.jar;app_server_root
/plugins/org.eclipse.emf.ecore_2.2.1.v200607270021.jar;
app_server_root/plugins/org.eclipse.emf.common_2.2.1.
v200607270021.jar;app_server_root/plugins/org.
eclipse.emf.ecore.xmi_2.2.0.v200607270021.jar;
app_server_root/plugins/org.eclipse.emf.ecore.sdo_2.2.0.v200607270021.jar
your_implementation_file.java
    (iSeries) 
    "${java.home}/bin/javac -classpath
app_server_root/plugins/com.ibm.ws.runtime_6.1.0.jar;app_server_root/plugins/org.eclipse.emf.commonj.sdo_2.1.0.
v200607270021.jar;app_server_root/plugins/org.eclipse.emf.ecore_2.2.1.v200607270021.jar;
app_server_root/plugins/org.eclipse.emf.
common_2.2.1.v200607270021.jar;app_server_root/plugins/org.eclipse.emf.ecore.xmi_2.2.0.v200607270021.jar;
app_server_root/plugins/org.eclipse.emf.
ecore.sdo_2.2.0.v200607270021.jar your_implementation_file.java"

  2. Copy the generated class files or the packaged JAR file to the product classpath. The preferred location is the app_server_root/lib/ext directory. This should be copied to the classpaths of all the product processes (cell and all NodeAgents).

  3. Configure our custom adapter by following the steps in Configure custom adapters for federated repositories using wsadmin.
  4. Test our custom adapter by following the steps in Use custom adapters for federated repositories


What to do next

Configure custom adapters for federated repositories using wsadmin provides details about configuring the custom adapter with the wsadmin tool.

Related tasks:

  • Configure custom adapters for federated repositories using wsadmin
  • Use custom adapters for federated repositories

    Related reference:

  • Sample custom adapters for federated repositories examples