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 a property extension repository in a federated repository > Set up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin

Manually setting up the property extension repository for federated repositories

Overview

To create tables in the property extension repository for federated repositories, use the script...

createIdMgrPropExtDbTables.sh

The following databases are supported...

• IBM DB2
• Apache Derby
• IBM Informix Dynamic Server
• Oracle 11g
• Microsoft SQL Server

For remote databases, copy the following files from WAS to the system hosting the database. Replicate the directory structure under ../setup.

WAS_HOME/etc/wim/setup/bin/createIdMgrPropExtDbTables.sh
WAS_HOME/etc/wim/setup/bin/createIdMgrPropExtDbTables.bat
WAS_HOME/etc/wim/setup/lookaside/db_type/dbclean.sql
WAS_HOME/etc/wim/setup/lookaside/db_type/schema.sql
WAS_HOME/etc/wim/setup/lookaside/db_type/primarykeys.sql
WAS_HOME/etc/wim/setup/lookaside/db_type/indexes.sql
WAS_HOME/etc/wim/setup/lookaside/db_type/references.sql
WAS_HOME/etc/wim/setup/lookaside/keys.sql
WAS_HOME/etc/wim/setup/lookaside/bootstrap.sql

The db_type variable represents one of the following directory names: db2, oracle, informix, derby, or sqlserver.

Specify the database schema:

To use the default schema of the database, execute the following commands without specifying the DBSCHEMA parameter. Typically, the default schema is the namespace of the current database user.

To replace the schema variable in the SQL files with the actual database schema name.

cd WAS_HOME/etc/wim/setup
export SCHEMA_LOCATION=WAS_HOME/etc/wim/setup/lookaside
export DBTYPE=db_type export
DBSCHEMA=dbschemaname
export SCHEMA_DEST_LOCATION=/path/where/updated/SQL/files/are/copied
./ws_ant.sh -f WAS_HOME/etc/wim/setup/filterbuild.xml

Where the value of db_type is db2, derby, informix, oracle, or sqlserver.

If WAS and the database are not on the same system, set the SCHEMA_LOCATION value to the location where you copied the SQL files.

If SCHEMA_DEST_LOCATION is not set, the updated SQL files are copied to a directory with the name as the value not substituted under the current directory. The output shows where the files are copied.

For Oracle 11g...

• If you did not create the default database when you installed Oracle product, manually create the database before you run createIdMgrPropExtDbTables.sh The value of the ORACLE_SID variable is the same value as the name of the database.

• To create the tables in the schema specified using DBSCHEMA ensure that you create the specified schema in this database before you run the createIdMgrPropExtDbTables.sh script.

• On the AIX, HP-UX, Linux, and Solaris operating systems, run createIdMgrPropExtDbTables.sh either as an Oracle user or as a root user with database administrator (dba) rights and appropriate permissions to run SQL queries as a system database administrator (sysdba).

For IBM DB2 on the Windows operating systems, initialize the DB2 environment before you run createIdMgrPropExtDbTables.bat. At the Windows command prompt, enter db2cmd to open a new DB2 command window and run createIdMgrPropExtDbTables.bat from this prompt.

For Microsoft SQL Server...

cd WAS_HOME\bin
set SCHEMA_LOCATION=WAS_HOME\etc\wim\setup\lookaside
set DBTYPE=sqlserver
set SCHEMA_DEST_LOCATION=\path\where\updated\SQL\files\are\copied
set DBOWNER=dbo
./ws_ant.bat -f WAS_HOME\etc\wim\setup\filterbuild.xml

If WAS and the database are not on the same system, set the SCHEMA_LOCATION value to the location where you copied the SQL files.

If SCHEMA_DEST_LOCATION is not set, the updated SQL files are copied to a directory with the name as the value not substituted under the current directory. The output shows where the files are copied.

The following default instance is created as a part of the database installation:

• DB2: DB2

• Informix: demo_on
• SQL Server: %computername%

The Informix database is created with the following environment:

