Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Upgrading from Version 10.0, 10.1, 10.2, or 10.3

Upgrading the SiperianClient Library Classes for the EJB Protocol

Upgrading the SiperianClient Library Classes for the EJB Protocol

If you use the EJB protocol to communicate with the MDM Hub through the Services Integration Framework (SIF) requests, you must use the latest version of the SiperianClient library classes. If you use custom JNDI lookup methods, update the lookup methods so that the methods conform to the EJB3 conventions.
  1. Replace the existing SiperianClient library classes with the latest version of the SiperianClient library classes.
    The
    siperian-api.jar
    file located in the following directories contains the SiperianClient library classes:
    • <Resource Kit Installation Directory>\sdk\sifsdk\lib
    • <MDM Hub Installation Directory>\hub\server\lib
  2. If you use custom JNDI lookup methods, update the lookup methods so that the methods conform to the EJB3 conventions.

0 COMMENTS

We’d like to hear from you!