![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
To execute an Ant-based task, you must first connect to the UDDI server. You can provide connection information to the UDDI server using one of the following methods:By default, an Ant-based task uses the URL properties in the uddi.properties file to connect to a UDDI server. You can modify the URL properties in the uddi.properties file to have the Ant-based tasks connect to the desired UDDI server.
• Providing the information in CLI through -D options. For example:
To assign a value to a property through a -D option, you need to enclose the value in double quotation marks if the value contains spaces. For example, -Dname="my value".The common properties required by all the Ant-based tasks are stored in the uddi.properties file. Each time you execute an Ant-based task, the task reads the properties stored in the file if you do not specify your own properties in command line through -D options.By default, the uddi.properties file is stored in the following directory: TIBCO_HOME/RuntimeUDDIServer/3.1/scripts/client.Normally, a uddi.properties file contains the following sections:
• URL Properties contain URL properties required by different types of Ant-based tasks.
• User confidential information contains the username and password used to access the server. You can provide an encrypted password for the password property.
• HTTPS Properties contain properties used to access HTTPS servers.
• Proxy Properties contain properties used to access proxies.A uddi.properties file contains the following information:where, Host is the name or the IP address of the host where TIBCO ActiveMatrix Runtime UDDI Server resides, and Port is the port number of the port through which UDDI services are provided.
If you want to inquiry anonymously, enable the anonymous inquiry in TIBCO ActiveMatrix Runtime UDDI Server and remove the username and password fields, or set username=emptyString, password=emptyString in the uddi.properties file.Executing an Ant-based task requires specific URL properties. The URL properties required vary with Ant-based task types. Currently, the following five URL properties are used: inquiry_URL, publish_URL, security_URL, subscription_URL, and admin_URL. By default, the URL properties specified in the uddi.properties file are used. You can also specify your own URL properties using -D parameters in CLI when executing an Ant-based task, as shown below.Table 3, Ant-based Tasks and the Corresponding Required URL lists Ant-based tasks and the corresponding required URL properties.
inquiry_URL, security_URL With anonymous inquiry disabled, all the Ant-based tasks require the security_URL property.With anonymous inquiry enabled, the security_URL is unnecessary to find tasks and get tasks. Moreover, if only the inquiry_URL is used, the username and password properties can be left empty; if other URLs are used, the username and password are necessary.The read-only permission is required to access an inquiry_URL or a publication_URL. You need to be a publisher to access a publication_URL; you need to be a subscriber to access a subscription_URL.To create a subscription that adopts the asynchronous notification mechanism, both the publication_URL and the subscription_URL are required. inquiry_URL, security_URL inquiry_URL, publication_URL, security_URL inquiry_URL, publication_URL, security_URL Subscription tasks subscription_URL, security_URL
In order for TIBCO Business Studio, TIBCO ActiveMatrix Administrator, and TIBCO ActiveMatrix BusinessWorks to work with TIBCO ActiveMatrix Runtime UDDI Server, anonymous inquiry must be enabled in TIBCO ActiveMatrix Runtime UDDI Server. You can enable anonymous inquiry in TIBCO Administrator Console.When connecting to the UDDI server, you are required to provide a username and the corresponding password. To avoid your password from being disclosed, you can encrypt your password by adding #! or #!! at the beginning of the password entered.The strings #! and #!! encrypt passwords in different ways. A password prefixed by #! is encrypted using a fixed symmetric key. In this case, the password is valid on any machines. A password prefixed by #!! is encrypted using a key generated by the local machine. In this case, the password is valid only on the local machine.Note that the string #! and #!! are reserved by TIBCO for password encrypting. Do not use them as the beginning of any clear text passwords.For more information on encrypting a password, see Encrypting a Password for the UDDI Server in TIBCO ActiveMatrix Runtime UDDI Server Administrator’s Guide.HTTPS uses digital certificates to control access to servers. To access an HTTPS server, you need to first import the corresponding digital certificates either as individual certificate files or to a trusted keystore file.HTTPS properties allow Ant-based tasks to access HTTPS web servers. They provide the information about the digital certificates to be used and are required when the URLs assigned to the URL properties point to HTTPS servers. The HTTPS properties are described as follows.
• trustStoreFolder, the folder where the digital certificate files are located. If you import the digital certificates as individual certificate files, provide the path of the certificate files for this property.
• keystorePath, the path of the trusted keystore. If you import the digital certificates to a trusted keystore file, provide the path of the keystore file for this property.
• keystoreType, the type of the keystore. Keystore type is specified when a keystore is created. This property is required if you import the digital certificate to a trusted keystore file. The two keystore types commonly used in TIBCO products are JKS and PKCS12. For related information, see Appendix A: Standard Names in Java Cryptography Architecture API Specification & Reference at http://java.sun.com/javase/6/docs/technotes/guides/security/crypto/CryptoSpec.html.
• keystorePassword, the password used to access the trusted keystore. This property is required if you import the digital certificate to a trusted keystore file.
For TIBCO ActiveMatrix Runtime UDDI Server, only one-way certificate verification is supported. That is, only the client verifies the server’s certificate. The server, however, does not verify the client’s certificate. The client can be Ant-based tasks, HTTP GET requests, and Service Console requests.Proxies are usually deployed for servers to implement additional control functions, such as monitoring and filtering the data and requests between servers and clients. For TIBCO ActiveMatrix Runtime UDDI Server, a proxy is usually used if the port assigned to it cannot be exposed externally. If a proxy is deployed and you want Ant-based tasks to access the server through the proxy, you need to set the proxy properties properly.
• proxyHost, the IP address of the host operating as the proxy.
• proxyPort, the port on the proxy for HTTP requests.
• proxyUsername, the username used to access the proxy.
• proxyPassword, the password used to access the proxy.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |