Configure an entry mapping repository in a federated repository configuration

 

Follow this task to configure an entry mapping repository that is used to store data for managing profiles on multiple repositories.

 

Overview

An entry-level join means that the federated repository configuration uses multiple repositories simultaneously and recognizes the entries in the different repositories as entries representing distinct entities. For example, a company might have a LDAP directory that contains entries for its employees and a database that contains entries for business partners and customers. By configuring an entry mapping repository, a federated repository configuration can use both the LDAP and the database at the same time. The federated repository configuration hierarchy and constraints for identifiers provide the aggregated namespace for both of those repositories and prevent identifiers from colliding. When you configure an entry mapping repository, you can supply a valid data source, a direct connection configuration, or both. The system first tries to connect by way of the data source. If the data source is not available, then the system uses the direct access configuration.

You cannot configure an entry mapping repository in a mixed-version deployment manager cell.

 

Procedure

1. Configure the data source. See Configure the WAS data source .

2. Set up the entry mapping repository using wsadmin. See Setting up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin commands; ignore the "Before you begin" options.

3. Configure the entry mapping repository into the federated repository by doing the following:

   1. In the console, click Security > Secure administration, applications, and infrastructure.

   2. Under User account repository, select Federated repositories from the Available realm definitions field and click Configure.

   3. Click Entry mapping repository.

   4. Supply the name of the data source in the Data source name field.

   5. Select the type of database that is used for the property extension repository.

   6. Supply the name of the Java database connectivity (JDBC) driver in the JDBC driver field. Values include:

      COM.ibm.db2.jdbc.app.DB2Driver

      Oracle

      oracle.jdbc.driver.OracleDriver

      Informix

      com.informix.jdbc.IfxDriver

      Microsoft SQL Server

      com.microsoft.jdbc.sqlserver.SQLServerDriver

      Derby

      org.apache.derby.jdbc.EmbeddedDriver

      com.ibm.db2.jcc.DB2Driver

      com.ibm.db2.jdbc.app.DB2Driver

   7. Supply the database URL that is used to access the property extension repository with JDBC in the Database URL field. Use an alphanumeric text string that conforms to the standard JDBC URL syntax. Values include:

      jdbc:db2:wim

      Oracle

      jdbc:oracle:thin:@<hostname>:<port>:<dbname>

      Derby

      jdbc:derby:c:\derby\wim

      Microsoft SQL Server

      jdbc:microsoft:sqlserver://<hostname>:1433;databaseName=wim;selectmethod=cursor;

      Informix

      jdbc:informix-sqli://<hostname>:1526/wim:INFORMIXSERVER=<IFXServerName>;

   8. Supply the user name of the database administrator in the Database administrator user name field.

   9. Supply the password of the database administrator in the Password field.

   10. Click OK.

 

Results

After completing these steps, your federated repository configuration, which includes an entry mapping repository, is configured.

 

What to do next

1. After configuring the federated repositories, click Security > Secure administration, applications, and infrastructure to return to the Secure administration, applications, and infrastructure panel. Verify that Federated repositories is identified in the Current realm definition field. If Federated repositories is not identified, select Federated repositories from the Available realm definitions field and click Set as current. To verify the federated repositories configuration, click Apply on the Secure administration, applications, and infrastructure panel. If Federated repositories is not identified in the Current realm definition field, your federated repositories configuration is not used by WebSphere Application Server.

2. If you are enabling security, complete the remaining steps as specified in Enabling security for the realm. As the final step, validate this setup by clicking Apply in the Secure administration, applications, and infrastructure panel.

3. Save, stop, and restart all the product servers (deployment managers, nodes, and Application Servers) for changes in this panel to take effect. If the server comes up without any problems, the setup is correct.

---

Entry mapping repository settings

 

Related tasks

Setting up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin commands
Configure the WAS data source