Follow this task to configure an entry mapping repository
that is used to store data for managing profiles on multiple repositories.
About this task
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 Lightweight
Directory Access Protocol (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.
Restriction: You cannot configure an entry mapping repository
in a mixed-version deployment manager cell.
Procedure
- Configure the WebSphere® Application Server data source. See Configuring the WebSphere Application Server data source .
-
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.
- Configure the entry mapping repository into the federated
repository by doing the following:
- In the administrative console, click .
- 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 .
Under Security Attributes, expand User Realm,
and click Customize for this domain. Select
the Realm type as Federated repositories and
then click Configure.
- Click Entry mapping repository.
- Supply the name of the data source in the Data source
name field.
- Select the type of database that is used for the property
extension repository.
- Supply the name of the Java™ database
connectivity (JDBC) driver in the JDBC driver field.
Values
include:
- DB2®
- com.ibm.db2.jcc.DB2Driver
- DB2 for z/OS®
- com.ibm.db2.jcc.DB2Driver
- 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
- 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:
- 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 Password field.
- Click OK.
Results
After completing these steps, your federated repository configuration,
which includes an entry mapping repository, is configured.
What to do next
- 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,
your federated repositories configuration is not used by WebSphere Application Server.
- 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 Global security
panel.
- 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.