Core Config Database Registry Configuration

Figure 38. Registry Configuration - Database Backend type A menu of databases from which to select the vendor of your database. Hostname Database host name or IP address, for example, dbserver.mycompany.com Port Database port number. Database Name Database name; for example, uddinode User Name User name; uddiuser by default User Password Database user password;uddi by default Default pool size Count of concurrent database connections initialized at start time Page 344

2.2. Database

Max pool size Maximum count of concurrent database connections. Each request books one connection until the request is served. If all connections are booked and new request comes in, the connection pool creates a new connection till the maximum count is reached. If this maximum is reached and new request comes in, this request must wait for a free connection to be released by a previous request. Pool cleaning interval How often database connections are closed over the default count. This value represents time in hours. Database cache This is used for performance optimization. Pessimistic Locking This option is not recommended unless there are excessive deadlock recovery messages in the log. It affects performance.

2.3. Security

On the Security tab, you can configure your digital signature token and key properties. Figure 39. Registry Configuration - Security AuthInfo Time Out Authorization token is obtained by invoking the get_authToken method. This token is used for each operation on the publishing port. Here you can set up the authorization token time-out in seconds. The default value is one hour. Token Creation Time Tolerance Tolerance interval of token validity, expressed in milliseconds. Page 345

2.3. Security

XML DSig Provider Registry performs XML digital security operations via an XML digital security provider. There are two XML digital security providers in the distribution. ssj Uses the XML digital security implementation of Systinet Server for Java. oracle Uses the Oracle XML digital security implementation. Registry Console offers the following options: Default XML digital security provider specified by the value of the registry.xml.dsig.providerName system property. The default when no such property is set is ssj. SSJ ssj XML digital security provider. Oracle oracle XML digital security provider. Note Oracle XML digital security libraries are bundled in Oracle Application Server since version 10.1.3. Oracle XML digital security provider does not work in previous releases of Oracle Application Server unless Oracle XML digital security libraries are installed.

2.4. Account

On this tab, you can specify accounts properties applicable for all Oracle Service Registry user accounts. Page 346

2.4. Account