A Comprehensive Guide to IBM WebSphere Host Publisher Version 3.5

450 IBM WebSphere Host Publisher Version 3.5

16.2 RIO XML interface and the XML Legacy Gateway

Although both the RIO support and the XML gateway in Host Publisher provide

an XML interface to applications, there are some basic differences which we

summarize in this section:

1. The RIO XML interface:

– It provides an XML interface to a single Integration Object via XML over

HTTP or HTTPS.

– RIO XML is a single transaction providing inputs that map one-to-one with

the Integration Object input variables, and has outputs that map

one-to-one with the Integration Object output variables.

2. The XML Legacy Gateway extends a HOD emulator session to render the

data from each window in XML and then HTML (with JavaScript) by applying

a stylesheet. In general:

– It retrieves, after a programmed delay, the current state of the host window

as XML data from the xmlAppData JavaBean.

– It formats the XML data as HTML output using an XSL stylesheet and an

XSL processor. This output is returned to the browser.

– The user can interact with the HOD terminal entering data and pressing

PF keys, and the output from that interaction is shown in HTML (via XSL

applied to XML).

For details about how the XML gateway has been implemented in Host

Publisher, see Chapter 18, “XML Legacy Gateway” on page 567.

16.3 RIO Studio support

As illustrated in Figure 16-2 on page 451, RIO support is included for a specific

Integration Object (IO) when the Integration Object is saved with the RIO option.

This option is always set by default, but it can be easily turned off if RIO support

is not required. In this section, we describe how the Host Publisher Studio is

used to generate RIO support for your database and host Integration Objects.

16.3.1 Creating RIO support

Remote Integration Object (RIO) support is provided by the Host Publisher

Studio via RIO files generated when Integration Objects are created.

Chapter 16. Remote Integration Objects (RIO) 451

Remote Integration Objects (RIO) files are generated when you select the

Create Remote Integration Object option in the menu bar, as illustrated in

Figure 16-2. The Host Publisher Studio creates the supporting files, tools and

sample programs that you can use to access your Integration Object from

different client devices. These files are created when you save the database or

host Integration Object.

Figure 16-2 Create Remote Integration Object (RIO) option

RIO properties

The Host Publisher Studio generates a Java file called the RIO proxy to provide

RIO support for Java client applications. The RIO proxy is actually a JavaBean

that can be instantiated by Java programs (applets, applications and servlets).

The RIO proxy runs on the client device and the Java client uses setter and

getter methods to set its input and output properties, respectively.

When you generate the RIO support for your Integration Object, you will be

prompted to enter the prefix for the name of the RIO proxy. The default value is

Remote (see Figure 16-3 on page 452) and you can either change the name of

the prefix or set it to blank characters. The latter will make the RIO proxy have

exactly the same name as the corresponding Integration Object.

452 IBM WebSphere Host Publisher Version 3.5

Figure 16-3 Remote Integration Object: properties

Saving the Integration Object

Once the database or host Integration Object has been created with the RIO

option in the Host Publisher Studio, the RIO files are generated. Figure 16-4

shows the resulting window.

Figure 16-4 Saving the Integration Object

In this window, you can optionally click the Details button to view the RIO file

creation activity as illustrated in Figure 16-5 on page 453.