File name: twim_entrymaprepos.html
Configuring 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.
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 Security > Secure administration,
applications, and infrastructure.
- Under User account repository, select Federated repositories from
the Available realm definitions field and 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:
- 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
- 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>;
- 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 > 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.
- 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.
- 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.
In this information ...
| IBM Redbooks, demos, education, and more(Index)
Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof.
|
|
