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. Post-Upgrade Tasks
  10. Search Configuration Upgrade
  11. Hierarchies 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. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrade External Calls and Applications

Upgrade External Calls and Applications

Effective in version 10.4, Multidomain MDM uses certificate-based authentication to authenticate external calls and applications. To use external calls and custom applications, you must configure a trusted application user. Also, EJB is not supported for external calls. You must use the HTTP communication protocol instead.
If your business entity services and custom applications use the BESExternalCall sample code and libraries included in the Resource Kit from a version prior to 10.4, perform the following upgrade steps:
  1. Configure a trusted application user for the custom application.
  2. Configure the following connection properties in the
    bes-client.properties
    file:
    Connection Property
    Description
    siperian-client.protocol
    Communication protocol that you want to use. Default is HTTP. Do not change the default value.
    bes-client.http.url
    URL for the custom application to connect to MDM. Use the following syntax:
    http://<MDM host>:<port number>/cmx
    Default is
    http://localhost:8080/cmx
    .
    The sample
    bes-client.properties
    file is in the following directory:
    <Resource Kit installation directory>/samples/BESExternalCall/source/resources
  3. Review the CustomLogicService class in the
    CustomLogicService.java
    file in the BESExternalCall sample and implement the use of a trusted application user.
    The following code sample shows the CustomLogicService class:
    public class CustomLogicService implements Provider<Source> { @Override public Source invoke(Source request) { CompositeServiceClient compositeServiceClient = createCompositeServiceClient(); CustomLogicFactory customLogicFactory = new CustomLogicFactoryImpl(compositeServiceClient); String appName = "<trusted application user>"; ExternalCallProcessor externalCallProcessor = new ExternalCallProcessor(compositeServiceClient, appName, customLogicFactory); return externalCallProcessor.invoke(request); } private static CompositeServiceClient createCompositeServiceClient() { InputStream resourceAsStream = CustomLogicService.class.getResourceAsStream("/bes-client.properties"); Properties config = new Properties(); try { config.load(resourceAsStream); } catch (IOException e) { throw new RuntimeException(e); } return CompositeServiceClient.newCompositeServiceClient(config); }
  4. Build the custom application to use the following updated JAR files:
    • siperian-api.jar
    • siperian-common.jar
    • mdm-spi.jar
    After you build the application, the external calls and applications use the HTTP communication protocol and certificate-based authentication.
  5. Redeploy the custom application on the application server.

0 COMMENTS

We’d like to hear from you!