Set an entry mapping repository in a federated repository configuration
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 an 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, we can supply...
- Data source.
- Direct connection
- 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.
We cannot configure an entry mapping repository in a mixed-version dmgr cell.
- Set the data source.
- Set up the entry mapping repository using wsadmin.
- Set the entry mapping repository into the federated repository...
- In the admin console, click...
Security | Global security | User account repository | Available realm definitions | Federated repositories | Set | Entry mapping repository- Supply the name of the data source in the Data source name field.
- Select the type of database used for the property extension repository.
- Supply the name of the JDBC driver in the JDBC driver field. Values include:
- 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
- Supply the database URL used to access the property extension repository with JDBC in the Database URL field. include:
- 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
- Supply the user name of the database administrator in the Database administrator user name field.
- Supply the password of the database administrator in the field.
- Click OK.
Results
After completing these steps, the federated repository configuration, which includes an entry mapping repository, is configured.
Next steps
- After configuring the federated repositories, click...
Security | Global securityVerify 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 WAS.
- If 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.
- Save, stop, and restart all WAS servers...
- dmgrs
- nodes
- 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
Set up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin commands
Set the WAS data source