Publish WSDL zip files

Use this page to publish Web Services Description Language (WSDL) files.

To view this administrative console page, click Applications >Enterprise Applications > application_instance > Publish WSDL.

To view this administrative console page in V5.1.1, click Applications >Enterprise Applications > application_instance > Publish WSDL zip files.

If you are using V5.0.2 or 5.1, when you click OK, a zip file of all the Web services-enabled modules in the application is produced. The name of the published zip file is application_name_WSDLFiles.zip. In the published zip file, the directory structure is application_name/module_name/[META-INF|WEB-INF]/wsdl/wsdl_file_name.

If you are using V5.1.1, when you click OK, a panel showing one or many zip file names displays. Each zip file contains a WSDL file that represents the Web services-enabled modules in the application. When you select a zip file to publish, a dialogue displays from which you can choose where to create the zip file. Within the published zip files, the directory structure is application_name/module_name/[META-INF|WEB-INF]/wsdl/wsdl_file_name.

In a published WSDL file, the location attribute of a service soap:address stanza contains the URL through which the Web service is accessed. You can specify the portion of the URL to be used for the Web services in each module. You can access the Web services in a module through a HTTP transport or JMS transport, or both. You can specify URL information for both types of transports.

In a published WSDL file, the location attribute of a port's soap:address element contains the endpoint URL through which the Web service is accessed. Using the Provide HTTP endpoint URL information and the Provide JMS and EJB endpoint URL information panels, configure the endpoint URLs to be used for the Web services in each module.

 

Configuration tab

application_name_WSDLFiles.zip

Specifies the application_name_WSDLFiles.zip file containing the WSDL file that describes Web services that are accessible by standard SOAP-based ports.

application_name_ExtendedWSDLFiles.zip

Specifies the application_name_ExtendedWSDLFiles.zip file containing the WSDL file that describes the Web services available, including SOAP-based and non-SOAP based (for example, EJB) ports.

If there are no Web services configured for direct EJB access, this zip file name does not appear. Do not use this zip file if you want to produce a WSDL file compliant to standards.

Specify URL prefixes for Web Services

Specifies the protocol (either http or https), host_name, and port_number to be used in the URL.

The URL prefix format is protocol://host_name:port_number, for example, http://myHost:9045. The actual URL that appears in a published WSDL file consists of the prefix prepended to the module's context-root and the Web service url-pattern, for example, http://myHost:9045/services/myService.

Select HTTP URL prefix

Specifies the drop down list associated with a default list of URL prefixes. This list is the intersection of the set of ports for the module's virtual host and the set of ports for the module's appserver. Use items from this list if the Web services appserver is accessed directly.

To set an HTTP prefix, select either the HTTP URL prefix or Custom HTTP URL prefix, enter the value, select the check box of the modules that are to use the prefix, and click Apply. When you click Apply, the entry in the Select HTTP URL prefix or Custom HTTP URL prefix fields, depending on which is selected, is copied into the HTTP URL prefix field of any module whose check box (in the leftmost column) is selected. The HTTP prefix is not applied to the fields in the JMS URL prefix column.

Custom HTTP URL prefix

Specifies the protocol, host, and port_number of the intermediate service if the Web services in a module are accessed through an intermediate node, for example the Web services gateway or an IHS server.

To set an HTTP prefix, select either the HTTP URL prefix or Custom HTTP URL prefix, enter the value, select the check box of the modules that are to use the prefix, and click Apply. When you click Apply, the entry in the Select HTTP URL prefix or Custom HTTP URL prefix fields, depending on which is selected, is copied into the HTTP URL prefix field of any module whose check box (in the leftmost column) is selected. The HTTP prefix is not applied to the fields in the JMS URL prefix column.

JMS URL prefix

Specifies the JMS URL prefix string used for each module.

The URL prefix specified must contain the destination and connectionFactory properties. It can contain other property-value pairs, but it must not contain the targetService property, which is added by the system when the published WSDL files are created. The format of the JMS URL prefix is jms:/[queue&topic]?destination=target_queue_or_topic_jndi_name&connectionFactory=factory_jndi_name, for example,

jms:/queue?destination=jms/Q1&connectionFactory=jms/QCF. The actual URL that appears in a published WSDL file consists of the prefix prepended to the Web service targetService, for example, jms:/queue?destination=jms/Q1&connectionFactory=jms/QCF&targetService=StockQuote.

    

 

---