Integration of Host Publisher objects

Host Publisher and HATS are complementary products you can use together to accomplish a variety of tasks. You can use Host Publisher objects to incorporate data from other legacy systems or databases with data from HATS legacy systems. You can use HATS global variables as a mechanism to share data between HATS variables and Host Publisher inputs and outputs. From HATS business logic, templates, and transformations, you can invoke Remote Integration Objects, EJB Access beans, and Web Services. You can also import Host Publisher macros into your HATS project. See Incorporating macros for information on importing macros into HATS.

Invoking Host Publisher Remote Integration Objects from HATS

You can invoke Host Publisher Remote Integration Objects from HATS. Although Host Publisher Server must be installed somewhere in your network to invoke Remote Integration Objects, it does not need to be installed on the same WebSphere Application Server as HATS.

To invoke Host Publisher Remote Integration Objects into your HATS project, you must first import the Remote Integration Objects into your HATS project. Refer to the section titled "Remote Integration Object Files" in the IBM WebSphere Host Publisher Programmer's Guide and Reference for information on importing Host Publisher Remote Integration Objects into WebSphere Studio workbench. After the Host Publisher Remote Integration Objects are imported into HATS, you can call the Remote Integration Objects from your HATS business logic or from HATS templates or transformations, by using in-line Java code enclosed in <%...%>. See the section titled "Programming with Remote Integration Objects" in the IBM WebSphere Host Publisher Programmer's Guide and Reference for more information.

To invoke a Host Publisher Remote Integration Object from HATS business logic, right-click in the HATS Project View tab of the HATS Studio and select New HATS > Business Logic. Enter a Java class name and package name and click Finish. A skeleton HATS business logic template is displayed. For a sample of the template updated to execute a Host Publisher Remote Integration Object, see the product Web site (http://www.ibm.com/software/webservers/hats).

Invoking Host Publisher EJB Access Beans and Web Services from HATS

You can invoke Host Publisher EJB Access Beans and Host Publisher Web Services from HATS. Although Host Publisher Server must be installed somewhere in your network to invoke EJB Access Beans, it does not need to be installed on the same WebSphere Application Server as HATS.

To invoke Host Publisher EJB Access Beans into your HATS project, you must first import the EJB Access Beans into your HATS project. Refer to the section titled "Using EJB Access Beans with Java Application Clients" in the IBM WebSphere Host Publisher Programmer's Guide and Reference for information on importing EJB Access Beans into WebSphere Studio workbench. After the EJB Access Beans are imported into HATS, you can call EJB Access Beans from your HATS business logic or from HATS templates or transformations. See the section titled "Programming with Web Services Integration Objects and EJB Access Beans" in the IBM WebSphere Host Publisher Programmer's Guide and Reference for more information.