CLIENT_LOCALE=EN_US.CP1252
DB_LOCALE=EN_US.8859-1
SERVER_LOCALE=EN_US.CP1252
DBLANG=EN_US.CP125

Procedure

Run the createIdMgrPropExtDbTables.sh script or createIdMgrPropExtDbTables.bat script to create the tables in the property extension repository.

Run the script from the following location or from the directory to which you previously copied the script file:

WAS_HOME/etc/wim/setup/bin/createIdMgrPropExtDbTables.sh

Script parameters...

-b	Home directory of the database.
-d	Set to same value specified for DBSCHEMA. Optional for DB2, Derby, and SQL Server databases. Not required for Oracle and Informix databases.
-h	Display help information. (Optional)
-i	Home directory of the database instance. Required for DB2 only; do not specify a value for other database types. Applies to the AIX, HP-UX, Linux, and Solaris operating systems.
-n	Name of the database. For Oracle, ORACLE_SID is the same as the name of the database.
-p	Password of the database administrator. Do not specify a value for a Derby database.
-s	Location of WAS_HOME/etc/wim/setup or location to which the updated files are copied.
-t	Database type: db2, oracle, informix, derby, sqlserver.
-u	User ID of the database administrator. Do not specify a value for a Derby database.

Example

Run the appropriate script for your database and operating system to create tables in the property extension repository. If the database exists on a system where WAS is not installed, the following examples assume that your PATH variable includes an entry for the location to which you copied the script files...

WAS_HOME/etc/wim/setup/bin/

...or...

/setup/bin/

On the AIX, HP-UX, Linux, and Solaris operating systems:

Oracle	createIdMgrPropExtDbTables.sh -b /space/oracle/product/10.2.0/Db_1/ -n orcl -u system -p manager -s /opt/IBM/WebSphere/AppServer1/etc/wim/setup -t oracle
Informix	createIdMgrPropExtDbTables.sh -b /opt/IBM/informix/ -n demo_on -u informix -p informix -s /opt/IBM/WebSphere/AppServer/etc/wim/setup -t informix
DB2	createIdMgrPropExtDbTables.sh -b /opt/ibm/db2/V9.1/ -n db2inst1 -p db2inst1 -s /opt/IBM/WebSphere/AppServer/etc/wim/setup -t DB2 -u db2inst1 -i /home/db2inst1/
Derby	createIdMgrPropExtDbTables.sh -b /opt/ibm/derby/ -n test11 -s /opt/IBM/WebSphere/AppServer/etc/wim/setup -t derby

On the Windows operating systems:

Oracle	createIdMgrPropExtDbTables.bat -b "c:\oracle\product\10.2.0\Db_1" -n orcl -u system -p manager -s "c:\IBM\WebSphere\AppServer1\etc\wim\setup" -t oracle
Informix	createIdMgrPropExtDbTables.bat -b "c:\IBM\informix" -n demo_on -u informix -p informix -s "c:\IBM\WebSphere\AppServer\etc\wim\setup" -t informix
DB2	createIdMgrPropExtDbTables.bat -t db2 -u db2admin -p sec001ret# -n test23 -b "c:\IBM\SQLLIB" -s "c:\IBM\WebSphere\AppServer1\etc\wim\setup"
Derby	createIdMgrPropExtDbTables.bat -t derby -b "c:\Derby" -n test11 -s "c:\IBM\WebSphere\AppServer1\etc\wim\setup"
Microsoft SQL Server	createIdMgrPropExtDbTables.bat -t sqlserver -u sa -p sec001ret# -n sqlsrv -b "c:\Progra~1\Micros~1\90\Tools" -s "C:\Progra~1\IBM\WebSphere\AppServer1\etc\wim\setup"

What to do next

Run...

setupIdMgrPropertyExtensionRepositoryTables -skipDBCreation true

...to populate the tables that are created. Manually set up the property extension repository for DB2 for iSeries or DB2 for z/OS
Set up an entry mapping repository, a property extension repository, or a custom registry database repository using wsadmin
WAS detailed system requirements

+

Search Tips   |   Advanced Search