Migrating from Host Publisher Version 4

If you are currently a Host Publisher V4 user, you can migrate whole projects or just the Integration Objects from your existing projects. When you import Host Publisher .ear files, the Integration Objects remain packaged in the .jar file.

If the Integration Object was in a Web Module, the .jar file is in the WEB-INF/LIB directory. If the Integration Object is in an EJB module, the .jar file is in the imported_classes\IntegrationObject directory. The EJB Access Beans also remain packaged in the .jar file in the WEB-INF/LIB directory of the Web Module.

If you import an .ear and modify the macro for which an Integration Object has been created, you will have the original Integration Object .jar that was imported, as well as the Java™ source. After you have regenerated the Integration Object for HATS, you can delete the imported .jar file.

Below is a list of considerations when migrating from Host Publisher V4:

  • If you import a Host Publisher EJB application, an error will show up when you try to run the application. You receive a java.lang.NoClassDefFoundError for com/ibm/HostPublisher/IntegrationObject/HPubReqCompleteEvent. To correct this, regenerate the EJB Access Beans and delete the EJB Access Bean .jar files in the WEB-INF\LIB directory of your Web application. In addition, to fix compile errors for name mismatches, you must update the EJB Access Bean names to reference newly generated names in any JavaServer Pages or Java™ code .
  • If you have Integration Objects or EJB Access Beans with Web service support, you need to regenerate the Web services. For information about regenerating Web services, refer to the Developing Web services.
  • Database Access Integration Objects are deprecated in HATS V6 or later. If you import a Host Publisher application that contains Database Access Integration Objects, the Integration Objects are preserved in a .jar file. However, you cannot create new Database Access Integration Objects in HATS V6 or later. You can use the relational database tools in Rational® SDP to access your relational databases.
  • Defined XML Gateway connections are not migrated. You can define HATS applications using the default transformation to achieve the same function as the XML Gateway connections.
  • The XML Legacy Gateway SDK is not available in HATS.
  • Host Publisher Express™ Logon is not supported in HATS. Integration Objects that were configured to use Express™ Logon must be configured to use HATS Web Express™ Logon (WEL). If you import an Integration Object that contains Express™ Logon Feature (ELF) support, the Integration Object is migrated without error, but a warning is issued that ELF is not supported and that WEL must be used to achieve the equivalent function. You must re-record your connect macros to use WEL actions, associate the Integration Object connections with the new WEL macros, and also do the WEL configuration. See Using Web Express Logon (WEL) for more information. The Integration Objects will not perform as intended unless this is done.
  • Encrypted user lists are now supported in HATS. However, encrypting user lists with a user-chosen encryption key is not supported in HATS. Importing a Host Publisher user list that was encrypted with a user-chosen encryption key requires supplying the key that was used to encrypt the user list. The user list is decrypted during import. After import you may encrypt the user list for use with HATS. To do this, open the connection editor, click the User List tab, and select Encrypt user list properties. Only the User ID, Description, and Password fields can be edited on the User List tab. If you must edit any user-defined properties you added to your Host Publisher user list, you must first clear Encrypt user list properties on the User List tab, and then click the Source tab to edit the property values. Do not edit the schema element. If you wish to encrypt the user list again, click the User List tab, select Encrypt user list properties, and save the file. Regardless of whether you choose to encrypt your user list data, you should use file system security and physical security measures to protect any sensitive data.
  • If you have Integration Objects that were created using a modified template, the following sequence should be used for migrating the Host Publisher application that contains these Integration Objects:
    1. Import the Host Publisher EAR. You will receive warnings that you are importing Integration Objects that contain a modified template.
    2. If any of the Integration Objects that you imported contained data that was extracted as a table, import those individual Integration Objects.
    3. Modify the Integration Object templates that are provided with HATS to achieve the same customizations you defined in Host Publisher. See Programming with Integration Objects for more information.