Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository

Configure an entry mapping repository in a federated repository

Overview

An entry-level join means that the federated repository uses multiple repositories simultaneously and recognizes the entries in the different repositories as entries representing distinct entities. For example, a company might have...

• LDAP directory that contains entries for its employees
• Database that contains entries for business partners and customers

By configuring an entry mapping repository, a federated repository can use both the LDAP and the database at the same time. The federated repository 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.

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

Procedure

1. Configure the WAS data source.

2. Set up the entry mapping repository using wsadmin.

   Ignore the "Before you begin" options.

3. Configure the entry mapping repository into the federated repository...

   1. In the console, click...
      Security | Global security | User account repository | Available realm definitions | Federated repositories | Configure

      To configure for a specific domain in a multiple security domain environment, click...

      Security domains | domain_name | Security Attributes | User Realm | Customize for this domain | Realm | Federated repositories | Configure | Entry mapping repository

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

   3. Select the type of database used for the property extension repository.

   4. Supply the name of the JDBC driver...

      DB2	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

   5. 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.

      DB2	jdbc:db2:wim
      Informix	jdbc:informix-sqli://host_name:1526/wim:INFORMIXSERVER=IFXServerName;
      DataDirect Connect	jdbc:datadirect:sqlserver://host_name:1433;databaseName=wim;selectMethod=cursor;
      Derby	jdbc:derby:c:\derby\wim
      Microsoft SQL Server	jdbc:sqlserver://host_name:1433;databaseName=wim;selectMethod=cursor;
      Oracle	jdbc:oracle:thin:@host_name:port:dbname

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

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

   8. Click OK.

Results

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

What to do next

1. After configuring the federated repositories, verify that Federated repositories is identified in the Current realm definition field...
   Security | Global security

   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, your federated repositories configuration is not used by WAS.

2. If you 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 (dmgrs, nodes, and Application Servers) for changes in this panel to take effect. If the server comes up without any problems, the setup is correct.

Related

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

+

Search Tips   |   Advanced Search