Configure an entry mapping repository in federated repository

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

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 containing entries for its employees and a database containing 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, we 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.

Restriction: We cannot configure an entry mapping repository in a mixed-version deployment manager cell.

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

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

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

   1. In the console, click Security > Global security.

   2. Under User account repository, select Federated repositories from the Available realm definitions field and click Configure. To configure for a specific domain in a multiple security domain environment, click Security domains > domain_name. Under Security Attributes, expand User Realm, and click Customize for this domain. Select the Realm type as Federated repositories and then 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 used for the property extension repository.

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

      Values include:

      DB2

      com.ibm.db2.jcc.DB2Driver

      
      (zos)

      DB2 for z/OS

      com.ibm.db2.jcc.DB2Driver

      
      (iseries)

      DB2 for iSeries

      com.ibm.db2.jcc.DB2Driver

      Informix

      com.informix.jdbc.IfxDriver

      DataDirect Connect

      com.ddtek.jdbc.sqlserver.SQLServerDriver

      Derby

      org.apache.derby.jdbc.EmbeddedDriver

      Microsoft SQL Server

      com.microsoft.sqlserver.jdbc.SQLServerDriver

      Oracle

      oracle.jdbc.driver.OracleDriver

   7. Supply the database URL 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:

      DB2

      jdbc:db2:wim

      Informix

      jdbc:informix-sqli://host:1526/wim:INFORMIXSERVER=IFXServerName;

      DataDirect Connect

      jdbc:datadirect:sqlserver://host:1433;databaseName=wim;selectMethod=cursor;

      Derby

      jdbc:derby:c:\derby\wim

      Microsoft SQL Server

      jdbc:sqlserver://host:1433;databaseName=wim;selectMethod=cursor;

      Oracle

      jdbc:oracle:thin:@host:port:dbname

   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, the federated repository configuration, which includes an entry mapping repository, is configured.

What to do next

1. After configuring the federated repositories, click Security > Global security to return to the Global security 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 Global security panel. If Federated repositories is not identified in the Current realm definition field, the federated repositories configuration is not used by WebSphere Application Server.

2. If we are enabling security, complete the remaining steps as specified in Enable security for the realm. As the final step, validate this setup by clicking Apply in the Global security 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.

Subtopics

• Entry mapping repository settings
  Use this page to configure an entry mapping repository used to store data for managing profiles on multiple repositories.

Related tasks

Set up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin commands

Configure the WAS data source