Vitria businessware: Web Services

Businessware Web services are an important part of the integration platform. This part is indeed powerful and easy to use.

Businessware can be used as a WebService client to call the WebService released by other applications and as a WebService server. The whole process model is published as WebService for other applications to call; in the modeling tool BME, you can easily complete this process through a visual interface and wizard.

 

1. As the WebService Server

The visualization component that completes this function is Web Input proxy. drag and drop from the panel to the model, you can configure it in several ways:

• Directly connect its output port to the input port of a process model. The process model is automatically published as WebService, and its interfaces and operations are as follows, is the interface and operation defined on its input port.

• If you specify a Java interface for the interface through the wizard, it will publish the interface as WebService. Of course, you need to connect a process model to provide an implementation of this service.

• If you use the Wizard to specify a WSDL location for it, it will parse the WSDL, generate a Java interface, and then publish it as WebService. Of course, you need to connect a process model to provide an implementation of this service.

Another way to do this is to right-click the input port of a process model and select "WebService output" from the menu ", then, BME automatically creates a Web Input proxy for you and connects it to the port to complete the release.

You can directly export the published WebService as a wsdl file in BME, or view its WSDL in the browser after the process is started.

 

2. As a WebService Client

The visualization component that completes this function is Web output proxy and Web Service State. The configuration of the two is basically the same. You can use the Wizard:

• Specify the WSDL of the WebService to be called. It can be used by the local file system or remote web system.

• Automatically parses the WSDL and allows you to select the port to be called.

• Finally, the client stub file is automatically generated for your Java code to call.

 

3. Weak type

However, businessware also provides an opportunity for you to directly operate SOAP envelope by changing the port type of Web Input/Output Proxy from a specific strong type to a General Com. vitria. types. xmlservices, so that you can get the SOAP header, payload, and even attachments from the parameters passed to you by the framework, or construct the whole SOAP envelope to call the WebService released by other applications.

There are several advantages to doing so. For example, you can process attachments. The most important thing is that a strong interface is replaced by a common interface. You can change the interface without affecting the customer code.

For example, you change a parameter from an integer to a string. If you cannot directly process soap, the old customers who use this interface have to make changes. In contrast, you use Com. vitria. types. xmlservices, you can convert the integer parameter in the SOAP request sent by the old customer into a string, and then perform real Processing

Do not worry that the customer program of BW WebService has to manually construct the SOAP request. You can use a strong type at the beginning and export the WSDL for the client to generate a strong type of stub, then change the Web Input proxy to a common xmlservices type.

 

Appendix:

1. BW Web Service is implemented based on Apache axis, so its stability and interoperability are extremely reliable.

2. Some time ago, I used BEA WebLogic Workshop 8.1. After searching for half a day, I didn't find any menus. The Wizard allowed me to specify the WSDL and generate the client stub, later, Google found that Bea provided an ant extension to do this. You need to manually write the build. XML, huh, I don't know if the new workshop version has the built-in function?