Registration options
Use the following options to register repositories, databases, and servers with the metadata repository.
Each of the registration options requires the use of the -propertyFile option and a properties file. Some product modules provide property file templates that you can edit, such as one for an IBM® InfoSphere® DataStage® operations database. Or, if a repository similar to the one that you want to register has already been registered, then you can use a display option with the -results parameter to redirect the output to a file and edit the resulting file. You can also, of course, create the properties file from scratch. Each of the following options shows an example properties file with the entries that are required for the particular entity to be registered.
-registerRepository -propertyFile filename [-saveSQLScripts [-scriptLocation directory_path]]
Shorthand:
-rr -pf filename [-sss [-sl directory_path]]
Registers a repository with the metadata repository. A repository is typically registered by the installation program during its corresponding tool installation, or manually as part of an upgrade. New repositories can also be registered for any given tool after installation, for tools that support multiple repositories, or as part of the process of relocating an existing repository to a different database.
The properties file that you provide with the command must contain at least the properties identifying the database with which the repository is to be registered, in addition to the full set of required repository properties.
Example command:
RepositoryAdmin.bat -registerRepository -pf odb.properties
Example of a properties file with the properties needed for repository registration:
DatabasePlatform.databaseType=DB2 DatabasePlatform.version=10.5 DatabaseServer.host=localhost DatabaseServer.port=50000 Database.name=odb Database.alias=odb Database.location=C:\ Repository.name=odb Repository.description=Production engine ODB. Repository.tool=DataStage Repository.context=production Repository.schema=odb RepositoryConnection.name=odb RepositoryConnection.userName=odb RepositoryConnection.password={iisenc}gwFQseoj24I/SnCFEH+cWg==
Tip: It is best to provide the password as an encrypted string by using the encrypt command, or you can provide a plain text password. The password is stored in encrypted form, however, and will always be shown as an encrypted string when you display the repository.If you have not yet registered a server or database, these will also be registered when you register the repository. In such a case, however, your properties file must contain the necessary information associated with the database and server to be registered.
In this example, a new repository named odb is registered with a database named odb. If the database is not already registered, then the database is first registered with the database server on the host localhost for the Db2 10.5 platform. If the database server is not already registered, the database server is registered so that the new database and repository can be registered with it. The repository connection is also registered.
If you are registering a new repository, you can provide the -saveSQLScripts parameter at the same time that you register a repository. By specifying this parameter, the SQL scripts necessary to create and set up the repository, with replaced parameters, are saved to disk. For example:
RepositoryAdmin.bat -rr -pf odb.properties -saveSQLScripts
Saving the SQL scripts here is a shortcut to avoid the need to run the
RepositoryAdmin
tool again with the -saveSQLScripts parameter.-registerDatabase -propertyFile filename
Shorthand:
-rd -pf filename
Registers a database with the metadata repository. The database is typically registered by the installation program as part of the repository registration during the installation process. You can register a database on its own, independently of any tool after installation, and then register new repositories with the database later.
The properties file that you provide with the command must contain at least the properties identifying the database server with which the database is to be registered, in addition to the full set of required database properties.
Example command:
RepositoryAdmin.bat -registerDatabase -propertyFile dbsrv.properties
Example properties file:
DatabasePlatform.databaseType=DB2 DatabasePlatform.version=10.5 DatabaseServer.host=localhost DatabaseServer.port=50000 Database.name=odb Database.alias=odb Database.location=C:\
-registerDatabaseServer -propertyFile filename
Shorthand:
-rs -pf filename
Registers a database server with the metadata repository. The database server is typically registered by the installation program as part of the repository registration during the installation process. You can register a server on its own, independently of any tool after installation, and then register new databases with the server later.
The properties file that you provide with the command must contain at least the properties identifying the database platform with which the database server is to be registered, in addition to the full set of required database server properties.
Example command:
RepositoryAdmin.bat -registerDatabaseServer -propertyFile dbsrv.properties
Example properties file:
DatabasePlatform.databaseType=DB2 DatabasePlatform.version=10.5 DatabaseServer.host=localhost DatabaseServer.port=50000 DatabaseServer.binPath=C:\IBM\SQLLIB\BIN DatabaseServer.adminUser=db2admin DatabaseServer.adminPassword={iisenc}fwGPejos3/I1QmTGHExwGc==
Tip: It is best to provide the password as an encrypted string by using the encrypt command, or you can provide a plain text password. The password is stored in encrypted form, however, and will always be shown as an encrypted string when you display the database server.