Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Configuring TIBCO ActiveMatrix Runtime UDDI Server : Configuring the UDDI Server in the Interactive Mode

Configuring the UDDI Server in the Interactive Mode
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.
1.
2.
Run srvconfig under the TIBCO_HOME/RuntimeUDDIServer/3.1/bin directory.
Run ant -f srvconfig.xml under the TIBCO_HOME/RuntimeUDDIServer/3.1/scripts/server directory.
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:
Please choose the following options:
(1): Configure All
(2): Configure the Database
(3): Configure the Container
(4): Configure the Server Domain
(5): Configure the Server Host and Port
(6): Configure the Server Root User and Password
(7): Configure SMTP for the Subscription Email Notification
(8): Configure the Folder for the Server Log File(s)
(9): Configure the Customized JAAS Module
(10): Configure the Product Name and Logo for UI
Your Option: ([1], 2, 3, 4, 5, 6, 7, 8, 9, 10)
The default option is option (1).
The first time you configure the uddi.war file you must choose option (1) to configure all the items.
Configure All
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:
(1) Tomcat
(2) JBoss
(3) WebSphere
Your Option: ([1], 2, 3)
Choose the container type that you have previously configured. Option (1) is the default option.
(1): HSQLDB
(2): SQL Server
(3): Oracle
(4): MySQL
(5): DB2
(6): Sybase
Your Option: ([1], 2, 3, 4, 5, 6)
Choose the database type that you have previously configured. Option (1) is the default option.
Configure the Container
To configure the web container, use the following prompt that appears on the screen:
(1) Tomcat
(2) JBoss
(3) WebSphere
Your Option: ([1], 2, 3)
Choose the type of the web container that you want to use.
Configure the Database
To configure the database, use the following prompts that appear on the screen:
(1):  HSQLDB
(2):  SQL Server
(3):  Oracle
(4):  MySQL
(5):  DB2
(6):  Sybase
Your Option: ([1], 2, 3, 4, 5, 6)
Choose the database type that you want to use.
yes: tables are created automatically during deployment
no: tables need to be created manually before deployment
Your option: ([yes], no)
Whether to auto-create the database schema.
The uddi.sql script to create the database schema is generated in the following location:
TIBCO_HOME/RuntimeUDDIServer/3.1/war/dist/CONTAINER_TYPE/
DATABASE_TYPE
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.
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 example:
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"
Configure the Server Domain
To configure the server domain, use the following prompt that appears on the screen:
Enter the domain name of the server.
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.
Configure the Server Root User and Password
To configure the root username and password, use the following prompts that appear on the screen:
Enter the default administrator’s login name.
Enter the default administrator’s password.
Configure the Server Host and Port
To configure the host and port number, use the following prompt that appears on the screen:
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.
Configure SMTP for Subscription Email Notification
To configure email notification, use the following prompts that appear on the screen:
Enter the host name for the SMTP server.
Enter the port number for the SMTP server. The default port number is 25.
Enter the email address from which the subscription notification will be sent.
This option allows you to require authentication for the SMTP server. The default is false.
If you choose true, the following options will appear on the screen:
Enter your email account in the SMTP server.
Enter the password to access the SMTP server.
Configure the Folder for Server Log File
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.
To configure log settings, use the following prompt that appears on the screen:
Please specify a directory where the server log file(s) will be stored: (optional, the default directory is user.home)
Enter the absolute path for the log output folder.
On Windows, user.home refers to %USERPROFILE%
On Unix, user.home refers to $HOME
Configure Customized JAAS Module
To configure the JAAS module, use the following prompt that appears on the screen:
yes: You will be asked for additional question.
no: No further action is required.
Whether to customize JAAS (Java Authentication and Authorization Service).
If you enter yes, the following prompts appear on the screen:
Please enter the customized JAAS Login Module configuration file:
Enter the path of the customized JAAS Login Module configuration file.
For example: /home/user1/my_jaas.properties
Please enter customized JAAS Login Module implementation file
Enter 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.
Configure the Product Name and Logo for UI
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?
yes: You will be asked for additional question.
no: No further action is required.
Whether to replace the Administration Console or Service Console names.
If you enter yes, the following prompts appear on the screen:
Enter the path of the properties file with the replacement names.
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.
yes: You will be asked for additional question.
no: No further action is required.
Whether to replace the Administration Console logo.
If you enter yes, the following prompt appears on the screen:
Please provide a .gif file to replace the Administration Console logo:
Enter the path of the .gif logo file.
For example: /home/user1/admin_logo.gif
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/srvconfig
yes: You will be asked for additional question.
no: No further action is required.
Whether to replace the Service Console logo.
If you enter yes, the following prompt appears on the screen:
Please provide a .gif file to replace the Service Console logo:
Enter the path of the .gif logo file.
For example: /home/user1/service_logo.gif
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
Copyright © TIBCO Software Inc. All Rights Reserved