Creating ModelRepositoryService
Creating ModelRepositoryService
© 2009 Informatica
Abstract
This article describes how to create a Model Repository Service. It also provides overview, requirement, and configuration
information for a Model Repository Service.
Supported Versions
¨ Data Services 9.0.0
Table of Contents
Model Repository Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Model Repository Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
IBM DB2 Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Microsoft SQL Server Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Oracle Database Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
General Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Repository Database Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Search Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Advanced Properties for Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Custom Properties for the Model Repository Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Properties for the Model Repository Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Node Properties for the Model Repository Service Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Creating a Model Repository Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
You can use the Administrator tool or the infacmd command line program to administer the Model Repository Service. You
create one Model Repository Service for each Model repository. When you create the Model Repository Service, you can
create a new Model repository or use an existing Model repository. You manage users, groups, privileges, and roles on the
Security tab of the Administrator tool. You manage permissions for Model repository objects in the Informatica Developer
and the Informatica Analyst.
Because the Model Repository Service is not a highly available service and does not run on a grid, you assign each Model
Repository Service to run on one node. If the Model Repository Service fails, it automatically restarts on the same node. You
can run multiple Model Repository Services on the same node.
2
Each Model repository must meet the following database requirements:
¨ Have its own schema. Two Model repositories or the Model repository and the domain configuration database
cannot share the same schema.
¨ Have a unique repository database name.
¨ On the IBM DB2 instance where you create the database, set the following parameters to ON:
- DB2_SKIPINSERTED
- DB2_EVALUNCOMMITTED
- DB2_SKIPDELETED
- AUTO_RUNSTATS
¨ On the database, set the following configuration parameters:
Parameter Value
applheapsz 8192
appl_ctl_heap_sz 8192
logfilsiz 4000
DynamicSections 1000
maxlocks 98
locklist 50000
auto_stmt_stats ON
Note: DB2 version 9.5 only
In a single-partition database, specify a tablespace that meets the pageSize requirements. If you do not specify a
tablespace, the default tablespace must meet the pageSize requirements.
In a multi-partition database, you must specify a tablespace that meets the pageSize requirements.
¨ The database user account must have the CREATETAB and CONNECT permissions.
3
Oracle Database Requirements
Use the following guidelines when you set up the Oracle database:
Parameter Value
open_cursors 1000
¨ The database user account must have the CONNECT and RESOURCE permissions.
¨ General properties
¨ Search properties
¨ Advanced properties
¨ Custom properties
Property Description
Name Name of the Model Repository Service. The name is not case sensitive and must less than 128
characters. The name cannot have leading or trailing spaces, carriage returns or tabs. The name
cannot contain the following characters:
/*?<>"|
Node Displays the node on which the Model Repository Service runs.
Property Description
4
Property Description
Password An encrypted version of the database password for the Model repository.
JDBC Connect String The JDBC connect string used to connect to the Model repository database.
For example, the connection string for an Oracle database contains the following syntax:
jdbc:informatica:oracle://Cadillac:
1521;SID=Marble;MaxPooledStatements=20;CatalogOptions=0;EnableServerResultCache=
true
The connection string for IBM DB2 and Microsoft SQL Server uses DatabaseName, not SID.
Dialect The SQL dialect for a particular database. The dialect maps java objects to database objects.
For example:
org.hibernate.dialect.Oracle9Dialect
For more information about dialects, see the Hibernate documentation:
https://www.hibernate.org/
Database Schema The schema name for a Microsoft SQL Server database.
Property Description
Search Analyzer The fully qualified java class name of the search analyzer.
Default is:
com.informatica.repository.service.provider.search.analysis.MMStandardAnalyzer
For example, specify the following java class name of the search analyzer for Chinese, Japanese
and Korean languages:
org.apache.lucene.analysis.cjk.CJKAnalyzer
Search Analyzer Factory The fully qualified java class name of the factory class.
Property Description
Maximum Heap Size Amount of RAM in megabytes allocated to the Java Virtual Manager (JVM) that runs the Model
Repository Service. Use this property to increase the performance. Default is 1024 megabytes.
JVM Command Line Options Java Virtual Machine (JVM) command line options to run Java-based programs. When you
configure the JVM options, you must set the Java SDK classpath, Java SDK minimum memory,
and Java SDK maximum memory properties.
You must set the following JVM command line options:
- Xms. Maximum heap size. Default value is 256 m.
- MaxPermSize. Maximum permanent generation size. Default is 128 m.
- Dfile.encoding. File encoding. Default is UTF-8.
5
Custom Properties for the Model Repository Service
Custom properties include properties that are unique to your environment or that apply in special cases. A Model Repository
Service process does not have custom properties when you initially create it. Use custom properties only if Informatica
Global Customer Support instructs you to.
Note: You must select the node to view the service process properties in the Service Process Properties section.
¨ Search properties
¨ Audit properties
¨ Repository properties
¨ Custom Properties
¨ Environment variables
The following table describes the search properties for the Model Repository Service process:
Property Description
Search Index Root Directory The directory that contains the search analyzer index files.
Default is:
./target/repository/1249674846269/prs/index
The following table describes the repository database properties for the Model Repository Service process:
Property Description
Hibernate Connection Pool Size The hibernate connection pool size. Default is 10.
Hibernate C3P0 Max Size The maximum hibernate C3P0 size. Default is 10.
Hibernate C3P0 Min Size The minimum hibernate C3P0 size. Default is 1.
6
Property Description
Hibernate C3P0 Max The maximum number hibernate C3P0 statements. Default is 500.
Statements
Activate Dump Persistence Writes persistence configuration to a log file. The Model Repository Service logs information about
Configuration to File the database schema, object relational mapping, repository schema change audit log, and
registered IMF packages. The Model Repository Service creates the log file when the Model
repository is enabled, created, or upgraded. The Model Repository Service stores the logs in the
specified repository logging directory. If a repository logging directory is not specified, the Model
Repository Service does not generate these log files. You must disable and re-enable the Model
Repository Service after you change this option. Default is False.
Activate Log Persistence SQL Writes parameterized SQL statements to a log file, which is stored in the specified repository
to File logging directory. If a repository logging directory is not specified, the Model Repository Service
does not generate these log files. You must disable and re-enable the Model Repository Service
after you change this option. Default is False.
For more information about hibernate and persistence, see the Hibernate documentation:
https://www.hibernate.org/
The following table describes the audit properties for the Model Repository Service process:
Property Description
Audit Enabled Displays audit logs in the Log Viewer. Default is False.
The following table describes the repository properties for the Model Repository Service process:
Property Description
Repository Logging Directory The directory that stores logs for Dump Persistence Configuration or Log Persistence SQL. Do not
specify a directory path to disable the logs. These logs are not the repository logs that appear in
the Log Viewer. Default is blank.
Repository Logging Severity The severity level for repository logs. Valid values are: fatal, error, warning, info, trace, and debug.
Level Default is info.
7
Environment Variables for the Model Repository Service Process
Environment variables for the Model Repository Service process.
The following table describes the environment variables for the Model Repository Service process:
Property Description
Environment Variables Environment variables defined for the Model Repository Service process.
9. Click Finish.
Authors
Manuel Castro
Principal Technical Writer
Dominic Sartorio
Senior Product Manager
Acknowledgements