New Features... 1 Installation... 3 Upgrade Changes... 3 Fixed Limitations... 4 Known Limitations... 5 Informatica Global Customer Support...

Transcription

1 Informatica Corporation B2B Data Exchange Version Release Notes June 2012 Copyright (c) Informatica Corporation. All rights reserved. Contents New Features... 1 Installation... 3 Upgrade Changes... 3 Fixed Limitations... 4 Known Limitations... 5 Informatica Global Customer Support... 7 This document contains important information about installation, fixed limitations, and known limitations for B2B Data Exchange. Do not upgrade to this release from a previous version without carefully reading the relevant sections on upgrading and bug fixes, since bug fixes may change the behavior of existing functionality. New Features B2B Data Exchange offers the following new features and enhancements: Dashboard and reports The extended Dashboard displays personalized visual reports about information that B2B Data Exchange processes. Use the Dashboard to view summary information about B2B Data Exchange event processing, such as the number of events for a specific partner or the accounts with the highest error rate. Most of the reports in the Dashboard are based on key performance indicators (KPIs) that B2B Data Exchange retrieves from the operational data store. You create the operational data store when you install the B2B Data Exchange Dashboard and Reports component. The operational data store collects aggregated event information from the run-time B2B Data Exchange repository with the operational data store event loader. The event loader is a PowerCenter workflow that loads events from the run-time B2B Data Exchange repository at predefined intervals. In addition to the default KPIs, you can instruct the event loader to load event attribute values. The B2B Data Exchange developer can use Logi Info Studio to create custom Dashboard panels based on the default KPIs or the event attribute values. If you upgrade from version and install the Dashboard and Reports component, the B2B Data Exchange installer replaces the previous basic Dashboard. DX-RLN

2 Event archiving with Data Archive You can use the B2B Data Exchange accelerator for Data Archive to archive events from the main B2B Data Exchange repository. With the B2B Data Exchange accelerator, you can use Data Archive to create archive projects with advanced parameters, such as event status or event type. You can also schedule standalone or recurring archive jobs, and browse or search for archived events and documents. If you use B2B Data Exchange with Data Archive 5.3.6, you can archive events and documents to the history database for short-term archiving and view the archived events from the Archived Events page of the Operation Console. You can still use the archive command line utility to perform basic event and document archiving. Audit trail enhancement You can use the enhanced audit trail to track actions that operators perform on objects in the Operation Console, APIs, or the command line utilities, such as creating or editing a partner or an account. Each audit record contains detailed information about the action and the object, such as the name of the user that performed the action and the actual values that were changed. B2B Data Exchange no longer stores audit records as events. If you upgrade from earlier versions, you can still view and archive legacy audit trail events. Authorization You can use authorization to comply with the organization business or legal need to monitor and regulate actions that operators perform in the Operation Console on partners, accounts, and profiles, before B2B Data Exchange completes the action. You define authorization levels for different actions or objects. For example, you can require approval by 2 operators every time an operator deletes a partner. Operators with authorization privileges review and approve or reject the pending operator actions. B2B Data Exchange completes the action and generates an audit record after approval. The object is locked for editing while an operator action is pending. Forms Designer Java API You can populate lists in the Forms Designer with values from external sources. Use the classes, interfaces, and methods in the API to determine the source of the values and set default values for the list. You can configure the API to throw an exception in case an error occurs while the Forms Designer retrieves the values. When you use the Forms Designer, you see an indication for any list with values from an external source. Storage of endpoint files in Hadoop file systems (HDFS) You can store backup copies of files that B2B Data Exchange processes through Managed File Transfer or File Receive endpoints in HDFS. You configure the HDFS location and credentials in B2B Data Exchange system properties. When you define the endpoint, you can use the HDFS root directory to determine the location in which to save the file. For Managed File Transfer endpoints, you can store incoming files in HDFS. You can use B2B Data Exchange with several Hadoop versions. Select the Hadoop version based on the organization needs. Password encryption command line utility When you install B2B Data Exchange, configuration properties and system property values that contain passwords are stored as encrypted strings. If you modify any of the passwords, you use the password encryption command line utility to encrypt the password and use the encrypted string. 2 DX-RLN

3 Installation Before you install or upgrade B2B Data Exchange, verify that your system meets the minimum requirements and follow the pre-installation steps. For information about installing or upgrading B2B Data Exchange, see the B2B Data Exchange Installation and Configuration Guide. B2B Data Exchange Installation Limitations When you install B2B Data Exchange on IBM AIX 6.1 operating systems, an error message may appear with the following text: Unzip: not found. (XE-6569) Workaround: Ignore the error message. When you install the B2B Data Exchange server plug-in for PowerCenter on IBM AIX operating systems, an error message may appear in cases where PowerCenter 9.5 is installed on the same machine without JDK. The error message includes the following text: java.policy doesn't exist. (XE-6824) Workaround: Ignore the error message. When you install or uninstall B2B Data Exchange on IBM AIX operating systems in console mode, an error message may appear with the following text: Hostname and service name not provided or found. (XE-6870) Workaround: Ignore the error message. When you upgrade from B2B Data Exchange while another application uses the dx-tools folder, the installer does not import account attribute values to the B2B Data Exchange repository. (XE-6839) Workaround: Before you upgrade, verify that no other application uses the dx-tools folder. B2B Data Exchange Accelerator for Data Archive Installation Prerequisites Before you import the B2B Data Exchange accelerator to Data Archive 5.3.6, contact Informatica Global Customer Support. Upgrade Changes When you upgrade to B2B Data Exchange 9.5.0, consider the following functionality and behavior changes: Java Development Kit (JDK) is not installed on IBM AIX operating systems. Install and configure JDK before you install B2B Data Exchange. Java Cryptography Extension (JCE) is not installed on IBM AIX operating systems. If you use B2B Data Exchange with Managed File Transfer, install JCE before you install B2B Data Exchange. The archive command line utility does not use the dx.event.status.category.success system property and the dx.event.status.category.failed system property to determine if an event reached a final or an error status. Instead, B2B Data Exchange stores the information in the event status. The archive command line utility determines which events to archive based on whether the event reached a final state, regardless of the error state. Names and identifiers of custom attributes for partners and accounts are case-insensitive. During the upgrade process, the B2B Data Exchange installer removes all duplicate names or identifiers and the log describes the removal information. The installer does not remove attribute definitions. If you import partners or accounts from earlier versions that contain duplicates, the import process rejects all duplicates and throws an exception. DX-RLN

4 B2B Data Exchange does not create events for audit records, and does not convert audit trail events from previous versions to enhanced audit records. You can use the archive utility to archive and delete all of the legacy audit trail events before you upgrade. If you keep the legacy audit events from earlier versions, you can view the events after you upgrade in the Legacy Audit Events page. You can also archive the legacy audit events with the B2B Data Exchange Accelerator for Informatica Data Archive or the B2B Data Exchange archive utility after you upgrade. When an event reconciliation completes successfully, B2B Data Exchange generates a single entry in the Processing Information tab of the event details instead of multiple entries for each stage of the reconciliation process. To improve performance and reduce bottlenecks, B2B Data Exchange creates a temporary file for every incoming file that it processes through Managed File Transfer endpoints in the following folder: <DXDocumentStore>\mft. Each file name includes the prefix dx_, the name of the incoming file, and the extension.tmp. To conserve disk space, periodically delete temporary files that B2B Data Exchange created in the folder at least 24 hours earlier. You cannot configure session replication for B2B Data Exchange in a cluster environment. B2B Data Exchange uses the dx.endpoint.jms.provider.url system property to determine if the B2B Data Exchange JMS Broker service is running. After you upgrade, you cannot view the Properties tab of the DX_Generate_Temporary_File transformation. To use this option, delete and re-add the transformation. In the B2B Data Exchange repository on Microsoft SQL Server, the type of the CORRELATION_IDENTIFIER column in the DX_CORRELATION table is NVARCHAR(255) instead of VARCHAR(255). In the B2B Data Exchange repository on Oracle and Microsoft SQL Server, the type of the CORRELATION_ID column in the DX_CORRELATION table is NUMERIC(19,0) instead of VARCHAR(255). Fixed Limitations Issue XE-6776 XE-6756 XE-6624 XE-6469 XE-6444 XE-6288 XE-6154 You cannot create event attributes for notifications that contain the prefix dx_*. The DX_Profile_Parameter and the DX_Increment_Profile_Parameter transformations may not process read-only profile parameters correctly. When B2B Data Exchange processes events through endpoints, the events do not include the related partner and account for profiles that do not include partners and accounts. When B2B Data Exchange processes a large number of document files through Managed File Transfer endpoints, B2B Data Exchange may take a long time to delete the temporary rows from the B2B Data Exchange repository. When you view schedules on multiple pages, the schedule list does not appear correctly. The DX_Event_Details transformation may not process events with statuses longer than 20 characters correctly. Editing a partner with a large number of accounts for which there is a large number of account attributes may take a long time. 4 DX-RLN

5 Issue XE-6084 XE-6071 XE-6044 XE-5974 XE-5881 XE-5771 XE-5717 You cannot run the pingjms command on the B2B Data Exchange server. When you configure a PowerCenter mapping, you cannot create a source data port with a name that is shorter than 5 characters. If you configure B2B Managed File Transfer to use a forward proxy by default, you cannot run batch workflows in B2B Data Exchange. When you run a simple Web Service endpoint request, strict validation of the Web Service API response might fail. When you install B2B Data Exchange with the HTTPS protocol, and configure Apache with HTTP, the Operation Console fails to appear. When you upgrade to version and select HTTPS as the sole connection setting without selecting HTTP, then you must manually update the following B2B Data Exchange URL system properties: - dx.console.url - dx.mft.console.url if B2B Data Exchange Managed File Transfer is installed - issue.tracking.url if issue tracking is installed - pwc.webservices.url if PowerCenter web services hub uses HTTPS From the Operation Console import/export feature, the user cannot export partners with more than 500 accounts in one file. Known Limitations CR XE-6877 XE-6849 XE-6846 XE-6834 XE-6695 XE-6657 XE-6545 XE-6531 If you assign a batch workflow to a profile, the Delayed Processing tab and the scheduling options may be disabled. Workaround: Save and re-edit the profile. If you schedule a monitor or an endpoint to run once, you cannot reschedule the monitor or endpoint to run once within 2.5 hours of the previous run. When you delete an object with information that the Dashboard displays in a panel and then create an object with the same name, the operational data store event loader fails. Workaround: Do not delete objects with information that the Dashboard uses. When you use B2B Data Exchange on Apache Hadoop 1.0 machines with the IBM AIX operating system, you cannot store files that B2B Data Exchange processes through File Receive or Managed File Transfer endpoints in the Hadoop file system. Workaround: Upgrade the Apache Hadoop version to or later. If you create a delayed processing rule for a profile that contains event properties with incorrect or incomplete default values, B2B Data Exchange may enable the Delay All Events processing rule. Workaround: Discard the event and define correct event attribute values for the profile. If you use B2B Managed File Transfer and you move the B2B Data Exchange repository to a different machine, B2B Managed File Transfer does not replace the database connection. Workaround: Manually delete the previous database connection in the Databases section of the Managed File Transfer administrator console. When you work with B2B Data Exchange workflows, you cannot move a group of profile parameters into one of its child groups. If you import a batch workflow to B2B Data Exchange before you define the workflow type, B2B Data Exchange may not recognize the batch workflow. Workaround: Delete the workflow file and define the workflow type before you re-import the workflow. DX-RLN

6 CR XE-6423 XE-6409 XE-6403 XE-6283 XE-6011 The operational data store event loader does not load events that B2B Data Exchange processed during the last hour before daylight savings time begins. If a PowerCenter session fails, the operational data store event workflow may not display a failed status. Workaround: Monitor the PowerCenter session to verify the success of the run. You cannot use the DX_Aggregate transformation in a PowerCenter session with multiple partitions. When you modify a Managed File Transfer endpoint, B2B Data Exchange does not generate an audit record for mailbox or host changes. When you install B2B Data Exchange with Managed File Transfer and you select HTTPS as the protocol, the following messages appear in the MFT log: Local Listener Error: HTTP/s SSL Server Certificate does not exist. Local Listener Result: "Exception" "java.net.bindexception: Port <PortNumber> - Address already in use... If installation was successful, the following message also appears and you can ignore the error messages: Local Listener Detail: Started Listener ports - <List of Ports, including HTTP/s> level=2 XE-5983 XE-5972 XE-5958 XE-5951 When you install B2B Data Exchange with Web Services API connectivity and you select ISP authentication, B2B Data Exchange fails due to failure to connect to the PowerCenter Web Server Hub. Workaround: Use a user name from the Native authentication group for the PowerCenter Web Services Hub and PowerCenter Domain panels of the installer. When you reprocess an event created with a default source document that was dropped into an endpoint configured for Pass by Reference, extra characters are appended to the source file name in the Input Message Log. When you install B2B Data Exchange with Managed File Transfer on a Linux or UNIX platform and you select HTTPS as the protocol, the Managed File Transfer process does not terminate when the installer terminates. Workaround: Shut down the Managed File Transfer process before you start B2B Data Exchange to register the license. When you install B2B Data Exchange with Managed File Transfer on a Linux or UNIX platform and you select HTTPS as the protocol, and you then start B2B Data Exchange to register the license, there are two instances of the MFT process and only one terminates when you close B2B Data Exchange. Workaround: Install the license file, close B2B Data Exchange, and then kill the MFT processes or run mft.sh stop or shutdown.sh. XE-5947 XE-5909 XE-5895 XE-5822 When the server and browser are running in different time zones, the partner date attribute is sometimes saved with an incorrect date value. Workaround: Use a String data type instead of a date field. When the developer uses the Profile Parameters custom transformation to define a workflow parameter that starts with "DX", the output port for this parameter is always null and the transformations fail. Workaround: Do not start parameter names with "DX". This prefix is reserved for internal system use only. When you click the Overview button on the Events List screen, you cannot scroll to the bottom of the screen. Workaround: Resize the window. When you install B2B Data Exchange with SQL server and use both the instance name and the port, B2B Data Exchange fails and the following error message appears in the log: FATAL [com.informatica.b2b.dx.bootstrap.dxruntimecontrolimpl] {main} Fatal error in starting the servicesorg.springframework.beans.factory.beaninitializationexception: DX Repository not found. Workaround: Enter a connection string without a port number or without the instance name. 6 DX-RLN

7 Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Europe / Middle East / Africa Asia / Australia Toll Free Brazil: Mexico: North America: Toll Free France: Germany: Italy: Netherlands: Portugal: Spain: Switzerland: United Kingdom: Toll Free Australia: New Zealand: Standard Rate India: Standard Rate Belgium: France: Germany: Netherlands: United Kingdom: DX-RLN