Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Before You Begin
  4. Pre-Installation Tasks
  5. B2B Data Exchange Installation
  6. Post-Installation Tasks
  7. Installing the Partners Portal on Non-B2B Data Exchange Nodes
  8. Upgrading B2B Data Exchange
  9. Starting and Stopping B2B Data Exchange
  10. Optional B2B Data Exchange Configuration
  11. Migrating OEM Managed File Transfer Endpoint
  12. Installing and Configuring the B2B Data Exchange Accelerator for Data Archive
  13. Uninstallation

Installation and Configuration Guide

Installation and Configuration Guide

After You Upgrade

After You Upgrade

After you upgrade, update the
B2B Data Exchange
configuration files to work with the upgraded instance of
B2B Data Exchange
.
To
update the configuration files and
complete the upgrade process, perform the following steps:
  1. Reapply modifications that were made to
    B2B Data Exchange
    configuration files in previous versions.
  2. If you installed the Dashboard and Reports component, register the license of the Dashboard and Reports component.
  3. If you installed the Dashboard and Reports component, import the operational data store (ODS) loader workflow.
  4. To unregister the existing PowerCenter server plug-in, click the Plug-ins tab after the Repository Service restarts. Click the unregister icon (next to the existing plug-in) to unregister the plug-in.
  5. Use the PowerCenter Administration Console to register the plug-in in the PowerCenter repository.
  6. Restart PowerCenter workflows.
  7. Start the
    B2B Data Exchange
    Server.
  8. If any of the
    B2B Data Exchange
    repositories are installed on a Microsoft SQL Server and use Windows authentication, configure credentials for Windows authentication.
  9. Clear the browser cache on each of the client machines.
  10. If you upgrade the Partners Portal component, to provide existing portal users with Partners Portal privileges, create portal user groups and then assign each portal user to a portal user group.
    If you do not assign a portal user to a portal user group, the portal user can only view the Dashboard in the Partners Portal.
  11. If you installed the Partners Portal component, you can brand the Partners Portal with the organization logo.
    If you used your logo in the previous version, you must perform this task after the upgrade in order to re-brand the portal.
  12. Informatica OEM MFT 10.2.2.HF1 does not support Azule's JDK. Therefore, you have to manually download and Install Oracle's JDK and then change the path of JDK in
    B2B Data Exchange
    and Managed FileTransfer after the upgrade. Perform the following steps to manually update the upgrade path :
    • To change the JDK path in
      B2B Data Exchange
      , modify
      <DX_HOME>/DataExchange/bin/setenv.(bat/sh)
      file to update the
      JAVA_HOME
      value.
    • To change the JDK path in Managed File Transfer, modify the JDK paths (including Java and DJava.ext.dirs) in all
      .lax
      files that reside in the
      <DX_HOME>/ManagedFileTransfer
      folder.
The
B2B Data Exchange
installer does not delete the previous version of
B2B Data Exchange
. The installer renames the folder with the suffix
_Backupn.n.n
where n.n.n is the version number that you upgraded. To ensure that you update the configuration files correctly, see the configuration files in the directory of the previous version of
B2B Data Exchange
.
To migrate endpoint data for the OEM Managed File Transfer component to Informatica Managed File Transfer, use the migration tool. Refer to Migrating OEM Managed File Transfer Endpoint Overview for usage information.

0 COMMENTS

We’d like to hear from you!