![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
After installing TIBCO ActiveMatrix Runtime UDDI Server, the configuration commands must be run before deployment. See TIBCO ActiveMatrix Runtime UDDI Server Installation for information about installing TIBCO ActiveMatrix Runtime UDDI Server.
2. Run one of the following commands and use the interactive mode to configure the UDDI server.
−
− If there is no build.properties file under the TIBCO_HOME/RuntimeUDDIServer/3.1/template directory, the command execution will switch to the interactive mode and will prompt the following questions:
The first time you configure the uddi.war file you must choose option (1) to configure all the items.If you choose option (1), items (2) through (10) listed above will be configured in order. Then the uddi.war file will be generated.If you need to reconfigure the items (2) through (10), you will be asked to indicate the previously configured container and database. The following prompts appear on the screen:Choose the container type that you have previously configured. Option (1) is the default option.Choose the database type that you have previously configured. Option (1) is the default option.
• Would you like to automatically create database tables when deploying the .war file?The uddi.sql script to create the database schema is generated in the following location:If you do not choose to automatically create the database schema, you need to manually execute the script to create the tables in the database before deployment, otherwise the database schema are automatically created during the first deployment.
• Would you like to specify default_schema attribute (required for DB2 and Oracle RAC only)If you select yes, then the following prompts appear on your screen.You need to specify the default schema for the database user that creates or updates uddi server database.
When using Oracle 11g RAC, you need to specify the default_schema attribute only if two users use the same tablespace.For Oracle, MySQL and DB2 databases, the value you specify here for the default schema must be consistent with the value written in the content.xml file. If you have installed the default server for the TIBCO ActiveMatrix Runtime UDDI Server, the content.xml file is located in the TIBCO_HOME\RuntimeUDDIServer\3.1\server\conf directory.
− For Oracle, if you specify UDDI as the default schema, the value of the user name written in the content.xml file must be username="UDDI".
− For DB2, if you specify UDDI as the default schema, the value written in the content.xml file must be url="jdbc:db2://Host:Port/DatabaseName:traceLevel=3;driverType=4;currentSchema=UDDI;"
− For MySQL, if you specify UDDI as the default schema, the value written in the URL attribute must be url="jdbc:mysql://Host:Port/UDDI?autoReconnect=true"
• The server domain will be the part of the default generated UDDI key. For example, uddi:serverDomain:UniqueValue
• You cannot modify the server domain name after it has been configured and TIBCO ActiveMatrix Runtime UDDI Server has been deployed.This is true even if you reconfigure it.To configure the root username and password, use the following prompts that appear on the screen:
• Please enter the server host and the port number: [localhost:8080]Enter the host name where your web container runs and the port number configured in the web container to accept the HTTP request. The default host name and port number is localhost:8080.
You cannot modify the host name and port number after they have been configured and TIBCO ActiveMatrix Runtime UDDI Server has been deployed. This is true even if you reconfigure them.If you choose true, the following options will appear on the screen:While running TIBCO ActiveMatrix Runtime UDDI Server, two log files are created in the log output folder. One log file records how TIBCO ActiveMatrix Runtime UDDI Server runs, and the other records how the client accesses TIBCO ActiveMatrix Runtime UDDI Server.
• Please specify a directory where the server log file(s) will be stored: (optional, the default directory is user.home)
If you do not specify the log output folder here, the two log files are created in the default log output folder.
•
•
− If you enter yes, the following prompts appear on the screen:Enter the path of the customized JAAS Login Module configuration file.
For example: /home/user1/my_jaas.propertiesEnter the path of the customized JAAS Login Module implementation file.
For example: /home/user1/login_module.jar
− If you enter no, the default JAAS Login Module is used.For detailed information about the customized JAAS Login Module, refer to Configuring the Customized JAAS Login Module for LDAP Users.To configure the product name and the logo for Administration Console and UDDI Service Console, use the following prompts that appear on the screen:Would you like to replace the names of Administration Console and Service Console?
• If you enter yes, the following prompts appear on the screen:The sample properties file is located in the following directory: TIBCO_HOME/RuntimeUDDIServer/3.1/sample/srvconfig/uibranding.properties.The value of the sc.caption property in the properties file will be the Service Console name.If you enter yes, the following prompt appears on the screen:Please provide a .gif file to replace the Administration Console logo:If you enter no, the default logo file uibranding-logo.gif is used. It is available from the following directory:TIBCO_HOME/RuntimeUDDIServer/3.1/sample/srvconfigIf you enter yes, the following prompt appears on the screen:If you enter no, the default logo file sc-uibranding-logo.gif is used. It is available from the following directory:TIBCO_HOME/RuntimeUDDIServer/3.1/sample/srvconfig
• If you enter no, the default names of Administration Console and Service Console are used.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |