WebSphere Product Center: Release Notes for Version 5.2
Note! Before using this information and the product it supports, read the information in "Notices" at the end of this document.
23 March2005
This edition of this document applies to WebSphere Product Center, version 5.2 (5724-I68), and to all subsequent releases and modifications until otherwise indicated in new editions.
Copyright International Business
Machines Corporations 2005. All rights reserved.
US Government Users Restricted Rights-Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
3.0 Known Issues and limitations
The main goals for this release include the implementation of the following:
Facilitate WebSphere Portal Server and WebSphere Commerce Server integration with WebSphere Product Center. The Web Services framework enhanced to facilitate integration with WebSphere Portal Server. (Limitation of Portal/Commerce Integration to English-only locale)
Enhance the security framework and capability of WebSphere Product Center for LDAP Authentication while still maintaining existing security framework. Currently, WebSphere Product Center is certified to integrate LDAP for IBM Tivoli Directory Server Version 5.2 with WebSphere Product Center 5.2.
Provide Spell Checking functionality in Content Authoring Screens for String Type Attributes
Replacement of XALAN & XERCES with IBM authorized packages
Support JDK 1.4.2 for development environments
Support JDK 1.4.2 and JRE 1.4.2 for WebSphere Product Center deployment
Support for command line job invoker
Support for localization of the user interface for IBM standard Group 1 languages
Support for additional hardware and software stacks
Installer executable to for multiple platforms. The installer can be run using a graphical interface or in silent mode. Refer to the "WebSphere Product Center: Installation Guide" for more information
Added new and updated scripting operations to the scripting library
Included change requests that have been closed due to being fixed or non-issue along with limitations identified for this release
Migration Framework for 4.2.x to 5.2 (Limitation of Migration from 4.2.x to 5.2 to English-only locale)
For this release, the following platform stacks are supported (* Primary stacks):
AIX 5L 5.2
* WebSphere Application Server Network Deployment 5.1.1/DB2 II 8.2
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
AIX 5L 5.3
WebSphere Application Server Network Deployment 5.1.1/DB2 II 8.2
Linux/Red Hat Advance Server 3.0 Update 3
WebSphere Application Server Network Deployment 5.1.1/DB2 II 8.2
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
* BEA WebLogic 8.1 Service Pack 3 Service Pack 2/Oracle 9.2.0.5
HP UX 11i
BEA WebLogic 8.1 Service Pack 3 Service Pack 2/Oracle 9.2.0.5
SPARC Solaris 9
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
BEA WebLogic 8.1 Service Pack 3 Service Pack 2/Oracle 9.2.0.5
1.2.1 Software and hardware server requirements
Note: The information in this section is subject to change. Prior to implementation, please consult your WebSphere Product Center representative.
Software Hardware The software requirements for WebSphere Product Center depend on which of the elements of the product components are being used and whether they are used singularly or in combination on a particular server. Dedicated servers are recommended for the database.
Bundled Products
The following software products are bundled with WebSphere Product Center 5.2:
Note: For WebSphere Application Server Network Deployment 5.1.1 and DB2 II 8.2 Advanced Edition, a limited use license is included with WebSphere Product Center.
Recommendations for hardware requirements are supplied for guidance only. This section lists the minimum hardware requirements for WebSphere Product Center. However, the actual requirements for your system may be greater, depending on the complexity of your specific WebSphere Product Center environment, throughput, and data object size. The following information is for the WebSphere Product Center system only. If you run other applications on the same system, make appropriate adjustments.
Additional server requirements:
- Additional CPUs may be required based on capacity requirements
- Additional memory may be required based on capacity requirements
- Additional servers for added capacity and/or redundancy
- Multi-server installations require network attached shared storage
AIX 5L 5.2
- (Primary Stack) WebSphere Application Server Network Deployment 5.1.1/DB2 II 8.2
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
(Primary Stack) WebSphere Application Server Network Deployment 5.1.1/DB2 II 8.2
The software in this primary stack lists the software products that are part of the IBM WebSphere Product Center offering.
Software Hardware Application Server
- WebSphere Application Server Network Deployment 5.1.1
- AIX 5L 5.2 (32 & 64 bit)
- IBM HTTP Server 2.0
- Server Type – IBM p630 Model 6C4
- Processor – 4 x 64-bit POWER4+ 1.45 GHz
- Memory – 8 GB
- Disk Sub-System – 144 GB SCSI
Database Server
- DB2 II 8.2 Advanced Edition
- AIX 5L 5.2
- Server Type – IBM p630 Model 6C4, PE2650
- Processor – 4 x 64-bit POWER4+ 1.45 GHz
- Memory – 8 GB
- Disk Sub-System – 420 GB SCSI
Additional Software Required software based on needed function:
- WebSphere MQ Series V5.3.0.2 (1)
- WebSphere Business Integration Adapter for WebSphere MQ V2.7.0 (1, 2)
- WebSphere Business Integration Adapter Framework V2.6.0 (1, 2)
(1) A limited use license is included with WebSphere Product Center
(2) Required when integrating with a process hub
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
Software Hardware Application Server
- WebSphere Application Server Network Deployment 5.1.1
- AIX 5L 5.2
- IBM HTTP Server 2.0
- IBM JDK bundled with WebSphere Application Server Network Deployment 5.1.1
- Server Type – IBM p630 Model 6C4
- Processor – 4 x 64-bit POWER4+ 1.45 GHz
- Memory – 8 GB
- Disk Sub-System – 144 GB SCSI
Database Server
- Oracle 9.2.0.5 Enterprise Edition
- AIX 5L 5.2
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
AIX 5L 5.3
Only one stack is currently supported on AIX 5L 5.3.
WebSphere Application Server Network Deployment 5.1.1/DB2 II 8.2
Software Hardware Application Server
- WebSphere Application Server Network Deployment 5.1.1
- AIX 5L 5.3 (32 & 64 bit)
- IBM HTTP Server 2.0
- Server Type – IBM p630 Model 6C4
- Processor – 4 x 64-bit POWER4+ 1.45 GHz
- Memory – 8 GB
- Disk Sub-System – 144 GB SCSI
Database Server
- DB2 II 8.2 Advanced Edition
- AIX 5L 5.3
- Server Type – IBM p630 Model 6C4, PE2650
- Processor – 4 x 64-bit POWER4+ 1.45 GHz
- Memory – 8 GB
- Disk Sub-System – 420 GB SCSI
Linux
WebSphere Application Server Network Deployment 5.1.1/DB2 II 8.2
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
BEA WebLogic 8.1 Service Pack 3/Oracle 9.2.0.5
WebSphere Application Server Network Deployment 5.1.1/DB2 II 8.2
Software Hardware Application Server
- WebSphere Application Server Network Deployment 5.1.1
- IBM HTTP Server 2.0
- Red Hat Enterprise Linux AS 3.0
- IBM JDK bundled with WebSphere Application Server Network Deployment 5.1.1
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
Database Server
- DB2 II 8.2
- Red Hat Enterprise Linux AS 3.0
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
Software Hardware Application Server
- WebSphere Application Server Network Deployment 5.1.1
- IBM HTTP Server 2.0
- Red Hat Enterprise Linux AS 3.0
- IBM JDK bundled with WebSphere Application Server Network Deployment
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
Database Server
- Oracle 9.2.0.5 Enterprise Edition
- Red Hat Enterprise Linux AS 3.0
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
BEA WebLogic 8.1 Service Pack 3/Oracle 9.2.0.5
Software Hardware Application Server
- WebLogic Server 7.0
- Apache HTTP Server 2.0
- Red Hat Enterprise Linux AS 3.0
- WebLogic JDK bundled with WebLogic Server 8.1
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
Database Server
- Oracle 9.2.0.5 Enterprise Edition
- Red Hat Enterprise Linux AS 3.0
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
HP-UX
BEA WebLogic 8.1 Service Pack 2/Oracle 9.2.0.5
BEA WebLogic 8.1 Service Pack 3/Oracle 9.2.0.5
Software Hardware Application Server
- WebLogic Server 8.1
- Apache HTTP Server 2.0
- HP/UX 11i
- WebLogic JDK bundled with WebLogic Server 8.1
- Server Type: HP RP 4440
- Processor: 2 CPUs
- Memory: 4 GB
- Disk Sub-System: HP MSA 1000
Database Server
- Oracle 9.2.0.5 Enterprise Edition
- HP/UX 11i
- Server Type: HP RP 4440
- Processor: 2 CPUs
- Memory: 4 GB
- Disk Sub-System: HP MSA 1000
Solaris
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
BEA WebLogic 8.1 Service Pack 2 Service Pack 3/Oracle 9.2.0.5
WebSphere Application Server Network Deployment 5.1.1/Oracle 9.2.0.5
Software Hardware Application Server
- WebSphere Application Server Network Deployment 5.1.1
- IBM HTTP Server 2.0
- Solaris 9
- IBM JDK bundled with WebSphere Application Server Network Deployment
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
Database Server
- Oracle 9.2.0.5 Enterprise Edition
- Solaris 9
- Server Type: Intel compatible
- Processor: Dual Intel, XEON 2.8 GHz
- Memory: 6 GB
- Disk Sub-System: 365 GB 10K RPM SCSI Driver
BEA WebLogic 8.1 Service Pack 3/Oracle 9.2.0.5
Software Hardware Application Server
- WebLogic Server 8.1
- Apache HTTP Server 2.0
- Solaris 9
- WebLogic JDK bundled with WebLogic Server 8.1
- Server Type: HP RP 4440
- Processor: 2 CPUs
- Memory: 4 GB
- Disk Sub-System: HP MSA 1000
Database Server
- Oracle 9.2.0.5 Enterprise Edition
- Solaris 9
- Server Type: HP RP 4440
- Processor: 2 CPUs
- Memory: 4 GB
- Disk Sub-System: HP MSA 1000
1.2.2 Hardware and software requirements for client access to WebSphere Product Center
The following are the minimum system requirements recommended for client access to WebSphere Product Center:
Software Hardware
- Microsoft Windows 2000 Professional Service Pack 3 or Microsoft Windows XP Professional Service Pack 1
- Browser: Microsoft Internet Explorer Version 6.0 Service Pack 1
- Processor: Intel-based system with a Pentium III with minimum processor speed of 750 MHz
- Memory: 256 MB
This release supports IBM standard National Language Support Enablement for the entire WebSphere Product Center platform. The IBM standard Group 1 languages include (Chinese Simplified, Chinese Traditional, Japanese, Italian, Korean, French, German, Italian, Spanish, and Portuguese Brazilian).
A limitation and workaround has been provided for migrating application instances from one local to another (Locale A to Locale B). Refer to section 4.0 for additional information.
Limitation of Migration from 4.2.x to 5.2 to English-only locale.
Although locale specific data can be exported from versions 4.2.0.x into version 5.2, this releasedoes not include NLS (National Language Support) support for 4.2.0.x.
No printed publications are shipped with this product. Translated product documentation can be obtained from the IBM internet site (http://www-306.ibm.com/software/integration/wpc/library/documentation.html ). Planned availability for translated documents on April 22, 2005.
The following documents are available for this release:
WebSphere Product Center: User Guide
WebSphere Product Center: Overview
WebSphere Product Center: Installation Guide
WebSphere Product Center: Support Guide
WebSphere Product Center: Scripting Reference Guide
WebSphere Product Center: Release Notes for Version 5.2
WebSphere Product Center: Portal Enablement
WebSphere Product Center: WebSphere Commerce Integration
This section provides a summary of all new features implemented in this release. Please refer to the product documentation for additional detailed information.
2.1.1. WebSphere Commerce and Portal Server Integration
Both WebSphere Portal Server and WebSphere Commerce Server can be facilitated to integrate with WebSphere Product Center. The WebSphere Product Center Web Services framework has been enhanced to properly integrate with WebSphere Portal Server.
Note: Limitation of Portal/Commerce Integration to English-only locale
Enhanced integration with WebSphere Commerce:
Product Information authoring capabilities, such as for aggregating, enriching, maintaining, and publishing product attributes to various commerce systems have previously been available in WebSphere Product Center. In the WebSphere Product Center 5.2 release, enhanced integration capabilities are provided to accelerate the integration with WebSphere Commerce. A WebSphere Commerce data model template is being packaged as part of WebSphere Product Center, to allow for quick mapping of product attributes and taxonomies to WebSphere Commerce storefronts. User interfaces are provided to define common WebSphere Commerce objects types such as products, bundles, and skus. Product content movement (export) capabilities for moving product information from WebSphere Product Center to WebSphere Commerce in complete load and delta modes are provided for a variety of scenarios, such as creating a new WebSphere Commerce storefront, or publishing new or modified product content to a WebSphere Commerce storefront. These capabilities can be further configured in a customer implementation. Integrated preview capabilities offer in-context WebSphere Commerce storefront previews during the authoring time. For version 5.2, this feature is enabled for "U. S. English" (or en_US) locale only.
Commerce server integration includes:
Basic WebSphere Product Center data modeling that includes representations for the Commerce catalog objects such as Categories, Product, Product Groups, SKUs, etc.
Export full catalog data as well as delta changes to Commerce application
Preview of an item in WebSphere Product Center by clicking a preview menu option, with Commerce screens, and navigate in the Commerce application to see all the related commerce catalog objects
Portal solution enablement:
WebSphere Product Center V5.2 offers enhanced support to create a portal interface to your WebSphere Product Center implementation. This functionality lets you establish a portal interface to provide strategic interactions with your trading partners, employees or customers that can extend to thousands of users. The ability to create a portal solution as part of your WebSphere Product Center environment is facilitated by inclusion of Web services-based APIs that create the ability to access and write item information via a portal to WebSphere Product Center. This release also allows you to leverage portal user interface personalization capabilities, as well as leveraging WebSphere Product Center's workflow to support the item enrichment process. Furthermore, LDAP integration is included in this release, enhancing your ability to authenticate users and define role-based access for parties accessing WebSphere Product Center via a portal. For version 5.2, this feature is enabled for "U. S. English" (or en_US) locale only.
Portal server integration to include the ability to perform specified operations from Portal server:
Add item in WebSphere Product Center
Modify item in WebSphere Product Center
Delete item in WebSphere Product Center
Search items based on GTIN (Global Trade Identification Number), SKU (Stock Keeping Unit), GLN (Global Location Number)
Support selections
CSV (Comma Separated Value) upload and download
Mass updates
2.1.2 Web services framework enhancements
WebSphere Product Center can return an XML message as a response to a Web services request in addition to text strings. With this functionality, WebSphere Product Center can be more easily integrated with order management, merchandising and other systems that query WebSphere Product Center via Web services for item, location, customer, and supplier information.
With the design to integrate WebSphere Portal Server, it was required to enhance the Web Services capabilities to include support for:
Sending attachments over Web Services
Providing asynchronous and synchronous Web Service calls
Providing support for complex types
Therefore, this release includes the following enhancement to the Web Services framework:
Improved Web Services Infrastructure
WebSphere Product Center module portlets are accessed from outside the firewall, therefore security was built into the APIs for access from outside the firewall. Previously, the SOAP API framework that was available within WebSphere Product Center allowed for behind the firewall access.Improved Web Services Capabilities
Web Services output is now an XML document instead of one string that is packed with all the data. In the previous implementation of Web Services, all the data is returned in the form of one string, which made it is a cumbersome to parse the string, especially in the cases where there are a lot of attributes involved. Web Services now has the capabilities to request data from other applications through Web Services infrastructure.XML Parser wrapper enhancements
The XML infrastructure within WebSphere Product Center was not namespace aware. In this release, XMLUtils.java was enhanced to support XML namespaces.Web Services Console enhancements
To support output of an XML document, the Web Services infrastructure has been enhanced to support Document Literal style web services in addition to existing RPC/Encoded style. Therefore the Web Services GUI now has two radio buttons that indicate the style to be used in the WSDL (Web Services Description Language).2.1.3 LDAP integration
The security framework and capability of WebSphere Product Center has been enhanced for LDAP (Lightweight Directory Access Protocol) Authentication while maintaining the pre-existing security framework.
Given the complexity involved in using third party LDAP capabilities for Authorization, the existing authorization infrastructure available within WebSphere Product Center 5.2 is used to authorize the LDAP users whereas the authentication is in the realm of LDAP. The entitlements of LDAP users and roles into WebSphere Product Center are both runtime as well as based on user/system invoked script operation. The LDAP user in the WebSphere Product Center is differentiated using the LDAP Flag.
LDAP Integration is certified only with IBM Tivoli Directory Server 5.1
2.1.4 Spell Check functionality
Provide Spell Checking functionality in Content Authoring Screens for String Type Attributes
The Spell Checker functionality is not bundled with WebSphere Product Center, as the framework used is a third party product from WinterTree called "Sentry Spell Checking Engine". To overcome this a plug-in type interface, which uses java reflection, APIs is provided. The method invocations and classes loading at runtime are configured using plugins.xml and plugins.properties file. Currently, Sentry supports only the English dictionary with dialects of American, Canadian, and UK English. Therefore, this release includes spell checking functionality for English only. To implement spell checking functionality, the purchase of the third party product "Sentry Spell Checking Engine"
The spell checker functionality in WebSphere Product Center V5.2 supports English only text.
2.1.5 Command line job interface
Customers deploying WebSphere Product Center often have system level scheduling tools such as IBM Tivoli Workload Scheduler. WebSphere Product Center version 5.2 adds command line interface to WebSphere Product Center scheduler, so that customers can utilize the system level scheduling tools to schedule frequent tasks such as import of data into Product Center, processing of data as well as export of data from WebSphere Product Center.
For this release, the command line Third Party Scheduler integration is certified with IBM Tivoli Workload Scheduler.
Limitations: In terms of NLS (National Language Support), WebSphere Product Center installations using "US English" as the language on the server will be able to use this feature. The rest will be blocked or not be fully supported. Messages will be in English in the output console. The message displayed in the output console from the scheduler is used for information purpose only in most customer implementations; therefore, there is very little user impact due to lack of support for Non-US English locales for this version. It is planned for all other Group 1 locales to to be supported in a future Fix Pack or major release.
2.1.6 Migration framework from 4.2.x to 5.2
Customers deployed on Trigo Product Center 4.2.X releases can now quickly migrate to the WebSphere Product Center 5.2 release by using the import/export tool capabilities. These tools are capable of migrating an entire environment, portions of product data, or the data model from the Trigo Product Center 4.2.X environments to the WebSphere Product Center 5.2 release. Using the export tool available in the Trigo Product Center 4.2.X releases an export file can be generated which can then be imported into the the WebSphere Product Center 5.2 environment using the import tool available in the WebSphere Product Center 5.2 release. These tools dramatically reduce the cost of migration and the time it takes to migrate from Trigo Product Center 4.2.X releases to the WebSphere Product Center 5.2 release.
2.1.7 Replace XALAN and XERCES
Replacement of XALAN and XERCES with IBM authorized packages.
XALAN (for Java) is an XSLT processor for transforming XML documents into HTML, text, or other XML document types and XERCES (for Java) is a XML Parser from the Apache XML Project. Previously, these were bundled with WebSphere Product Center and due to the fact that they are derived from an Open Source entity, they were replaced with IBM authorized packages.
The IBM authorized equivalent of XERCES (for Java) is XML4J and the IBM authorized equivalent of XALAN (for Java) is XSLT4J. IBM JDK 1.4.2 comes with a combined bundle of XML4J and XSLT4J in a jar called xml.jar.
2.1.8 JDK 1.4.2 Support
Support for JDK 1.4.2 has been implemented for the following purposes:
JDK 1.4.2 used for development environments
JDK 1.4.2 and JRE 1.4.2 used for WebSphere Product Center deployment
Currently, new or enhanced features of JDK 1.4.2 over JDK 1.3.1 will not be leveraged
2.2.1 Updated script operations
This document provides a list of script operations that have been modified in WebSphere Product Center 5.2 from version 5.1.
Note: The script operations listed in this document are for reference only and are subject to change. Refer to the Script Sandbox in the WebSphere Product Center product for more accurate information.
Each modified script operation listed in the following sections is preceded with one of the acronyms listed in the table below, which represent the type of change that was made.
D
Deprecated
PU
Prototype updated
DU
Description updated
For example
Catalog
Input Output
PU/DU logActionableMessage
- Prototype: Integer logActionableMessage(String type, String action, String comment, IMessage msg, String state)
- Description: Logs a message in the alerts console for a message "msg". the Actionable "type" is primary heading or category under which an actionable is classified. Actionable "action" is known as the actionable topic. The topic is essentially a more specific version of the actionable type, it can be Accept or Reject. Actionable "comment" is information about the actionable. Actionable "state" sets the priority level of this actionable, the level can be set to either "INF" for informational, "ACT" for actionable or "ERR" for any error. It returns a unique ID for the message logged.
DU getFtp
- Description: Use to get a file via FTP. The seventh parameter set where WebSphere Product Center will store the retrieved file. The eighth and the ninth paramters together are optional. The eigth parameter gets the FTP Operation Status and the ninth paramter ensures that the FTP operations are logged. Returns the result as true/false if the eighth and the ninth are not specified otherwise a HashMap is returned. If a true/false is returned, it indicates if the ftp was a success/failure. If the size of the retrieved file is not the same as the size of the remote file the status is set to false. If a HashMap is returned, the first paramater is the true/false which indicates success/failure, the second paramater is the message string of the FTP Operation Status and the third parameter is the FTP Operation error code
Web Services
PU/DU createWebService
- Prototype: WebService createWebService(String name, String desc, String wsdlDocPath, String protocol, String style, String implScriptPath, Boolean storeIncoming, Boolean storeOutgoing, Boolean deployed [,String style])])
- Description: Creates a new web service with the given parameters. To save and deploy the service x(if DEPLOYED is true), call saveWebService(). NAME is the name of the service. DESC is the description of the service. WSDLDOCPATH is the doc path at which the WSDL is stored. PROTOCOL is the protocol. Currently "SOAP_HTTP" is the only supported protocol. IMPLSCRIPTPATH is the doc path of the service implementation script. It is the callers responsibility to ensure that WSDLDOCPATH and IMPLSCRIPTPATH do not cause the documents for any other web service to be overwritten. STOREINCOMING determines whether incoming requests are stored. STOREOUTGOING determines whether outgoing request are stored. DEPLOYED determines whether the service will be deployed. STYLE is the message style. Currently, RPC_ENCODED and DOCUMENT_LITERAL are supported. If no value is provided RPC_ENCODED is taken as the default style. If a web service with the name of NAME already exists, throws an AustinException.
N getStyle
- Prototype: String WebService::getStyle()
- Description: Returns the style for this web service
N setStyle
- Prototype: void WebService::setStyle(String style)
- Description: Sets the style of the given Web Service.
Catalog
DU getCurrentCtgViewName
Description: Returns name of current catalog view (only in Entry Preview scripts). Returns an empty string in scripts other than Entry Preview scripts.For other scripts use Catalog::getDefaultCtgViewName() to get the view name.
Entry
N previewEntryAttrib
- Prototype: String Entry::previewEntryAttrib(String sAttribPath)
- Description: Returns the preview string for displaying entry attribute specified by attribute path.
Locale
N getCompanyLocales
- Prototype: Locale[] getCompanyLocales()
- Description: Returns the locales that are part of the current company.
IMutable Spec
DU importXSD
- Description: Imports a XML Schema Definition file (.xsd) to a WPC Spec, using the given parameters.
DU importXML
- Description: Imports a XML file to a WPC Spec.
DU exportXSD
- Description: Exports a WPC Spec to a String representing the contents of XML Schema Definition.
DU exportXML
- Description: Exports a WPC Spec to a String representing a XML file.
Export environment
DU new$EnvObjectList
- Description: Returns a container for the WPC objects to be exported. This class is used to add and retrieve the objects to be exported.
DU setTypeToExport
- Description: Sets the object type to be exported. List of acceptable values for sObjectType are:
"ACG",
"ALERT",
"ATTRIBUTE_COLS",
"CATALOG",
"CATALOG_CONTENT",
"CATALOG_VIEW",
"COLLABORATION_AREA",
"COLLABORATION_AREA_CONTENT",
"COMPANY_ATTRIBUTES",
"CONTAINER_ACCESSPRV",
"DATASOURCE",
"DESTINATION_SPEC",
"DISTRIBUTION",
"DISTRIBUTION_GROUP",
"DOC_STORE",
"EXPORTS",
"FEEDS",
"FILE_SPEC",
"HIERARCHY",
"HIERARCHY_CONTENT",
"HIERARCHY_MAPS",
"HIERARCHY_VIEW",
"INHERITANCE_RULES",
"ITEM_CATEGORY_MAPS",
"JOBS",
"LOOKUP_TABLE",
"LOOKUP_TABLE_CONTENT",
"LOOKUP_TABLE_SPEC",
"MAPS",
"MY_SETTINGS",
"PRIMARY_SPEC",
"QUEUE",
"REPORTS",
"ROLES",
"SELECTION",
"SCRIPT_INPUT_SPEC",
"SECONDARY_SPEC",
"SPEC",
"SUB_SPEC",
"USERS",
"WEBSERVICE",
"WORKFLOW"DU addObjectByNameToExport
- Description: Sets the entity to be exported by specifying the entity name as an argument. sObjectType is optional. In case of Catalog and Hierarchy Content export, this operation is used to specify the attribute collection associated with the object. In case of DocStore partial export, this operation is used to specify the DocStore path. List of acceptable values for sObjectType are:
"ACG",
"ALERT",
"ATTRIBUTE_COLS",
"CATALOG",
"CATALOG_CONTENT",
"CATALOG_VIEW",
"COLLABORATION_AREA",
"COLLABORATION_AREA_CONTENT",
"COMPANY_ATTRIBUTES",
"CONTAINER_ACCESSPRV",
"DATASOURCE",
"DESTINATION_SPEC",
"DISTRIBUTION",
"DISTRIBUTION_GROUP",
"DOC_STORE",
"EXPORTS",
"FEEDS",
"FILE_SPEC",
"HIERARCHY",
"HIERARCHY_CONTENT",
"HIERARCHY_MAPS",
"HIERARCHY_VIEW",
"INHERITANCE_RULES",
"ITEM_CATEGORY_MAPS",
"JOBS",
"LOOKUP_TABLE",
"LOOKUP_TABLE_CONTENT",
"LOOKUP_TABLE_SPEC",
"MAPS",
"MY_SETTINGS",
"PRIMARY_SPEC",
"QUEUE",
"REPORTS",
"ROLES",
"SELECTION",
"SCRIPT_INPUT_SPEC",
"SECONDARY_SPEC",
"SPEC",
"SUB_SPEC",
"USERS",
"WEBSERVICE",
"WORKFLOW"DU addAllObjectsToExport
- Description: Notifies that all the entities of specific object type be exported. sObjectType is optional. List of acceptable values for sObjectType are:
"ACG",
"ALERT",
"ATTRIBUTE_COLS",
"CATALOG",
"CATALOG_CONTENT",
"CATALOG_VIEW",
"COLLABORATION_AREA",
"COLLABORATION_AREA_CONTENT",
"COMPANY_ATTRIBUTES",
"CONTAINER_ACCESSPRV",
"DATASOURCE",
"DESTINATION_SPEC",
"DISTRIBUTION",
"DISTRIBUTION_GROUP",
"DOC_STORE",
"EXPORTS",
"FEEDS",
"FILE_SPEC",
"HIERARCHY",
"HIERARCHY_CONTENT",
"HIERARCHY_MAPS",
"HIERARCHY_VIEW",
"INHERITANCE_RULES",
"ITEM_CATEGORY_MAPS",
"JOBS",
"LOOKUP_TABLE",
"LOOKUP_TABLE_CONTENT",
"LOOKUP_TABLE_SPEC",
"MAPS",
"MY_SETTINGS",
"PRIMARY_SPEC",
"QUEUE",
"REPORTS",
"ROLES",
"SELECTION",
"SCRIPT_INPUT_SPEC",
"SECONDARY_SPEC",
"SPEC",
"SUB_SPEC",
"USERS",
"WEBSERVICE",
"WORKFLOW"DU exportEnv
- Description: Exports the WPC objects specified in envObjList at the specified DocStore path. sDocFilePath is the filepath of the zip file that will be exported into the document store - returns the log as a string.
Reader
N getLdapUserInfo
- Prototype: reader getLdapUserInfo(String username, [HashMap LdapEnvConf])
- Description: Returns a reader to the LDAP user's ldap credentials. If LdapEnvConf is not given it takes the Environment values from the default conf file
N getAllLdapUsersInfo
- Prototype: reader getAllLdapUsersInfo([HashMap LdapEnvConf])
- Description: Returns a reader to all LDAP user's credentials. If LdapEnvConf is not given it takes the Environment values from the default conf file
Basic: Script Object
N invokeSoapServerForDocLit
- Prototype: Object invokeSoapServerForDocLit(String sURL, String xmlRequestMsg)
- Description: Invoke a soap server for Document-Literal based web services. SURL is the URL of the service. XMLREQUESTMSG is a string containing the request message in XML format.
Basic: Date
PU/DU new$Date
- Prototype: new Date(String sFormat, String sDate[,Locale locale)
- Description: Builds a Date object from a String given a date format, if the locale is supplied that locale will be used to apply the given format, else en_US will be used
Docstore: XML Document
DU validateXML
- Description: Validates an XmlDocument from a docstore Doc instance. Returns "Success" if its a valid XML Document. Returns "Document not found" if the XML Document not found in DocStore. Returns "Document is empty" if the XML Document is empty. Returns "Fatal Parsing Error" concatenated with the error description for a non-XML Document. Returns "Error" for any other error.
Input/Output: XML Node
DU getXMLNodeValue
- Prototype: String XMLNode::getXMLNodeValue(String nodePath [, Boolean bRequired])
- Description: Returns the value of the current XMLNode. Default value of bRequired is false. It is set to throw AustinException
Security: User
PU/DU createUser
- Prototype: User ::createUser(String username, String firstname, String lastname, String email, Boolean enabled, String password, HashMap roles, Category organization [, Boolean encryptPassword, Boolean enableLdap])
- Description: Creates an user with the specified parameters. Enabled, Password, Roles, and organization parameters are required. encryptPassword exists for the purpose of migrating environments so that encrypted passwords exported from one environment can be loaded into another environment without encrypting them again and that there is no possibility of knowing what the password was. EnableLdap marks the user as LDAP enabled.
N getUserLdapEnabled
- Prototype: boolean User::getUserEnabled()
- Description: Returns if the User is a LDAP user or not.
N setUserLdapEnabled
- Prototype: void User::setUserLdapEnabled(boolean)
- Description: Sets the user as a LDAP user.
System Admin: Logger
N getLogger
- Prototype: Logger getLogger(String s)
- Description: Returns a logger (loggers are in the system log directory with the given name
N loggerDebug
- Prototype: void Logger::loggerDebug(String s)
- Description: Writes to this logger
N loggerInfo
- Prototype: void Logger::loggerInfo(String s)
- Description: Write s to this logger
N loggerWarn
- Prototype: void Logger::loggerWarn(String s)
- Description: Write s to this logger
N loggerError
- Prototype: void Logger::loggerError(String s)
- Description: Write s to this logger
N loggerFatal
- Prototype: void Logger::loggerFatal(String s)
- Description: Write s to this logger
The following items have been addressed for this release.
Tracking number
Description 16189 getDateField(MONTH) returns a incorrect value 16489 Acceptable values available for sObjectType are not acceptable for Selections,WBS,Queues,Dist Grps and Alerts 16559 Incorrect locale description in My Settings page. This was identified to be a permanent restriction as it relates to a Third party issue (JDK) 16578 Migration - Distribution Groups are not exported 16713 "Default value" is not saved in the Spec Console 16714 LDAP: When cn and Uid are different on the LDAP server , user cannot login to WebSphere Product Center 16723 FTP distribution not working. Could not reproduce 16724 Unable to retrieve the file from a FTP data source 16759 Invalid date output in catalog version summary 16839 Cannot import Arabia currency and number to collaboration area in workflow 16884 Some locale names are not showed in Arabic language when locale changed to Arabic(Egypt). This was identified to be a permanent restriction as it relates to a Third party issue (JDK) 16905 User is unable to save dates in the format yyyy-mm-dd hh:mm 16995 Available locales are hard coded in company attributes for G1 17036 Can not import objects depending on default values into WPC v5.2 company. For WPC 5.2, The Migration Framework is certified to work only when the server and the client is set on en_US locale (in 4.2.0.x). The migration frame work is not certified to work across locales or on any other locale apart from en_US.
17219 Customers critically misled about the date format displayed in Multi-Edit screen
The following table lists the known issues that are present in WebSphere Product Center 5.2. These known issues are being considered for resolution in a subsequent release.
Tracking number |
Description |
P9999 | Hierarchy Attributes page should have a 'Save' button and nothing should be committed on an individual field basis |
P9865 | Organization in the Left Pane should allow the deletion of a user *missing feature* |
P9861 | Hierarchy Attribute page should contain a way to setup a link to the catalog items *missing feature* |
P9576 | disableContainerProcessingOptions() is not working properly |
P15368 | wrong code page for readmes for DBCS |
P15094 | Multi-occurring attribute of a sub spec that is attached to a secondary spec does not work properly |
P15082 | Strings on the System Status panel are not translated |
P15076 | Merge Step needs manual intervention when an item/category is added in a general step |
P14935 | Not able to edit or browse directory name textbox |
P14906 | Unable to to export a spec when logged in as a user with defined access privileges to the docstore |
P14890 | Invoking a deployed service without a returned value is not working. |
P14682 | Maximum Occurring values in catalog to catalog inheritance are not getting inherited |
P14510 | No error messages are displayed when adding an item hierarchy or standalone spec to a category and then clicking the Create Spec or the Search button without specifying a value |
P14509 | An error message should display when adding an item hierarchy/standalone specs to a category and clicking the Select button without selecting a secondary spec |
P14315 | In the multi-edit data entry screen, an attribute of type "password" does not display the correct characters |
P14288 | symbol can not be displayed correctly in CSV preview page . |
P14270 | Inherit/Override buttons disappear when overriding an item with new values and saving it in a workflow step |
P14165 | Search attributes popup not refreshed |
P14088 | No return values in aggregate search while searching for -ve values |
P14047 | Cannot remove user from organization |
P14045 | Users who are non-administrators of the Collaboration area cannot check out items or categories |
P14003 | No links for Sorting of search results of Attribute Search |
P14002 | Enter key feature not working in search attributes popup window |
P13975 | My Setting value "Initial display of multi-valued items" is not working properly |
P13841 | Imports should fail if the imported file type does not match what has been defined in the Specs Console |
P13817 | All Values are not getting inherited for Maximum Occurrence Attributes |
P13805 | Script abort_local.sh can not work correctly on HP-UX platform |
P13803 | Duplicate spec names are allowed without any error message |
P13770 | Can not specify '> for Catalog Display Attribute . |
P13764 | error on new CategoryTree() Script function with optionalArgs parameter. |
P13650 | Export Alert,WorkFlow Alert not working in the Left pane. |
P13640 | An error does not display when adding a secondary spec with no value selected |
P13626 | Adding a unsupported characters in the data entry screen does not throw an error |
P13608 | Shortcut keys Ctrl+Alt+L and Ctrl+Alt+D are not working properly in the main page |
P13533 | The title of the exit confirmation panel is truncated when running the installer |
P13522 | error on createExport() function with the same export name. |
P13518 | Lookup table -- Error occur : delete lookup table . |
P13514 | Exact Match / NOT predicate not working in Rich Search for Hierarchy |
P13490 | Button Menu not getting displayed completely in Catalog / Hierarchy Console |
P13483 | Last visited module is not updated in the left pane. |
P13456 | Extact Match / NOT predicate not working in Rich Search |
P13418 | No 'default value' and 'lookup table' options are available when creating a spec |
P13412 | Turning off the attributes privilege under catalog disables available options in the Left Pane |
P13347 | In My Task List page "Delete" Button not working |
P13304 | When creating a files spec with no file type and ignore header attributes, an error should return and the spec should not be created |
P13190 | sorting Ascending/ Descending not working in Catalog Console |
P13061 | On job console, Description "exact match" does not work |
P13056 | Space character shouldn't be allowed to be Tab view name |
P13047 | job description exact match not working properly |
P13037 | deleting operation error for pattern (regular expression) of an attribute |
P13029 | Tool tip messages are not displayed correctly when clicking "DELETE" button on specs console |
P12978 | Alert message should display in current page |
P12975 | You can specify "1.w" for range of Bulk Edit |
P12943 | Can not view the .jpg file named with localized language letters |
P12941 | Multiple edit page treats space character inconsistently with Single edit page |
P12922 | There lack message when delete spec from Spec Console. |
P12801 | Unexpected result when using the setAttribute script operation |
P12709 | In My Settings, setting the "Display spec attribute as" value to "popup" does not produce the expected result |
P12365 | Column names are not displayed correctly when the value of My Settings "Enable persisting of lookup table sort columns" is set to "Yes" |
P12325 | Importing XSD Spec reports parsing error |
P12319 | reportAllTableIndexes() causes out of memory |
P12314 | Removing attribute collection from the view will still keep it for the Tabs |
P12281 | Date type attribute doesn't display default values set in the spec's default field |
P12231 | Cannot change ACG for organization hierarchy |
P12228 | Catalog to Catalog Export is not setting the value for the time part of the date field |
P12214 | "Catalog Spec" should be replaced with "Primary Spec" in the drop down list of Specs Map console. |
P12156 | Multiple Edit - If there are 2 specs that reuse the same sub spec specified in the attribute collection, then the catalog view will not display these sub spec attributes |
P12141 | replaceString() should support regex |
P12133 | getLkpId is redundant with getContainerId |
P12091 | Can add hierarchy nodes to collab area if sku is not editable anywhere in the workflow |
P12076 | Edit Spec – It is possible to associate regular spec nodes to inheritance ones |
P12002 | Display Inheritance paths - If there are 2 or more different hierarchies, then only 1 will have '(H)' displayed next to name |
P11990 | getRoles() and getRolesForCompany() can be combined into one script operation |
P11989 | getRolesForCompany() should return empty array in case of bad name |
P11982 | Spelling correction in the error message of import "occured" >>"occurred" |
P11980 | UI Look & Feel of the Application should be more consistent throughout |
P11971 | Needs operation for setUserOrganizations() |
P11963 | RE::match() should return empty array instead of null in case of not matching |
P11961 | austin.properties has redundant mq/jms parameters |
P11959 | async wfl ops should take in a boolean optional arg for waiting or not |
P11958 | Value Rule Editor Screen title is incorrect |
P11906 | Click on ">>“ to expand the "User Search" results for an Organization Hierarchy should not throw any error message |
P11896 | Checked out attributes listing is out of order in Tool Tip for workflow history |
P11885 | Need white space between comments given by multiple “And Approvers” in workflow |
P11859 | Fetched files are NOT deleted from doc store when a Job is deleted |
P11854 | The user should be able to save the basic search results for a lookuptable in Search Catalog console when a lookup table is selected in the dropdown list in the Select Catalog dropdown list |
P11832 | Save button is gone after clicking Save on the Report page |
P11822 | exportEnv() cannot export "ITEM_CATEGORY_MAPS" |
P11775 | Click on the "Exit" button on any mapping details page, the page does not close |
P11767 | Create a Catalog View with the name same as the already existing one. System displays "Error Creating Catalog view message". Better message would be "View with the given name already exists” |
P11762 | Rich Search screen - Inherited Values are not identified |
P11761 | Value entered for Password (editable) field appears in the decrypted form on Multi Edit screen and encrypted form on Single Edit screen |
P11726 | Left Pane - Font Size settings are not reflected in the left pane |
P11723 | Needs updating - migration script for tque_mqu_queue |
P11720 | Short cut keys are not working for a few options on the Single Edit page |
P11719 | The search criteria is lost when a sort is done on a lookup table column in the lookup popup window |
P11708 | Adding a subspec node or assigning a subspec to a primary spec, having same attribute names as that of a subspec does not add the common attribute names from sub spec |
P11707 | User can make a Primary key non-persistent, this should not be allowed |
P11705 | Trying to add appserver status without an empty name gives “page cannot be displayed” error |
P11703 | Error Message not displayed while deleting the last node in any spec except primary spec. An exception is thrown in the log files |
P11673 | dropEntries() should be renamed as removeEntries() |
P11650 | If number of bytes for a number attribute exceed 16 bytes , then it does not allow to save the attributes |
P11642 | Mandatory fields need to be disabled for table display properties in the Job Console |
P11613 | The user can add Items having a primary key with more than one character though the maximum length of primary key is set to "1" |
P11576 | After creating new User, the User Console should be displayed |
P11575 | Creating a user which already exists does not have correct flow after error message |
P11551 | Inconsistency in the use of a few script operation names |
P11273 | jmsGetMsgProperties() always returns an empty array |
P11155 | Edit Item Inheritance - Inheritance rule will not get values from a 3rd level source if another Attribute Collection is defined, which is not in 2nd level |
P11093 | Edit Inheritance Creation/Going back for inheritance is general instead of object specific |
P10995 | arrayreturntyped operations should return an empty array/set instead of null/exception |
17790 | Step name not displayed correctly in workflow (Japanese) |
17746 | Custom tool script does not execute correctly when name contains globalize characters |
17744 | French translation error during setup |
17726 | "WebLogic 7.0" showed in Product configuration panel in "Traditional Chinese", should be WebLogic 8.1 |
17715 | Installer does not support the "-console" flag |
17694 | Date format is different for single edit and mass edit /file Upload |
17691 | error "getMoniker method not implemented" |
17649 | Running interval can not be saved correctly in Scheduler |
17642 | Workflow reserve status rich search for checked out items not working |
17635 | not working if create a new category and do re-categorization of catalog object |
17586 | Report does not generate xml files after the catentry items are mass updated. |
17583 | Renaming and adding a new value at the same time to a product is not working properly |
17450 | Renaming a descriptive attribute is not working properly |
17448 | Add a defined attribute and cancel while saving, it still gets added to the skucatalog |
17355 | Left pane preferred search failing for display attribute search |
17322 | Wrong "drop" button name and hot key used |
17320 | Import of My Settings fails intermittently |
17305 | Deleting a defining attribute causes a duplicate value combination |
17253 | Search results are not displaying the ItemPspec/product description, Actual Image, Packaging, Security Code, Availability period, Top component product, current Thumbnail and Available Geography. |
17251 | Secondary Spec cannot be deleted from specs console |
17239 | Debug Report for an Import job displays incorrect messages |
17183 | Mnemonics in Spelling window |
17162 | Spell checking focus is not proper for incorrect words |
17122 | Tamil strings do not appear correctly in drop-downs |
17120 | Tamil characters do not appear correctly in the Hierarchy attributes pane |
17118 | Installer: Directory name on Destination panel is getting
un-editable after browse. Workaround: Click on the Browse button again, and specify your target directory |
17113 | "Spell Check" Button is not working properly with localized spec. |
17111 | Items summary with ACG is not working |
17109 | Able to edit items not having edit permission |
17094 | Date attributes not inherited correctly |
17080 | Datetime format should be localized |
17061 | Emailing items functionality is not implemented |
17058 | Bold fonts in wizards are inappropriate for Japanese |
17035 | Accumulation in Inheritance does not work, only works with multi-occurring groups |
17015 | Collaboration Area console does not display numbers correctly |
17012 | Cannot add user with Russian characters in username in ru_RU client |
17005 | Portal - Search criteria on 'DATE' field is not correct |
16964 | Workflow step names truncated on Collaboration Area Console |
16929 | Incorrect number (exceed defined precision) can be saved successfully in number enumeration |
16921 | Cannot attach file for product documentation when file name is in zh_CN locale |
16877 | User Flag is not getting disabled if user deleted from LDAP Server |
16869 | Can not display image in AIX5.3_WAS_DB2 (language : ja_JP) |
16867 | Space character should not be allowed to be export name in Japanese locale |
16849 | Uppercase French character in username causes LDAP authentication to fail |
16838 | Localized attributes having no dictionary are getting spell checked by English. |
16837 | Functionality "Add to Dictionary" is not working for paragraphs spell Check |
16835 | Values are lost on checking in items with overridden values |
16832 | Multi-edit 'auto populate' feature can cause inability to save items |
16829 | Incorrect UI behaviors in New Basic Selection/Edit Basic Selection |
16820 | Spurious error message appears when deleting import, try to delete and it says cannot delete |
16789 | Unable to reset/view the character delimiter on a file spec |
16780 | Opening XML file with WPC server window open crashes session |
16755 | Portal- File upload preview button opens another instance of portal |
16754 | Rich search, press "CLEAR" Try search again for "Primary Key". Not working |
16753 | "CLEAR" Button in rich search is not clearing data of "Primary Key" & "Path" attributes |
16741 | Changing the number of services displayed per page is not working |
16729 | Collaboration Console search for source container does not find hierarchy areas |
16720 | Migration - Export of Inheritance rules fails |
16710 | Catalog sort order incorrect for fr_FR locale |
16705 | Import fails using Multi-Char Character delimited file spec |
16632 | create_vhost.sh script is not correct, its giving error when running |
16616 | Japanese is not displayed correctly, the word separators in Japanese katakana turn into boxes in a dropdown list |
16573 | Migration - Export of Organization Hierarchies fails (Import is blocked) |
16556 | Migration - Import of a Lookup spec and Lookup table having a lookuptable attribute fails |
16479 | Rich search for Hierarchy Spec mapping - Spec Name "Is Empty" is not working |
16475 | Undo step for inherited values does not work |
16461 | Binary and Image files export scripts are not available |
16363 | Not able to import spec |
16324 | Scheduler does not report duplicate SKUs when running an item feed to a catalog with duplicate SKUs |
16705 | Import fails using Multi-Char Character delimited file spec |
14015 | The readme for double byte is not displayed automatically in the correct encoding in IE.The encoding for the files need to be updated. The workaround is the user has to manually change the encoding in IE. |
02905 | Error on setAttribute script operation |
The following list of reported issues are identified as limitations of WebSphere Product Center. At this time, these issues may or may not be resolved in a subsequent release.
16457 Image, thumbnail attributes are not inherited properly 16570 When entering a negative replace pattern, it is not showing an error message 16875 LDAP User information (Email etc.) is not getting updated 16895 Web services restriction to one company is not apparent in client 17163 Portal: date and number range based search and wildcard search issues 17219 Customers critically misled about the date format they are seeing in Multi-edit 17293 Portal: Performing a search for more than 180+ items is failing. Therefore, a limit has been placed on the search feature. 17360 When the user info in LDAP server is updated, it is not getting refreshed in the Left Pane 17530 Portal: In Item catalog portlet, there is no unassigned category 17586 Report does not generate XML file after the catalog entry items are mass updated 17695 Product Center crashes when wild card used to search category with 250k items
The following inheritance capabilities are not supported in this release:
Ancestral Catalog-Catalog Inheritance
Ancestral Category-Category Inheritance
The Import/Export functionality in WebSphere Product Center is not enabled. Therefore, the Portal/Commerce integration features and the Migration framework provided in the 5.2 release, that have a dependency on this functionality, is limited to English-only locale. This issue will be addressed in a future Fix Pack.
The documentation set for WebSphere Product Center does not includes translation for Italian.
Images used in the documentation were created for English and were used for all translations. Therefore, the number of images used in translated documents have been limited. It is planned for images to be translated in future releases.
Installation files on the WebSphere Product Center product CD are separated into different sub-directories based on the various operating systems supported.
Operating System Installation directory AIX WPC_AIX Linux WPC_Linux HP-UX WPC_HP Solaris WPC_Solaris
Several configuration properties have been added to the common.properties configuration file in this release to support both LDAP integration and Spell Check enablement. Refer to the "WebSphere Product Center: Installation Guide" for configuration properties associated with these new features.
17118 An issue with the WebSphere Product Center installer was reported with the following details: The directory name on Destination panel can not be edited after clicking the browse button.
Workaround: If the destination directory can not be edited at any time during or after clicking the Browse button, click on the Browse button again and specify the target directory.
An installation/configuration issue was reported with the tr_TR locale, which is a Group 2 language supported in this release. The following workaround resolves this issue:
For AIX user in tr_TR locale, before starting the WebSphere Product Center installation (create_schema.sh, create_acme.sh, chreate_cmp.sh) or starting WebSphere Product Center services (start_local.sh) , set the locale to en_US using the following commands:
export LANG = en_US
export LC_ALL = en_US
Issue
Inability to migrate application instances from Locale A to Locale B
Impact
Customers on versions prior to WebSphere Product Center V5.1 (English-only) who wish to migrate to WebSphere Product Center V5.1/V5.2 using a non-English default locale e.g. WebSphere Product Center V4.2.x English to WebSphere Product Center V5.1/V5.2 French
Customers on WebSphere Product Center V5.1->beyond who wish to change their default application locale e.g. WebSphere Product Center V5.2 English to WebSphere Product Center V5.2 French
Does Not Impact
Customers moving from WebSphere Product Center V4.2 English to WebSphere Product Center V5.1/V5.2 English
Customers moving from WebSphere Product Center V5.1/V5.2 Locale A to WebSphere Product Center V5.1/V5.2 Locale A
Cause
The application setup process creates some default named entities
The names are localized for the default application locale
There are 5 such default named entities e.g. "Default Access Control Group", "Default Hierarchy Primary Spec"
Other application object have dependencies on these default entities and their names
Application migrations use the application export/import tool
On application export, foreign-key-like references to these default entities are by the localized name in Locale A
The target application is setup in Locale B, and has different names for these default entities
On application import, there files being imported refer to default entities by name that do -not- exist in the application instance
Workaround
The application export feature exports the entire application instance into a .ZIP file
The .ZIP archive contains only text files (csv, xml, etc)
The .ZIP archive could be uncompressed, followed by a global search and replace to textually replace all occurrences of these 5 default entity names from the source Locale A's names to the target Locale B's names, followed by a recompress back to a .ZIP file ready to be imported
List of five default entity names
1)Default ACG: If ACG name is "Default", replace with localized message OBJECTGROUPENUM_ENUM_STR_DEFAULT in enum_str.xml
check <ACG> tag for Catalogs, WorkFlows
check <Acg> tag for Selections
check <AccessControlGroup> tag for Hierarchies, CollabAreas, Roles
check <AccessControl> tag for Feeds
2)Default Spec: if Spec name is "Default Hierarchy Primary Spec", replace with localized message CREATE_COMPANY_INFO_DEFAULT_HIERARCHY_SPEC_NAME in info.xml
check <Spec> tag for Catalogs, Hierarchies, AttributeCollections
Since attriubtes of default spec are also localized: CREATE_COMPANY_INFO_DEFAULT_HIERARCHY_SPEC_PRIMARY_KEY_FIELD_NAME for "Name" attribute, CREATE_COMPANY_INFO_DEFAULT_HIERARCHY_SPEC_DISPLAY_NAME_FIELD_NAME for "Display Name" attribute and CREATE_COMPANY_INFO_DEFAULT_HIERARCHY_SPEC_PATH_FIELD_NAME for "Path" attribute. And we need to do additional check for them.
check <Attr> tag for AttributeCollections if the spec is default
check <PathAttribute>, < DisplayAttribute> tag for Catalog and Hierarchy if the spec is default
3)Default Hierarchies: if Hierarchy name is "Default Lookup Table Hierarchy", replace with localized message CREATE_COMPANY_INFO_DEFAULT_LOOKUP_TABLE_HIERARCHY_NAME in info.xml. If Hierarchy name is "Default Organization Hierarchy", replace with localized message CREATE_COMPANY_INFO_DEFAULT_ORGANIZATION_HIERARCHY_NAME in info.xml.
check <PrimaryCategoryTree> & <SecondaryCategoryTree> tag for Catalogs
check <Container> tag for CollabAreas
check <ContainerName> tag for CatalogViews and HierarchyViews
check <Hierarchy> tag for Selections
check <CatTreeName> tag for Feeds
4)(Not a common case) System Generated Attribute Collection: If it's "[*]Generated Default Core Collection for XXX" (for v5.x) or "Generated Default Core Collection for XXX" (for v4.2), please replace with localized message SPEC_INFO_GENERATED_GROUP_NAME in info.xml and replace "{0}" in that message with argument XXX. (XXX is spec name here.)
check <AttributeGroup> tag for Catalogs, Hierarchies
check <AttributeCollection> tag for CatalogViews, HierarchyViews, Workflows
check <AttrColl> tag for InheritanceRules
check <AttrCollection> tag for CAP
IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Burlingame Laboratory
Director IBM Burlingame Laboratory
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.S.A
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not necessarily tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information may contain examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Programming interface information, if provided, is intended to help you create application software using this program.
General-use programming interfaces allow you to write application software that obtain the services of this program's tools.
However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.
Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.
The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries, or both:
IBM
the IBM logo
AIX
CrossWorlds
DB2
DB2 Universal Database
Domino
Lotus
Lotus Notes
MQIntegrator
MQSeries
Tivoli
WebSphere
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
MMX, Pentium, and ProShare are trademarks or registered trademarks of Intel Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product or service names may be trademarks or service marks of others.
IBM WebSphere Product Center contains certain Excluded Components (as defined
in the relevant License Information document), to which the following additional
terms apply. This software is licensed to you under the terms and conditions of
the International Program License Agreement, subject to its Excluded Components
provisions. IBM is required to provide the following notices to you in
connection with this softwatre:
i.) IBM WebSphere Product Center includes the following software that was
licensed by IBM from the Apache Software Foundation under the terms and
conditions of the Apache 2.0 license:
- Apache Regular Expression v1.2
- Apache Axis v1.1
- Apache XML4J v3.0.1
- Apache Log4j v1.1.1
- Apache Jakarta Commons DBCP Package v1.1
- Apache Jakarta Commons Pool Package v1.1
- Apache Jakarta Commons Collections Package v3.0
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the
copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all ther
entities that control, are controlled by, or are under common control with that
entity. For the purposes of this definition, "control" means (i) the
power, direct or indirect, to cause the direction or management of such entity,
whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or
more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation source, and
configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation, and conversions to
other media types.
"Work" shall mean the work of authorship, whether in Source or Object
form, made available under the License, as indicated by a copyright notice that
is included in or attached to the work (an example is provided in the Appendix
below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the editorial
revisions, annotations, elaborations, or other modifications represent, as a
whole, an original work of authorship. For the purposes of this License,
Derivative Works shall not include works that remain separable from, or merely
link (or bind by name) to the interfaces of, the Work and Derivative Works
thereof.
"Contribution" shall mean any work of authorship, including the
original version of the Work and any modifications or additions to that Work or
Derivative Works thereof, that is intentionally submitted to Licensor for
inclusion in the Work by the copyright owner or by an individual or Legal Entity
authorized to submit on behalf of the copyright owner. For the purposes of this
definition, "submitted" means any form of electronic, verbal, or
written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems, and
issue tracking systems that are managed by, or on behalf of, the Licensor for
the purpose of discussing and improving the Work, but excluding communication
that is conspicuously marked or otherwise designated in writing by the copyright
owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and subsequently
incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this
License, each Contributor hereby grants to You a perpetual, worldwide,
non-exclusive, no-charge, royalty-free, irrevocable copyright license to
reproduce, prepare Derivative Works of, publicly display, publicly perform,
sublicense, and distribute the Work and such Derivative Works in Source or
Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License,
each Contributor hereby grants to You a perpetual, worldwide, non-exclusive,
no-charge, royalty-free, irrevocable (except as stated in this section) patent
license to make, have made, use, offer to sell, sell, import, and otherwise
transfer the Work, where such license applies only to those patent claims
licensable by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s) with the Work
to which such Contribution(s) was submitted. If You institute patent litigation
against any entity (including a cross-claim or counterclaim in a lawsuit)
alleging that the Work or a Contribution incorporated within the Work
constitutes direct or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate as of the date
such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or
Derivative Works thereof in any medium, with or without modifications, and in
Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of
this License; and
(b) You must cause any modified files to carry prominent notices stating that
You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You
distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work, excluding those notices
that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained within such NOTICE
file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one of the following
places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or documentation, if
provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and wherever such
third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and do not modify the
License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside or as an addendum
to the NOTICE text from the Work, provided that such additional attribution
notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide
additional or different license terms and conditions for use, reproduction, or
distribution of Your modifications, or for any such Derivative Works as a whole,
provided Your use, reproduction, and distribution of the Work otherwise complies
with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any
Contribution intentionally submitted for inclusion in the Work by You to the
Licensor shall be under the terms and conditions of this License, without any
additional terms or conditions. Notwithstanding the above, nothing herein shall
supersede or modify the terms of any separate license agreement you may have
executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names,
trademarks, service marks, or product names of the Licensor, except as required
for reasonable and customary use in describing the origin of the Work and
reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including,
without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT,
MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible
for determining the appropriateness of using or redistributing the Work and
assume any risks associated with Your exercise of permissions under this
License.
8. Limitation of Liability. In no event and under no legal theory, whether in
tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly negligent
acts) or agreed to in writing, shall any Contributor be liable to You for
damages, including any direct, indirect, special, incidental, or consequential
damages of any character arising as a result of this License or out of the use
or inability to use the Work (including but not limited to damages for loss of
goodwill, work stoppage, computer failure or malfunction, or any and all other
commercial damages or losses), even if such Contributor has been advised of the
possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or
Derivative Works thereof, You may choose to offer, and charge a fee for,
acceptance of support, warranty, indemnity, or other liability obligations
and/or rights consistent with this License. However, in accepting such
obligations, You may act only on Your own behalf and on Your sole
responsibility, not on behalf of any other Contributor, and only if You agree to
indemnify, defend, and hold each Contributor harmless for any liability incurred
by, or claims asserted against, such Contributor by reason of your accepting any
such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate
notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include the brackets!)
The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a file or class name
and description of purpose be included on the same "printed page" as
the copyright notice for easier identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License"); you
may not use this file except in compliance with the License. You may obtain a
copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed
under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
for the specific language governing permissions and limitations under the
License.
ii.) IBM WebSphere Product Center includes the following software that was
licensed by IBM from Scott Hudson, Frank Flannery and C. Scott Ananian under the
following terms and conditions:
- Cup Parser Generator v0.10k
CUP Parser Generator Copyright Notice, License, and Disclaimer
Copyright 1996-1999 by Scott Hudson, Frank Flannery, C. Scott Ananian
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both the copyright
notice and this permission notice and warranty disclaimer appear in supporting
documentation, and that the names of the authors or their employers not be used
in advertising or publicity pertaining to distribution of the software without
specific, written prior permission. The authors and their employers disclaim all
warranties with regard to this software, including all implied warranties of
merchantability and fitness. In no event shall the authors or their employers be
liable for any special, indirect or consequential damages or any damages
whatsoever resulting from loss of use, data or profits, whether in an action of
contract, negligence or other tortious action, arising out of or in connection
with the use or performance of this software.
iii.) IBM WebSphere Product Center includes the following software that was
licensed by IBM from Elliot Joel Berk and C. Scott Ananian under the following
terms and conditions:
- JLex v1.2.6
JLEX COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
Copyright 1996-2003 by Elliot Joel Berk and C. Scott Ananian
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted, provided that
the above copyright notice appear in all copies and that both the copyright
notice and this permission notice and warranty disclaimer appear in supporting
documentation, and that the name of the authors or their employers not be used
in advertising or publicity pertaining to distribution of the software without
specific, written prior permission. The authors and their employers disclaim all
warranties with regard to this software, including all implied warranties of
merchantability and fitness. In no event shall the authors or their employers be
liable for any special, indirect or consequential damages or any damages
whatsoever resulting from loss of use, data or profits, whether in an action of
contract, negligence or other tortious action, arising out of or in connection
with the use or performance of this software. Java is a trademark of Sun
Microsystems, Inc. References to the Java programming language in relation to
JLex are not meant to imply that Sun endorses this product.
iv.) IBM WebSphere Product Center includes the following software that was
licensed by IBM from International Business Machines Corporation and others
under the following terms and conditions:
- ICU4J v2.8
ICU License - ICU 1.8.1 and later
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2003 International Business Machines Corporation and others
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
provided that the above copyright notice(s) and this permission notice appear in
all copies of the Software and that both the above copyright notice(s) and this
permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD
PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS
NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be
used in advertising or otherwise to promote the sale, use or other dealings in
this Software without prior written authorization of the copyright holder.
-----------------------------------------------------------------------------
All trademarks and registered trademarks mentioned herein are the property of
their respective owners.