The objective of this
guide is to facilitate the installation and configuration of the IBM Global Data
Synchronization for WebSphere Product Center solution for both Supply and Demand components.
The intended audiences for
this guide are the system administrators and IT analysts who are responsible for
installing and configuring IBM Global Data Synchronization for WebSphere Product Center.
The following related
Global Data Synchronization Demand documentation is also available:
.
User Guide
.
Customization guide
.
WebSphere Partner Gateway configuration guide
.
Release Notes
This document uses the
following conventions:
|
Courier New
font |
Indicates
commands, directory names, user names, path names, and file names.
|
|
Note |
Indicates
important or clarifying information including exceptions,
interdependencies, and special situations. |
|
Tip |
Indicates a
helpful action that will simplify or streamline the current
procedure. |
|
bold
font |
Indicates
buttons, tabs, menus, and keyboard key names. For example, the Save
button. |
|
Italics font
|
Indicates
screen names. For example, the Login
screen. |
|
Term/Acronym |
Description |
|
GDS |
For convenience, the
product name IBM Global data synchronization for WebSphere Product Center is sometimes written in a shortened form as
GDS. All instances of the acronym GDS in this document and related
documentation stand for the product name IBM Global Data Synchronization
for WebSphere Product Center. |
|
Trade Item |
A Trade Item is any
product or service for which there is a need to retrieve pre-defined
information and that may be priced, ordered or invoiced at any point in
any supply chain. |
|
Global Trade Item Number (GTIN) |
This is a unique
14-digit number used to identify trade items. The first 13 digits
represent the item reference number and the last digit is the check
digit. |
|
Global Location Number (GLN) |
This is a unique 13-digit number used identify
trading partners and trade location. |
|
Target Market (TM) |
Geographic areas in
which a trade item is available for sale. |
|
Information Provider (IP) |
Information provider
indicates the information owner. For example, Distributor, broker,
Manufacturer, or Franchisee. The retailer could receive information from
both sellers and this field indicates the information
owner. |
|
Global Attributes |
A global attribute
indicates that the attribute is relevant for business cases around the
world and can only have a single value throughout the world.
(For example,
GTIN). |
|
Global-Local Attributes |
A global/local
attribute indicates that the field is relevant for business cases around
the world. Its definition is the same but may have a different value
depending on the geography. (For example, VAT tax values, 1.00 in
France, 1.05 in Belgium) |
|
Local Attributes |
A local attribute is
only relevant in certain geographical areas, and the values may change
based on where the product is offered for sale. (For example, green dot
:only relevant in certain European countries.) |
|
Data Pool |
Repositories of data
where trading partners can obtain, maintain, and exchange information on
items and parties in a standard format. |
|
Global Registry |
A directory for the
registering the items.The item is identified by the GTIN, GLN, and Target
Market. Each combination of this key data found in the Global Registry is
unique. |
Global Data
Synchronization is the process by which trading partners exchange basic
information about products on an ongoing basis. The information can be on price,
party, and other relationship-specific details. This process ensures that all
stakeholders for a product are kept in sync about the latest information
on the product.
Global Data
Synchronization enables you to:
.
Reduce costs and increase competitiveness through the efficient and accurate
transfer and on-going synchronization of information.
.
Lay the foundation for future supply chain collaboration initiatives which
require that trading partners are in sync on the basic product, price,
party, and relationship specific information.
This section details the
minimum hardware and software required for installing the IBM Global Data
Synchronization for WebSphere Product Center solution.
Note:The requirements listed in this section are the minimum
hardware and software recommendations. Prior to installation, a requirement
analysis is recommended by WebSphere Professional Services to plan hardware
considerations based on the choice of software used and the projected load
volume of the servers (that is,the number of SKU's and transaction
rates).
This section outlines the
hardware and software requirements for the following platform:
|
Operating System
|
Application Server |
Database Server |
|
AIX Version 5L
v5.2
|
IBM WebSphere
Application Server Version 5.1.1
|
IBM DB2 II Version
8.2
Advanced Edition,
Fix
Pack 5
OR
Oracle 9.2.0.5
Enterprise
Edition
|
|
AIX 5L 5.3 (32 & 64 bit) |
WebSphere Application Server 5.1.1 |
IBM DB2 II Version 8.2 Advanced
Edition |
|
Application Server |
|
Software |
WebSphere Product
Center
5.2.1 IF 003
WebSphere Application Server
5.1.1
AIX 5L 5.2 (32 & 64
bit)
IBM HTTP Server
2.0
IBM JDK bundled with
WebSphere Application Server 5.1.1
|
|
Hardware
|
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 |
|
Software
|
IBM DB2 II 8.2 Advanced
Edition
AIX 5L 5.2(32 & 64
bit)
|
|
Hardware
|
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 |
|
This primary stack is also
bundled with the following:
WebSphere MQ Series V5.3
(1)
WebSphere Business
Integration Adapter for WebSphere MQ V
2.7 (1,2)
WebSphere Business
Integration Adapter Framework V2.4.0 (1, 2)
Websphere Portal Server
V5.1
(1) A limited use license is
included with WebSphere Product
Center
(2) Required when
integrating with a process hub
|
|
Application Server
|
|
Software |
WebSphere Application Server
5.1.1
AIX 5L 5.2
IBM HTTP Server
2.0
IBM JDK bundled with
WebSphere Application Server 5.1.1
|
|
Hardware
|
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
|
|
Software
|
Oracle 9.2.0.5 Enterprise
Edition
AIX 5L 5.2
|
|
Hardware
|
Server Type: Intel
compatible
Processor: Dual Intel, XEON
2.8 GHz
Memory: 6 GB
Disk Sub-System: 365 GB 10K
RPM SCSI Driver |
|
Application Server
|
|
Software |
WebSphere Application Server
5.1.1
AIX 5L 5.2 (32 & 64
bit)
IBM HTTP Server
2.0
IBM JDK bundled with
WebSphere Application Server 5.1.1
|
|
Hardware
|
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
|
|
Software
|
DB2 II 8.2 Advanced
Edition
AIX 5L 5.2
|
|
Hardware
|
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 |
This section outlines the
hardware and software requirements for the following platform:
|
Operating System
|
Application Server |
Database Server |
|
Red Hat Enterprise Linux AS 3.0 Update 3
|
WebLogic Server
8.1
Service Pack
2
|
Oracle 9.2.0.5
Enterprise Edition
|
|
Red Hat Enterprise Linux AS 3.0 Update 3 |
WebSphere Application Server 5.1.1 |
IBM DB2 II Version 8.2 Advanced Edition
OR
Oracle 9.2.05 Enterprise
Edition |
|
Application Server |
|
Software |
WebSphere Product
Center
5.2.1 IF 003
WebLogic Server 8.1 Service
Pack 2
Apache HTTP Server
2.0
Red Hat Enterprise Linux AS
3.0 Update 3
WebLogic JDK bundled with
WebLogic Server 8.1 Service Pack 2
|
|
Hardware
|
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 |
|
Software
|
Oracle 9.2.0.5 Enterprise
Edition
Red Hat Enterprise
Linux
AS 3.0
Update
|
|
Hardware
|
Server Type :Intel
Compatible
Processor : Dual Intel, XEON
2.8 GHz
Memory : 6 GB
Disk Sub-System :365 GB 10K
RPM SCSI Driver
|
|
Application Server
|
|
Software |
WebSphere Application Server
5.1.1
IBM HTTP Server
2.0
Red Hat Enterprise Linux AS
3.0 Update 3
IBM JDK bundled with
WebSphere Application Server 5.1.1
|
|
Hardware
|
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
|
|
Software
|
DB2 II 8.2 Advanced
Edition
Red Hat Enterprise Linux AS
3.0 Update 3
|
|
Hardware
|
Server Type: Intel
compatible
Processor: Dual Intel, XEON
2.8 GHz
Memory: 6 GB
Disk Sub-System: 365 GB 10K
RPM SCSI Driver |
|
Application Server
|
|
Software |
WebSphere Application Server
5.1.1
IBM HTTP Server
2.0
Red Hat Enterprise Linux AS
3.0 Update 3
IBM JDK bundled with
WebSphere Application Server Network Deployment 6.0.2
|
|
Hardware
|
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
|
|
Software
|
Oracle 9.2.0.5 Enterprise
Edition
Red Hat Enterprise Linux AS
3.0 Update 3
|
|
Hardware
|
Server Type: Intel
compatible
Processor: Dual Intel, XEON
2.8 GHz
Memory: 6 GB
Disk Sub-System: 365 GB 10K
RPM SCSI Driver |
|
Operating System
|
Application Server |
Database Server |
|
HP UX 1
1i
|
WebLogic Server
8.1
Service Pack
2
|
Oracle 9.2.0.5
Enterprise Edition
> |
|
Application Server |
|
Software |
WebSphere Product
Center
5.2.1 IF 003
WebLogic Server 8.1 Service
Pack 2
Apache HTTP Server
2.0
HP/UX 11i
WebLogic JDK bundled with
WebLogic Server 8.1 Service Pack 2 |
|
Hardware
|
Server Type : HP RP
4440
Processor : 2
CPUs
Memory : 4 GB
Disk Sub-System : HP MSA
1000
|
|
Database Server |
|
Software
|
Oracle 9.2.0.5 Enterprise
Edition
HP/UX 11i
|
|
Hardware
|
Server Type : HP RP
4440
Processor : 2
CPUs
Memory : 4 GB
Disk Sub-System : HP MSA
1000
|
|
Operating System
|
Application Server |
Database Server |
|
Solaris 9 |
WebSphere Application
Server Network Deployment
5.1.1
OR
WebLogic Server
8.1
Service Pack 2 |
Oracle
9.2.0.5 |
|
Application Server |
|
Software
|
WebLogic Server 8.1 Service
Pack 2
Apache HTTP Server
2.0
HP/UX 11i
WebLogic JDK bundled with
WebLogic Server 8.1 Service Pack 2
|
|
Hardware
|
Server Type : HP RP
4440
Processor : 2
CPUs
Memory : 4 GB
Disk Sub-System : HP MSA
1000
|
|
Database Server |
|
Software
|
Oracle 9.2.0.5 Enterprise
Edition
HP/UX 11i
|
|
Hardware
|
Server Type : HP RP
4440
Processor : 2
CPUs
Memory : 4 GB
Disk Sub-System : HP MSA
1000
|
|
Application Server |
|
Software
|
WebSphere Application Server
5.1.1
IBM HTTP Server
2.0
Solaris 9
IBM JDK bundled with
WebSphere Application Server 5.1.1
|
|
Hardware
|
Server Type : Sun Enterprise
V440
Processor - 4 way UltraSPARC
IIIi @ 1.062 GHz
Memory : 4 GB
Disk Sub-System : Sun
StorEdge 3510
|
|
Database Server |
|
Software
|
Oracle 9.2.0.5 Enterprise
Edition
Solaris 9
|
|
Hardware
|
Server Type : Sun Enterprise
V440
Processor : 4-way UltraSPARC
IIIi @ 1.062 GHz
Memory : 4 GB
Disk Sub-System : Sun
StorEdge 3510
|
The following represents the minimum client Hardware
requirements for client access to IBM Global Data Synchronization for WebSphere
Product Center:
|
Operating environment
|
|
Software |
Microsoft Windows 2000
Professional Service Pack 3
OR
Microsoft Windows XP
Professional Service Pack 1
AND
Browser: Microsoft Internet
Explorer Version 6.0 Service
Pack 1
|
|
Hardware
|
Processor: Intel-based
system with a Pentium 3 processor
and a minimum processor
speed of 750 MHz
Memory: 256 MB
|
Note: If your IE browser displays any other tool bar other than
an IE tool bar, then error messages such as Page not found may be
displayed when working with the IBM Global Data Synchronization for
WebSphere Product Center solution. Therefore, ensure that you do not have any other
toolbars other than IE toolbars. Also ensure that no other utilities are
installed on your IE browser.
This chapter provides the
installation procedure to install the IBM Global Data Synchronization for
WebSphere
Product
Center
solution.
The installation process
is described primarily for AIX operating system, DB2 database and WebSphere
Application Server. The instructions hold good for installation on other stacks
supported in the current release. Specific changes are mentioned as a note
depending on the combination of Operating system, Database and Application
Server being used.
Note:
If you are configuring a fix pack, skip this section and directly go to Post Installation tasks
section
Note: Refer to the Installation checklist provided in Appendix C for a quick reference to verify
proper installation.
Note: Before you start the installation of GDS ensure that
WebSphere
Product
Center is
not running.
This section specifies the
pre-requisites necessary before installing the IBM Global Data Synchronization
for WebSphere Product Center solution.
Prior to installing IBM
Global Data Synchronization for WebSphere Product Center application,
ensure that WebSphere Product Center version 5.2.1 IF003 is installed on your system. Download
the WebSphere Product Center binaries (currently for 5.2.1 IF003 with all patches) and
put them in the source directory. For information about installing WebSphere Product Center version 5.2.1
IF003, refer WebSphere Product
Center 5.2.1 IF003 Installation Guide.
The pre-requisites
are:
1. WebSphere Product Center 5.2.1 IF003 must
be installed and the patch must be applied with the necessary schema updates as
required.
2. WPC and GDS both require a server, a virtual host, and an
installed war file. Neither of these components is shared nor can the WPC and
GDS directory be shared.
There are two source file
directories; one for WebSphere Product Center files, and the other for IBM Global Data synchronization
for WebSphere Product Center files.
There are two separate
application servers created for each of the applications on which the respective
war files are installed. Similarly there are two virtual hosts
created.
The database is shared by
both the applications. Both the applications use the same company
name.
Note:WebSphere Business Integration Connect(WEBSPHERE PARTNER
GATEWAY) and IBM Global Data Synchronization for WebSphere Product Center should
each be deployed in operating environments consistent with the technology
platforms supported by the individual products. There is no technology platform
dependency between these two products. For more information on installation and
configuration for WebSphere Partner Gateway, please refer to the WebSphere
Partner Gateway documentation. To configure WEBSPHERE PARTNER GATEWAY specific
to GDS, refer to the WebSphere Partner Gateway documentation provided along with
GDS (IBMGDS_WPGconfigdoc_1.3).
This section describes general procedures for using
the installation media.
Invoking the
Graphical Installer
The graphical Installer presents a wizard that
allows a user to make choices about The installation of Global Data
Synchronization for WebSphere Product Center. Invoke the Installer by running an
executable from one of the installation media installer directories.
|
Operating System
|
Installer
directory |
|
AIX |
GDS_Demand_AIX
|
|
Linux |
GDS_Demand_Linux |
|
HP-UX |
GDS_Demand_HP |
|
Solaris |
GDS_Demand_Solaris |
Example on AIX:
This example describes how to invoke the WebSphere
Product Center installer for an AIX environment.
Running CDE on the AIX computer: If
the Common Desktop Environment (CDE) is running and working on the AIX computer
directly, then navigate the installation media and double-click the desired bin
file (*.bin) to invoke the Installer.
Another option would be to navigate the
installation media and execute the bin file (.bin) at the command line.
Connecting to the AIX computer through X
emulation software: If a Windows computer is used to connect to the AIX
computer through X emulation software do the following to invoke the
installer:
1. Configure the environment for X emulation
software.
2. Execute the bin file (.bin) specific to the
operating system. The following example shows how to do so on an AIX
computer.
./setupAix.bin
The graphical installer starts on the Windows
computer that is used to connect to the AIX computer.
A silent installation of Global Data
Synchronization for WebSphere Product Center can be performed where installation
choices are provided in a file rather than at the screens of the installation
wizard. This is particularly helpful when performing multiple installations that
are identical.
The silent installation can be executed with or
without an options file. The options file holds the install parameters used by
the silent installation. Run the installer executable at the command line using
one of the following choices:
. Set
installation options manually
.
Use option file to set installation options
Performing silent installation setting option manually
In order to start the installer in silent mode,
invoke the following:
>./setup.bin -silent -options <options
file>
Ensure that an options file has been created
containing the appropriate parameters, which gets passed to the installer at
startup.
Note :
The options file can contain comment lines starting with '#': these are ignored
by the installer
When performing a silent installation, the
following mandatory parameters are required:
|
Installation
Location |
Provide the location
for the installation directory
-PinstallLocation=<dir>
Note: Use
the full path names when specifying <dir>
names |
|
License
Agreement |
Indicate acceptance of
the license agreement, the user is required to supply the following
parameter in the options file.
-G
licenseAccepted=true |
|
Application server
and database combinations |
Include the selection of application server and
database combination for a specific operating system. These options can be
included as part of the install options set manually or as part of the
option file.
For AIX
-W adapterFeatures_aix.selectedFeature=<index>
Index values
.
AIX/WAS/DB2 = 0
.
AIX/WAS/Oracle= 1
For Linux
-W adapterFeatures_linux.selectedFeature=<index>
Index values
.
Linux/WAS/DB2 = 0
.
Linux/WAS/Oracle= 1
.
Linux/WAS/Oracle= 2
For HPUX
.
HP/WebLogic/Oracle
For Solaris
.
Solaris/WAS/Oracle
For options with only one application server and database combination
option, it is only required to include the installation location
option.
./<installer file> -P installLocation=<dir> -silent
Note: Refer to the software requirements sections
in this document for the supported versions of each application server and
database combination. |
To install silently using the required
options, use the following command line:
./<name of installer file> -W
adapterFeatures_<operating system>.selectedFeature=<index> -P
installLocation=<dir> -silent
Example
The following example shows how to do so for an AIX
computer using the WebSphere/DB2 combination:
./setupAIX.bin-wadapterFeatures_aix.selectedFeature=0-PinstallLocation=
/opt/IBM/WPC-silent
Perform silent install with options file
The installer can record user selections during an
interactive install to a file. This file is generated when installation is
complete. This file can be used as a response file for silent installs on other
machines (recorded user selection is applied to these installs).
./setup.bin -options -record
<file name>
The silent install can be performed using an
options file by using the following command line:
./setup.bin -P -Options
<options file name> -silent
The options file must include the required options
for the silent install, as discussed in the previous section.
This section provides instructions to install
Global Data Synchronization for WebSphere Product Center style='font-family:.
You can select to install the software product using the graphical installer or
silently from the command line.
The Installer is used to
unzip the files to the required directory.
To install the IBM Global
Data Synchronization for WebSphere Product Center solution using the installer:
1.
Invoke the installer as described in Invoking
the graphical Installer.
2.
Select a language to be used for the installation wizard and click
OK
3.
At the "Welcome" screen click
Next.
4.
At the IBM software license acceptance
screen, click "I accept the terms in the license agreement" and then click
Next.
5.
Select the application server and
database combination from the available list of combinations and click
Next.
6.
At the product directory screen,
perform one of the following tasks:
a.
Type the full path of the directory into which
you want to install Global Data Synchronization for WebSphere Product Center in the Directory
Name field and click Next.
b.
Click Browse to select a directory and click
Next.
c.
Accept the default path and click
Next.
7.
>The summary screen lists the features that
will be installed, the specified product directory, and the amount of disk space
required. Click Next.
8. After the installer finishes successfully, >it is
installed but not configured. Click Finish
Configure to proceed configuring Global Data Synchronization for
WebSphere
Product
Center
or click Finish to configure manually. This completes the installation process.
Configuration
1. Select
appropriate WPC,WAS_HOME,JDK_HOME click N ext after this step
2. Input the
Application Server related details. (Hostname
name, VHOST,
Appserver port)
3. Input the
database connection details for messaging:
i. db_maxConnection_appsvr_gdsmsg=30
ii. db_maxConnection_scheduler_gdsmsg=10
iii. db_maxConnection_workflowengine_gdsmsg=10
iv. db_maxConnection_messaging=60
v. db_minConnection_messaging=4
vi. db_maxConnection_messaging_gdsmsg=40
vii. db_maxConnection_messaging_default=10
viii. db_maxConnection_messaging_system=10
4. Input GDS Company, Datapool and M ode.
5. Input GDS variables for messaging services (exchange
GLN,
Self GLN etc.), refer to Appendix E for
details.
6. Click the icon to configure parameters for the messaging
receiver, or else click Next to continue.
7. Click on the icon to configure the Data Model, or click
on Next to continue
8. To configure security, refer to C hapter
5
1.
Installer startup
This is identical to the startup in graphical mode
, except for the command line flag:
> ./setup.bin -console
2.
Language selection
Once the installer is invoked, the user is
presented with the language selection screen showing all G1 languages. The
default is English. Type in the number corresponding to the desired
languages.
Select a language to be used for this wizard.
[ ] 1: Simplified Chinese
[ ] 2: Traditional Chinese
[X] 3: English
[ ] 4: Portuguese (Brazil)
[ ] 5: French
[ ] 6: German
[ ] 7: Italian
[ ] 8: Japanese
[ ] 9: Korean
[ ] 10: Spanish
To select an item enter its number, or 0 when you
are finished: [0]
3.
Welcome Screen
The user is shown the welcome screen showing basic
product information, as shown below.
-------------------------------------------------------------------------------
Welcome
to the InstallShield Wizard for IBM Global Data Synchronization for
WebSphere Product
Center 1.3.0
The InstallShield Wizard will install IBM Global
Data Synchronization for
WebSphere Product
Center1.3.0 on your computer.
To continue, choose Next.
IBM Global Data Synchronization for
WebSphere Product Center 1.3.0
IBM
http://www.ibm.com
4.
Software License Agreement screen
The user will first be shown instructions on how to
work with the license agreement (LAP Instructions screen)
Press the Enter key to view the license agreement
text, one screen at a time. At then end of the agreement, enter 1 to accept the
terms. If you choose to decline the agreement, installation will not be
completed and you will not be able to complete the installation.
5.
Platform Warning screen
If attempting to install on an unsupported
operating system the following text appears.-
------------------------------------------------------------------------------
You
are attempting to install GDS on a version of the operating system for which no
formal testing has been done. For more details please consult the Release
Notes
Press 1 for Next, 2 for Previous, 3 to Cancel or 4 to Redisplay
[1]
Press 1 to continue if desired.
6.
Stack (Appserver/DB server combination) Selection screen
Select the number that corresponds to your
application server and database server stack being configured for GDS. Press 1
to continue to the next screen.
7.
WAS-DB2 Pre-requisite Check screen
This screen will show only if the user selected the
WAS-DB2 stack, and immediately after the stack selection screen. The screen will
show a message indicating that the installer is checking for the pre-requisite
on the local system. The installer will be searching for the WAS and DB2
versions stated in the PRD. The text will be approximately as follows:
Please wait while the installer searches for
pre-requisites on the local system.
8.
Missing WAS-DB2 pre-requisite screen.
This screen appears only if the user selected the
WAS-DB2 stack, and the installer fails to find the WAS app-server and DB2 server
on the local machine.
The screen informs the user that the software was
not found. It will allow the installation to proceed, but a warning
message will appear.
Press 1 to continue to the next screen.
9.
Destination Screen
The user is prompted to specify the installation
directory for the product. Specify a directory or press Enter to accept the
default directory.
Destination Directory [/opt/IBM/GDS]
The default installation path will be /opt/IBM/GDS.
If the product was previously installed, the default path will be the
installation path of the last installation. The user can type the installation
path of their choice.
Press enter, then press 1 to continue to the
next screen.
Note: To utilize the
directory where you have previously installed GDS, you have to uninstall all old
versions of GDS to proceed
Prior to moving to the next screen, the path is
checked for invalid characters as well as the presence of the space character,
and access permissions. The user is shown an appropriate error message, if
applicable:
.
Error: /opt/readOnlyDir is not writable.
.
A file name cannot contain any of the following characters: ' " ^ ( ) \ | { } [
] < >
.
The directory name must not contain any spaces.
If there is not enough space in the selected path,
the user is presented with the following message:
WARNING: /opt partition has insufficient space
to install the items selected. 76.2 MB additional space would be needed to
install the selected items. Press 2 to go back to the previous screen and return
to the be returned to the directory path prompt. Enter a new path that has
sufficient disk space.
Existing WPC Installation Search screen.
This screen indicates to the user that the
installer is searching for existing installations of GDS on the local system.
The installer performs a search of software that was installed using the
executable installer (installations carried out by extracting the product from a
TAR files will not be detectable, in general).
Versions of GDS from1.1.x up to and including 1.3.0
will be detected.
The installer will be able to detect all successful
installations of GDS carried out by the user invoking the current installation.
In general, the installer will not detect any installations of GDS that were
carried out by a different user.
Install Preview screen.
This screen displays to the customer the basic
installation settings (location, and total disk space required).
-------------------------------------------------------------------------------
Global
Data Synchronization for WebSphere Product Center 1.3.0 will be installed in the
following location:
/opt/IBM/GDS
for a total size:
70
MB
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to Redisplay
[1]
Install Progress screen.
This screen displays the progress of file transfer
(percent to completion shown as vertical bars below a scale), and other
install-time tasks.
Installing IBM Global Data Synchronization for
WebSphere Product Center
1.3.0.
Please wait...
Time to log: 1
0 % complete
10 % complete
20 % complete
30 % complete
40 % complete
50 % complete
60 % complete
70 % complete
80 % complete
90 % complete
Time to log: 16
Time to log: 0
100 % complete
Creating
uninstaller...
Finalizing the Vital Product Data Registry. Please
wait...
Post-Install Summary screen.
This screen will show immediately after
installation is complete .
-------------------------------------------------------------------------------
The
InstallShield Wizard has successfully installed Global Data Synchronization for
WebSphere Product Center 1.3.0. Choose Next to continue the
wizard.
Press 1 for the next screen.
Existing GDS - Migration Guide Information screen.
This screen indicates to the user that the
installer is searching for existing installations of GDS on the local system.
The installer will perform a search of software that was installed using the
executable installer (installations carried out by extracting the product from
TAR files will not be detectable, in general).
Versions of GDS from 1.1.0 up to and including
1.3.0 will be detected.
The installer will be able to detect all successful
installations of GDS carried out by the user invoking the current installation.
In general, the installer will not detect any installations of GDS that were
carried out by a different user.
It is important to note that the installer will
only be able to detect GDS installations that were carried out using installer
software.
Finish screen.
-------------------------------------------------------------------------------
Please
read the information below.
You have completed the installation of IBM
Global Data Synchronization for
WebSphere Product
Center 13.0. To proceed with Configuration click Next and to
exit
without configuring click Cancel. Please consult
the Release notes for details
on this release. An Installation Log has been
created in /tmp/GDSinstallLog.txt.
Configuration
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Select the WPC for GDS installation
Select the WebSphere Application Server
Select the JDK
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Enter the setup attributes
WAS_NODENAME:
WAS_APPSERVERNAME:
WAS_HOSTNAME:
APP_SVR_PORT: 9876
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Enter GDS specific parameters
Company:
Admin User:
GDS_App_Type:
Active_Datapool_Id:
Language_Specific_Spec_Identifier:
Press 1 for Next, 2 for Previous, 3 to Cancel or 5 to
Redisplay [1]
Enter Messaging Parameters (
** Attributes additional for UCCNet)
ExchangeGLN:
SelfGLN:
UserID **:
Password**:
RepresentatingParty:
Default Locale:
Timezone:
Enter Messaging Parameters (
** Attributes additional for UCCNet)
Sender Identifier:
Receiver Identifier:
Press 1 for Next, 2 for
Previous, 3 to Cancel or 5 to Redisplay [1]
Enter Database connection
details for messaging
db_minConnection_messaging:
db_maxConnection_messaging:
db_maxConnection_messaging_gdsmsg:
db_maxConnection_messaging_default:
Press 1 for Next, 2 for
Previous, 3 to Cancel or 5 to Redisplay [1]
Enter Database connection
details for messaging
db_maxConnection_messaging_system:
db_maxConnection_appsvr_gdsmsg:
db_maxConnection_scheduler_gdsmsg:
db_maxConnection_workflowengine_gdsmsg:
Press 1 for Next, 2 for
Previous, 3 to Cancel or 5 to Redisplay [1]
Please select to configure
the messaging receiver [True/False]
If you select true
Enter the parameters for
configuring messaging receiver.
Queue name for Inbound
messages:
Queue name for Outbound
messages:
Queue Factory Name:
Press 1 for Next, 2 for
Previous, 3 to Cancel or 5 to Redisplay [1]
If you select false:
Please Select to Load Data Model
[True/False]
Press 1 for Next, 2 for
Previous, 3 to Cancel or 5 to Redisplay [1]
GDSv1.3 has been configured and
after doing the security settings you can
access GDS application at the
following URL:
http://<hostip>:xxxx/Login.do
Press 1 for Next, 3 to Cancel or
5 to Redisplay [1] 1
IBM Global Data Synchronization
for WebSphere Product Center 1.3.0
-
InstallShield Wizard
Thanks for using GDS
installer.
Press 3 to Finish or 5 to
Redisplay [3]
Ch 3
Post Installation Tasks
This section provides the
post installation tasks for IBM Global Data synchronization for WebSphere Product Center.
Note:If
you are facing the error "argument list is too long" on AIX stack, do the
following to increase the size of the argument list that is used by WAS_CPATH
variable to pass the Classpath:
1. Check the supported argument list size
of the OS:
lsattr -El sys0 -a
ncargs
2. Change the size by running the following
command:
chdev -l sys0 -a
ncargs=<number>
By default it is 4k byte. You have to
increase it in blocks of 4kb. So, if you specify 100 as
<number> then it becomes 400k byte.
1.
In the .bashrc file of the IBM Global
Data Synchronization for WebSphere Product Center solution, make the following changes:
a. Set
the variable TOP to the GDS installed directory.
Example on AIX:
export
$TOP=/usr/gds
b. Set
the environment variable WPC_INSTALL_DIR to the WPC installed
directory.
Example on AIX:
export
WPC_INSTALL_DIR=/usr/gds/wpc_5002_07_websphere5_db2_unix
>b c. Set the environment variable WPC_JAR_DIR to the
directory where WPC jars are located.
Example on AIX:
export
WPC_JAR_DIR=/usr/gds/wpc_5002_07_websphere5_db2_unix/jars
-Or-
export WPC_JAR_DIR=$WPC_INSTALL_DIR/jars
c. d. Set
DB Home variable in
Example on AIX/ORACLE
export ORACLE_TERM=vt100
export
ORACLE_HOME=/dump/oracle/OraHome1
export ORACLE_SID=ORAQA
export
LD_LIBRARY_PATH=$ORACLE_HOME/lib
export
PATH=$PATH:HOME/bin:$ORACLE_HOME/bin
EXAMPLE
on DB2:
if [ -f
/db2data/db2inst1/sqllib/db2profile ]; then
./db2data/db2inst1/sqllib/db2profile
e. Include the
following script
Tahoma; background:white'> .setup/init_cgd_vars.sh . <GDS Installed
Directory>/setup/init_cgd_vars.sh
2. Create a soft link for the following or copy the following
files from GDS installed directory to WPC installed directory.
The table describes the commands for creating soft links
for files and directories
>
|
Filename |
Syntax |
|
gds.properties
|
ln -s< GDS Installed Directory
>/etc/default/gds.properties
<
WPC_Install_Dir >/etc/default/gds.properties
|
|
gds_system.properties
|
ln -s < GDS Installed Directory> /etc/default/gds_system.properties
<
WPC_Install_Dir >/etc/default/gds_system.properties |
|
gdsDemandTradeItemFunctions.properties.
(for demand side)
gdsSupplyTradeItemFunctions.properties.
( for supply side) |
For demand:
ln -s < GDS Installed Directory
>/etc/default/gdsDemandTradeItemFunctions.properties
<WPC_install_dir> >
$WPC_INSTALL_DIR/etc/default/gdsDemandTradeItemFunctions.properties
For Supply
ln -s < GDS Installed Directory
>/etc/default/gdsSupplyTradeItemFunctions.properties
<WPC_install_dir>
$WPC_INSTALL_DIR/etc/default/gdsSupplyTradeItemFunctions.properties
|
|
GDSServiceRegistrySupply.xml
If you are
installing a demand side component then create a link to the following
file >< GDS Installed Directory
>
$TOP/etc/default/GDSServiceRegistryDemand.xml
|
ln -s<GDS Installed Directory
>/etc/default/GDSServiceRegistrySupply.xml
<WPC_install_dir>
$WPC_INSTALL_DIR/etc/default/GDSServiceRegistrySupply.xml
|
|
GDSCacheRegistry.xml. |
ln -s<GDS Installed Directory
>/etc/default/GDSCacheRegistry.xml.
<WPC_install_dir>
$WPC_INSTALL_DIR/etc/default/GDSCacheRegistry.xml |
|
GDSCacheManagerRegistry.xml |
ln -s< GDS Installed Directory>/etc/default/ GDSCacheManagerRegistry.xml.
<WPC_install_dir>
$WPC_INSTALL_DIR/etc/default/
GDSCacheManagerRegistry.xml
|
|
Create a link to
messaging folder in GDS |
ln -s < GDS Installed Directory>/etc/messaging <WPC_install_dir> $WPC_INSTALL_DIR/etc/messaging
|
|
Create a link to
processflow publicationprocess.properties file in GDS (for demand side)
Note: This is only if you
need to use the pass through model for GDS. The custom workflows that need
to be invoked for publications will be configured using the publicationprocess.properties
file.Please refer
Configuring Custom Workflows section in the configuration
guide. |
For UCCNET data
pool
ln -s < GDS Installed Directory
>/etc/processflow/uccnet/publicationprocess.properties
<WPC_install_dir> $WPC_INSTALL_DIR/etc/processflow/
uccnet/publicationprocess.properties
For WWRE
ln -s < GDS Installed Directory
>/etc/processflow/wwre/publicationprocess.properties
<WPC_install_dir> $WPC_INSTALL_DIR/etc/processflow/
wwre/publicationprocess.properties
or create a general
directory for either one:
ln -s < GDS Installed Directory
>/etc/processflow/
<WPC_install_dir> $WPC_INSTALL_DIR/etc/processflow
|
|
.bindings |
ln -s < GDS Installed Directory
>/etc/default/.bindings<WPC_install_dir>>$WPC_INSTALL_DIR/etc/default/.bindings |
Note:If
you have copied the files from GDS to WebSphere Product Center, then for any
changes that you make, ensure that you update files so that they are consistent
in both directories.
3.
Modify the common.properties file located in < GDS Installed
Directory>$TOP/etc/default directory
to configure the application server and the port number.
.
rmi_port
.
app_svr_port
.
db_userName
.
db_password
.
db_url
.
Note:The values for rmi_port and db Connection should be the
same as the values in the common.properties for WebSphere Product Center installation
guide.
Ensure
that different value is specified for app_svr_port when the WebSphere Product Center and IBM Global
Data Synchronization for WebSphere Product
Center are hosted
on the same Application Server.
Do not
maintain soft link for common.properties file.
4.
Run < GDS Installed
Directory > $Top/bin/tesh_db.sh
5.
Modify the init_cgd_vars.sh file
located in < GDS
Installed Directory >$TOP/setup directory to
set the following environment variables in WebSphere Application
Server.
JDK_HOME
WAS_HOME
WAS_NODENAME
WAS_APPSERVERNAME
WAS_VHOST
Example on AIX:
export JDK_HOME=/usr/WebSphere/AppServer/java
export WAS_HOME=/usr/WebSphere/AppServer
export WAS_NODENAME=localhost
export WAS_APPSERVERNAME=gds_reg
export WAS_VHOST=gds_reg
Note: Ensure that the same values are not
specified for WAS_APPSERVERNAME and WAS_VHOST as given while installing
WebSphere
Product
Center.
Specify different values for WAS_APPSERVERNAME and WAS_VHOST for the IBM Global
Data Synchronization for WebSphere Product Center instance.
6.
If the installation is on BEA WebLogic, set the
path for the following
Modify the
init_cgd_vars.sh file located in $TOP/setup
directory for the parameters WL_DOMAIN, WL_HOME, JDK_HOME, WL_SERVER, and
WL_USER, WL_PASSWORD.
Example on AIX:
export
RMIREGISTRY=($JAVA_HOME/bin)
export
JDK_HOME=/root/bea/jrockit70sp5_131_10
export
WL_HOME=/root/bea/weblogic700
export
CCD_WL_DOMAIN_DIR=/root/bea/user_projects/gdsdmddomain
export
CCD_WL_DOMAIN=gdsdmddomain
export
CCD_WL_SERVER=gdsserver1
export
CCD_WL_PW=gdsuser1
export
CCD_WL_USER=gdsuser
Note : If the installation is
being done for HP UX then in addition to the above variables set the Locale to
en_US.iso88591. For example, export
lang="EN"_US.iso88591
Note: Comment the line
export APPSVR_MEMORY_FLAG='-Xmx1024m -Xms256m -XX:MaxPermSize=128m'.
>
Run the .bashrc or logout/login back into the environment for the
changes to be reflected.
7.
Run the .bashrc or logout/login back
into the environment for the changes to be reflected.
8.
Configure the Application
Server.
To
configure WebSphere Application Server, run the scripts create_vhost.sh,
create_appsvr.sh, and install_supply_war.sh
for supply side operations, install_demand_war.sh for demand side
operations, located in the < GDS Installed
Directory
> $TOP/bin/websphere directory.
Note: If you are running Node Manager for WebSphere Application
Server, create the vhost manually from WAS Admin Console and specify the port on
which the IBM Global Data Synchronization for WebSphere Product Center solution will run.
To
configure BEA WebLogic as the Application Server follow the steps listed
in the section
.
Set default home directories
.
Create a new domain with the $WL_HOME/common/bin/ config .sh wizard
.
Update the config.xml file
.
Copy or link the WebLogic domain applications directory
Set default home
directories
The
default home directories are set in step 2 under modifying init_cgd_vars.sh.
For
the purpose of this document, the WebLogic setup instructions in this section
are configured for the following:
Domain name
'gdsdmddomain'
Listening on port
'7506'
Domain files contained
in the directory '/root/bea/user_projects/gdsdmddomain'
Servername set to
'gdsserver1'
WebLogic username
'gdsuser'
WebLogic password
'gdsuser1'
Create a new WebLogic
domain
To
create a new WebLogic domain, use the >config .sh wizard located in the
following directory:
$WL_HOME/common/bin/ config
.sh
a. Run
$WL_HOME/common/bin/ config .sh
b. Choose
Domain Type (3) WLS Domain
c.
Choose Server Type (1) Single Server (Standalone Server)
d. Choose
Domain Name (1) Modify current selection
e.
Configure Single Server
f.
Modify Server Name gdsserver1
g. Modify
Server Listen Port 7506
h. Choose
Location to Create Domain > Modify current selection
/root/bea/user_projects
i.
Enter User Name gdsuser
j.
Enter Password gdsuser1
k. Enter
Verify Password gdsuser1
l.
Press Enter to create the domain and follow the prompts to exit the
wizard.
At
the completion of the config wizard, the following message is displayed:
Domain Configuration Wizard has successfully created gdsdmddomain
Now
that the WebLogic domain has been created in
"/root/bea/user_projects/gdsdmddomain ", it can be configured by editing
/root/bea/user_projects/gdsdmddomain /config.xml"
Configure config.xml
Remove the following sections
.
SSL section
.
Application DefaultWebApp section
.
Certificate application section
Add the following Application and Startup Class
sections:
.
Applications (add within the Domain xml parameters)
Application Deployed="true"
Name="suppliers"
Path="{ACTUAL_PATH_TO_PUBLIC_HTML}"
TwoPhase="false">
<WebAppComponent Name="suppliers"
Targets=" gdsserver1 "
URI="suppliers"/>
</Application>
<Application
Deployed="true" Name=" demand " Path="./applications"
StagedTargets=""
TwoPhase="false">
<WebAppComponent Name=" demand " Targets="
gdsserver1 " URI=" demand
.war"/>
</Application>
.
Startup Class (add within the Domain xml parameters)
<StartupClass
ClassName="austin.appsvr.current.admin.RemoteWeblogic"
FailureIsFatal="true"
Name="RemoteWeblogic" Targets=" gdsserver1 "/>
Change DefaultWebApp
.
Change the DefaultWebApp in the WebServer field from DefaultWebApp to demand
Note :
Change it to supply if you are installing the supply component.
WebLogic Domain applications
directory
Copy
the war file into the new WebLogic Domain applications directory
To create a symbolic
link to the applications directory, delete the applications directory and
replace with a symbolic link to the GDS installable war file.
9.
Update Classpaths:
Make sure that the following jars
are present in the respective files / classpaths.
Entries to be present under
Classpath section of
<WPC_Install_Dir>/setup/ccd.rc.
#--------------------------------------------------------------------------------
# classpath
#--------------------------------------------------------------------------------
InitClasspath()
{
export
CCD_CLASSPATH=
AddJar $TOP/jars/ccd_svr.jar
AddJar <GDS
Installed Directory>/jars/cgd_svr.jar
AddJar <GDS
Installed Directory>/jars/com.ibm.mqbind.jar
AddJar <GDS
Installed Directory>/jars/connector.jar
AddJar <GDS
Installed Directory>/jars/fscontext.jar
AddJar <GDS
Installed Directory>/jars/jms.jar
AddJar <GDS
Installed Directory>/jars/jndi.jar
AddJar <GDS
Installed Directory>/jars/providerutil.jar
AddJar <GDS
Installed Directory>/etc/messaging/jars/gds-object-mapping.jar
AddJar <GDS
Installed
Directory>/etc/messaging/jars/gds-datapool-properties.jar
AddJar <GDS
Installed Directory>/etc/messaging/jars/gds-message-registry.jar
AddJar <GDS
Installed Directory>/etc/messaging/jars/xbean.jar
AddJar <GDS
Installed Directory>/etc/messaging/jars/commons-jxpath-1.2.jar
AddJar <GDS
Installed Directory>/etc/messaging/jars/gds-data-mapping.jar
AddJar <GDS
Installed Directory>/etc/messaging/jars/migrationexpimp.jar
AddJar
<GDS_Install_Dir>/etc /ajax_jars/jsonrpc-cvs.jar
#--------------
JARs for Transora Connector only -----------#
AddJar <GDS
Installed
Directory>/etc/messaging/jars/transora_r5_2v3_request.jar
AddJar <GDS
Installed
Directory>/etc/messaging/jars/transora_r5_2v3_response.jar
# ---------------
JARs for UCCNet Connector only ------------#
AddJar <GDS
Installed Directory>/etc/messaging/jars/uccnet241_demand13.jar
# ---------------
JARs for WWRE Connector only
AddJar <GDS
Installed Directory>/etc/messaging/jars/wwre1.3_inbound.jar
AddJar <GDS
Installed Directory>/etc/messaging/jars/wwre1.3_outbound.jar
Append the following entries to the
Classpath at <WAS> Application Servers >
GDS_Application_server > Process Definition > Java Virtual
Machine.
<GDS Installed
Directory>/etc/messaging/jars/gds-object-mapping.jar
<GDS Installed
Directory>/etc/messaging/jars/gds-datapool-properties.jar
<GDS Installed
Directory>/etc/messaging/jars/gds-message-registry.jar
<GDS Installed
Directory>/etc/messaging/jars/xbean.jar
<GDS Installed
Directory>/etc/messaging/jars/commons-jxpath-1.2.jar
<GDS Installed
Directory>/etc/messaging/jars/gds-data-mapping.jar
<GDS Installed
Directory>/etc/messaging/jars/uccnet241_demand13.jar
<GDS Installed
Directory>/etc/messaging/jars/
transora_r5_2v3_response.jar
<GDS Installed
Directory>/etc/messaging/jars/
transora_r5_2v3_request.jar
<GDS Installed
Directory>/etc/messaging/jars/
wwre1.3_inbound.jar
<GDS Installed
Directory>/etc/messaging/jars/
wwre1.3_outbound.jar
<GDS Installed
Directory>/etc/ajax_jars/jsonrpc-cvs.jar
Note :
After the JARs are appended in WAS Classpath, the changes need to be saved
.
Append to the Classpath at
<WAS> Application Servers > WPC_Application_server >
Process Definition > Java Virtual Machine.
<GDS Installed
Directory>/jars/cgd_svr.jar
<GDS Installed
Directory>/jars/com.ibm.mqbind.jar
<GDS Installed
Directory>/jars/connector.jar
<GDS Installed
Directory>/jars/fscontext.jar
<GDS Installed
Directory>/jars/jms.jar
<GDS Installed
Directory>/jars/jndi.jar
<GDS Installed
Directory>/jars/providerutil.jar
<GDS Installed
Directory>/etc/messaging/jars/gds-object-mapping.jar
<GDS Installed
Directory>/etc/messaging/jars/gds-datapool-properties.jar
<GDS Installed
Directory>/etc/messaging/jars/gds-message-registry.jar
<GDS Installed
Directory>/etc/messaging/jars/xbean.jar
<GDS Installed
Directory>/etc/messaging/jars/commons-jxpath-1.2.jar
<GDS Installed
Directory>/etc/messaging/jars/gds-data-mapping.jar
<GDS Installed
Directory>/etc/messaging/jars/uccnet241_demand13.jar
<GDS Installed
Directory>/etc/messaging/jars/transora_r5_2v3_response.jar
<GDS Installed
Directory>/etc/messaging/jars/transora_r5_2v3_request.jar
<GDS Installed
Directory>/etc/messaging/jars/wwre1.3_inbound.jar
<GDS Installed Directory>/etc/messaging/jars/wwre1.3_outbound.jar
<GDS Installed
Directory>/etc/ajax_jars/jsonrpc-cvs.jar
Note:After the JARs are added in WAS Classpath, the changes need
to be saved to the
Mater
Configuration.
Example on AIX:
/home/gdsuser/gds12/setup/cgd_svr.jar
/home/gdsuser/gds12/etc/messaging/jars/gds-datapool-properties.jar
10. Modify the common.properties file located in <WPC_Install_Dir>/etc/default directory
to configure the database connection details for messaging.
.
Update the following existing properties:
.
.
db_maxConnection_appsvr=60
.
db_maxConnection_scheduler=50
.
db_maxConnection_workflowengine=50
.
.
Add the following:
.
db_maxConnection_appsvr_gdsmsg=30
.
db_maxConnection_scheduler_gdsmsg=10
.
db_maxConnection_workflowengine_gdsmsg=10
.
db_maxConnection_messaging=60
.
db_minConnection_messaging=4
.
db_maxConnection_messaging_gdsmsg=40
.
db_maxConnection_messaging_default=10
.
db_maxConnection_messaging_system=10
.
11. Modify the gds.properties
file located at <GDS Installed
Directory>
$TOP/etc/default directory for the
company_code, gds_app_type, admin_user, ACTIVE_DATA_POOL_ID. Set the parameter
DEFAULT_LANGUAGE to the appropriate value as documented in the gds.properties
file. The value for company_code should be the company name as created in
WebSphere
Product
Center.
Example on AIX:
For demand :
company_code=<Name of company>
admin_user=Admin
gds_app_type=Demand
ACTIVE_DATA_POOL_ID=UCCNet or WWREV6
DEFAULT_LANGUAGE=en
For supply:
company_code=<Name of company>
admin_user=Admin
gds_app_type=Supply
ACTIVE_DATA_POOL_ID =Transora
DEFAULT_LANGUAGE=en
Note: For a detailed description and configuration of all the
variables in the gds.properties and gds_system.properties file refer to the
section Appendix D : Variables in
gds.properties
Note: If you are installing a demand side application and want
to configure the custom workflows, refer to the Configuring custom workflows section in the
Configuration Guide. Also follow the steps as outlined in the post installation
tasks (creating soft links) section above.
You can
also copy the file publicationprocess.properties from GDS
$TOP/etc/processflow/<datapoolname>/publicationprocess.properties
to $WPC_INSTALL_DIR/etc/processflow/<datapoolname>/publicationprocess.properties
.
Example
location:
$TOP/etc/processflo/wwre/publicationprocess.properties
12. Verify the database connection is successful by the
executing the below script
< GDS Installed
Directory >
$TOP/bin/test_java_db.sh.
13. Verify the company has been created using WPC. To To load the data model, run the following script. Before
runnning the script, ensure that you stop all the services for WebSphere Product Center.
< GDS Installed
Directory > $TOP/src/db/schema/create/create_gds_schema.sh
This value for company_code should be same as specified in
gds.propeties.
After running creating the schema, run the following script
depending on the ACTIVE_DATAPOOL_ID
1.
If ACTIVE_DATA_POOL_ID=UCCnet
< > GDS Installed Directory >
>$TOP/src/db/schema/gds/DEMAND-SIDE/UCCNet/v241/loadUCCNetV241DataModel.sh--company_code=<Name of a company>
2.
If ACTIVE_DATAPOL_ID=WWREV6
< GDS Installed Directory
>
>$TOP/src/db/schema/gds/DEMAND-SIDE/WWRE/v6/loadWWREV6DataModel.sh - -company_code=<Name of a company>
3.
If ACTIVE_DATAPOOL_ID=Transora
< GDS Installed Directory
>
>$TOP/src/db/schema/gds/SUPPLY-SIDE/Transora/v50/loadTransoraV50DataModel.sh
--company_code=<Name of a
company>
Update the classpath with the above jar files
for the Application Server hosting
WebSphere
Product
Center and
restart WPC by running
14. the start_local_rmlogs.shscript located in the $WPC_INSTALL_DIR/bin/go
directory
>Update the CLASSPATH with the above jar files
>for the Application Server
hosting GDS and
15. restart GDS by running the start_appsvr.sh script
located in the >< GDS Installed Directory
>> >$TOP/bin/go/start directory to start GDS.
>
>
16.
Access GDS application with the
appsvr_port number as specified in the common.properties file.
For example, http://9.182.74.226:9706/Login.do.
Note: Ensure that all WPC services are running correctly by
running the script $WPC_INSTALL_DIR/bin/go/rmi_status.sh and also the GDS services by running
>< > GDS
Installed Directory >
$TOP/bin/go/rmi_status.sh.
Set the
following variables in the file Properties.xml to configure GDS
messaging:
Note: The path of Properties.xml file varies depending on the
ACTIVE_DATAPOOL_ID configured in gds.properties.
1. ACTIVE_DATAPOOL_ID=UCC Net
etc/messaging/xml/demand/uccnet/Properties.xml
2. ACTIVE_DATAPOOL_ID=WWREV6
etc/messaging/xml/demand/wwrev6/Properties.xml
3. ACTIVE_DATAPOOL_ID=Transora
etc/messaging/xml/supply/transora/Properties.xml
Refer to Appendix E for
a detailed listing of properties.xml
Locale/Language Specific
Configurations
All the locale specific
resource files are located into the < > GDS Installed
Directory
> >$TOP
directory. The GDS default installation will have resource files for locale
en_US. Create new resource files for all the required locales in the
< > GDS
Installed Directory
>
>$TOP/locales directory.
If the locale is French
(France) i.e. fr_FR, then create a directory fr_Fr and copy the files within
en_US
folder to the newly created folder. Make the necessary changes to the files in
the newly created directory.
.
For more details, refer to Select
Languages in the Lookup table and>Configure
Language Specific Attributes under WebSphere Product Center
Configuration
.
>
>
Ch 4
Configuring the messaging
receiver
This chapter explains the necessary configuration of the
JMS receiver.
Open >< > GDS Installed
Directory
>
>$TOP/etc/default/gds_system.properties file and set the value of the
variable SEND_TO JMS to TRUE.
Change directory to >< > GDS Installed
Directory
>
>$TOP/etc/messaging/xml/. Choose demand/supply folder as per the
application installed, then go to the uccnet/transora/wwrev6 folder with respect
to your requirement and set the values for the parameters
<inBoundQueueName>,
<outBoundQueueName>and<queueConnectionFactory> in the file
Properties.xml.
For Example:
For Inbound message:
<inBound>
<transport>
<jms>
<inBoundQueueName>XML_OUT</inBoundQueueName>
<initialContextFactory>com.sun.jndi.fscontext.RefFSContextFactory</initialContextFactory>
<queueConnectionFactory>ptpQcf</queueConnectionFactory>
</jms>
</transport>>
_
_
</inBound>
Similarly for Outbound message:
<outBound>
<transport>
<jms>
<outBoundQueueName>XML_IN</outBoundQueueName
>
<initialContextFactory>
com.sun.jndi.fscontext.RefFSContextFactory</initialContextFactory>
<queueConnectionFactory>ptpQcf</queueConnectionFactory>
</jms>
</transport>
<outBound>
In the above example:
XML_OUT: this will be the queue
name for inbound message
XML_IN: this will be the queue name for outbound
message.
ptpQcf: this will the queue factory name.
To Start/Stop JMSReceiver :
To start JMSReceiver
, go to $>< GDS Installed
Directory > TOP/bin directory and execute
:
.
gdsmsg.sh start
To abort the JMSReceiver, go to < GDS Installed
Directory>> $TOP/bin directory and execute
.
gdsmsg.sh abort
To check the status of the JMSReceiver, go to <> GDS Installed
Directory > $TOP/bin directory and
execute
.
gdsmsg.sh status
Note: Before starting the receiver, make sure the .binding file
in the < GDS Installed Directory>>/etc/default directory has been updated with the queue
configured above.
This chapter provides
information about security and user management in IBM Global Data
Synchronization for WebSphere Product Center.
WebSphere Product Center 5.2.1-IF003 is used for setting the security and the roles
for the various users.
Note: For a sample implementation of security refer to
Appendix A for Supply component and Appendix B for Demand
component.
Topics:
.
Security
.
Steps to configure Security
Security requirements for
IBM Global Data Synchronization for WebSphere Product Center are divided into
two parts. They are:
.
Functional Security
.
Data Security
Functional Security
controls the actions that can be performed by the user on the System. Depending
on the privileges granted, the user will be able to perform a limited set of
actions. Functional Security is implemented through Access Control Groups
feature in WebSphere Product Center.
Data Security is
implemented using the Roles and Selections feature in WebSphere Product Center. Security is
provided for the Trade Items, Trade Item Links, Trading Partners, Target Markets
and Transactions.
Relationship
between ACGs, Roles, Selections and Users
A role is a collection of
tasks, services, and information for a user or a group of users. The role
defines which service and information the user should be able to access and the
activities that can be performed by the user. The role also defines the
visualization of the contents and the navigation structure within the
solution.
The Access Control Group
is used to control the access levels for each role. The ability to control a
user's access to view, edit, and delete entities can be restricted based on the
access privilege definition of the role that is assigned to the user.
Multiple ACG's can be
associated with multiple roles.
A selection is then used
to associate ACG's with the required entities. Therefore, a single selection can
be made available to a specific ACG and all roles that are part of the ACG will
have access to that entity (such as a catalog or a hierarchy). A user is allowed
access to an entity once they are assigned to the role.
The steps to set the
security are:
1.
Log on to WebSphere Product Center
2.
Create a Role
3.
Create an Access Control Group (ACG)
4.
Create Selections
5.
Provide Data Access
Privileges
6.
Create User
To create a new
Role:
1.
Log on to WebSphere Product Center.
2.
Go to Data Model Manager >
Security > Role Console.
3.
Click New.
4.
Type the name for the role.
5.
From the drop-down menu
select default ACG and provide the
access privileges for this role.
6.
Save the settings.
The roles and Access
Control Groups (ACG) that are set in WebSphere Product Center are applied in IBM
Global Data Synchronization for WebSphere Product Center.
Create an Access Control Group (ACG)
These are sample types of
Access Control Groups:
.
[UDEX CAT SPECIFIC] ACG : This is the UDEX category specific access control
group. The available roles can be:
.
[UDEX CAT SPECIFIC] Global Brand Manager
.
[UDEX CAT SPECIFIC] Global Product Executive
.
[UDEX CAT - TM SPECIFIC] Brand Manager
.
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] Product Executive
.
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] User
.
[UDEX CAT - TM SPECIFIC] Variant Publisher
.
[TM Specific] ACG : This is the target market specific access control group. The
available roles can be:
.
[UDEX CAT - TM SPECIFIC] Brand Manager
.
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] Product Executive
.
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] User
.
[UDEX CAT - TM SPECIFIC] Variant Publisher
.
[TM Specific] Marketing Manager
To create new
ACGs:
1.
Log on to WebSphere Product Center.
2.
Go to Data Model Manager >
Security > Access Control Groups > Access Control Group Console.
3.
Click New.
4.
Type the name for the ACG. From the
Role drop-down menu, select the role that is created in step2.
5.
Provide access privileges for the
default ACG. Select the checkboxes for Catalog list, Hierarchy list, Selection
list, and Selection Measures list.
6.
Save the settings.
The created ACGs are
linked to Selections that are created through WebSphere Product Center. These Selections
are used to achieve Category and Target Market based security.
When a Selection is
created, it is associated with an ACG, a catalog, and a hierarchy. So, for
achieving category-level security, a Selection is created for [UDEX CAT SPECIFIC] ACG, Global_Catalog and
UDEX_Hierarchy_UCCNet hierarchy. Similarly, for Target Market based security,
Selection is created for [TM Specific] ACG, Global_Local_Catalog and
Target_Market hierarchy.
Once the Selection is
created, the required Categories are selected. Once this is done, the users
associated with the ACGs will have visibility into only those categories/ target
markets that are selected in the Selection.
Note: All Categories (Internal and UDEX) that are accessible
through selections must be enabled. If that is not done, the pagination will not
be proper, that is the result size may not correspond to the defined page
size.
The following selections
need to be done:
Selection configurations common to both Demand
and Supply
Global Catalog
Selection
1.
Go to Product Manager >
Selections > Selection Console. Click New
Basic Selection.
2.
Select Global
Catalog from the drop-down.
3.
Select the version.
4.
Select the Access Control Group.
5.
Select the hierarchy as
.
UDEX_Hierarchy_UCCNet, if classification scheme in gds.properties is
UDEX_Hierarchy_UCCNet.
.
GPC_Hierarchy if, classification scheme is GPC_Hierarchy
.
Internal_Hierarchy, if classification scheme is Internal_Hierarchy.
6.
Type a name for the selection and then
select the categories.
7.
Click Save to save the selection.
Global Local Catalog
Selection
1.
Go to Product Manager >
Selections > Selection Console. Click New Basic Selection.
2.
Select Global Local
Catalog from the drop-down
3.
Select the version.
4.
Select the Access Control Group.
5.
Select the hierarchy as
Target_Market_Hierarchy. All the target
markets under Global Local Catalog Hierarchy are displayed.
6.
Type a name for the selection and then
select the categories.
7.
Click Save to save the selection.
Trading Partner Catalog
Selection
1.
Go to Product Manager >
Selections > Selection Console.
Click New Basic Selection.
2.
Select Trading Partner Catalog
from the drop-down.
3.
Select the version.
4.
Select the Access Control Group.
5.
Select the hierarchy as
Target_Market_Hierarchy. All the target
markets under Target_Market_Hierarchy are displayed.
6.
Type a name for the selection and then
select the target markets.
7.
Click Save to save the selection.
Information Provider
Hierarchy selection
1.
Go to Product Manager >
Selections > Selection Console. Click
New Basic Selection.
2.
Select Trading Partner Catalog
from the drop-down. Select the version.
3.
Select the Access Control Group.
4.
Select the hierarchy as
IP_Hierarchy. All the categories under
IP_Hierarchy are displayed.
5.
Select the default hierarchy as
'0000000000000'.
6.
Click Save to save the selection.
Demand-Side specific selections
In addition to the common
selections configurations, for demand side the following selection
configurations need to be performed in WebSphere Product Center.
Publication Object
Catalog Selection
1.
Go to Product Manager >
Selections > Selection Console. Click New Basic
Selection.
2.
Select Publication Object
Catalog from the drop-down.
3.
Select the version.
4.
Select the Access Control Group.
5.
Select the hierarchy as Dummy
Filter. All the categories under Dummy Filter are displayed.
6.
Type a name for the selection and then
select all the categories.
7.
Click Save to save the
selection.
UCCNET
specific
UCCNet Message Archive
Catalog Selection
1.
Go to Product Manager >
Selections > Selection Console. Click New Basic
Selection.
2.
Select UCCNet Message Archive
Catalog from the drop-down.
3.
Select the version.
4.
Select the Access Control Group.
5.
Select the hierarchy as
UCCNetMessageArchiveHierarchy. All the categories under UCCNet Message
Archive Catalog Hierarchy are displayed.
6.
Type a name for the selection and then
select all the categories including the unassigned category.
7.
Click Save to save the
selection.
WWRE
specific
WWRE Message Archive
Catalog Selection
1. Go to Product Manager > Selections > Selection
Console. Click New Basic Selection.
2. Select WWREMessageArchiveCatalog from the drop-down.
3. Select the version.
4. Select the Access Control Group.
5. Select the hierarchy as WWREMessageArchiveHierarchy.
All the categories under WWRE Message Archive Catalog Hierarchy are
displayed.
6. Type a name for the selection and then select all the
categories including the unassigned category.
7. Click Save to save the selection.
To provide access
privileges to the attribute groups for the Global Catalog
1. Go to Data Model Manager > Security >
Access Privileges > Catalog Access Console.
2. Click on the new button located at the top of
the screen
3. From the drop down menu, Select Catalog as
Global_Catalog
4. .Select Role
5. Select the Privileges and click on the Add Editable
or Add Viewable button depending on the privilege
6. Click Save Click
Save to save the selection.
To provide access
privileges to the attribute groups for the Global Local Catalog
1. Go to Data Model Manager > Security >
Access Privileges > Catalog Access Console.
2. Click on the new button located at the top of
the screen
3. From the drop down menu, Select Catalog as
Global_Local_Catalog
4. .Select Role
5. Select the Privileges and click on the Add Editable
or Add Viewable button depending on the privilege
6. Click Save to save the selection
For information about
creating the user, refer the section
Configure Users and Roles in Chapter 4 :>Websphere
WebSphere Product Center Configuration.
Ch 6
WebSphere Product Center Configuration
This chapter details the
configurations that you can make for GDS, according to your requirement. These
configurations need to be made in WebSphere Product Center version 5.2.0 IF2.
The settings reflect in the IBM Global Data Synchronization for WebSphere Product Center
solution.
Note: You need to have working knowledge of WebSphere Product Center version
5.2.1-IF003
Topics:
Configurations common for
both demand and supply component
.
Modify or Move the Names of Attributes
.
Modify or Move the Names of Attribute
Groups
.
Configure Target Markets
.
Configure
Target Market Sub-Division Codes
.
Select
Languages in the Lookup table
.
Configure
Language Specific Attributes
.
Configure
Trade Item Status
.
Configure Enrichment Completion Criteria
.
Configure
Item Data Compliance Check
.
Configure Approval Process
.
Configure Classification Scheme
.
Configure Users and Roles
.
Configure Workflows
. Mapping Between Internal Category and the UDEX
Category
.
Mapping
Between Internal Category and the GPC Category
.
Configuring Interoperability Attributes
To configure, you need to
log on to WebSphere Product Center version 5.2.1-IF003.
Modify or Move the Names of
Attributes
You can change the names
of global and global-local attributes that is displayed in the IBM Global Data
Synchronization for WebSphere Product Center application.
The Global Attributes of
the data pool are mapped to the Global Catalog in WebSphere Product Center.
To change the names of
Global Attributes:
1.
Go to Product
Manager>Catalogs>Catalog Console. You can also modify the spec from the
Data Model Manager> Specs/Mappings>Specs Console.
2.
Click
Global_Attributes_Spec next to
Global_Catalog.
3.
Click Edit to edit the
Global_Attribute_Spec.
4.
Click on the plus symbol next to
Global_Attributes_Spec to add a new attribute.
5.
To modify the names of the attributes,
click on the attribute name.
6.
To move an attribute, click on the
upward arrow to move the attribute up or the downward arrow to move the
attribute down.
7.
To add attributes, click on the plus
symbol next to the attribute name for which you want to add a
attribute.
8.
To delete an attribute, click on the
delete button for the attribute that you want to delete.
9.
Click Save to save your
changes.
The Global-local
Attributes of the data pool are mapped to the Global-Local Catalog in
WebSphere
Product
Center.
To change the names of
Global-Local Attributes:
1.
Go to Product
Manager>Catalogs>Catalog Console. You can
also modify the spec from the Data Model Manager> Specs/Mappings>Specs
Console.
2.
Click Global_Local_Attributes_Spec next
to Global_Local_Catalog.
3.
Click Edit to edit the
Global_Local_Attribute_Spec.
4.
Click on the plus symbol next to
Global_Local_Attributes_Spec to add a new attribute.
5.
To modify the names of the attributes,
click on the attribute name.
6.
To move an attribute, click on the
upward arrow to move the attribute up or the downward arrow to move the
attribute down.
7.
To add attributes, click on the plus
symbol next to the attribute name for which you want to add a
attribute.
8.
To delete an attribute, click on the
delete button for the attribute that you want to delete.
Modify or Move the Names of
Attribute Groups
Multiple attributes can be
arranged into a named group. Attribute groups are defined and named in one place
so that they can be reused and easily updated. For example, in the GDS, all
attributes related to Logistics are grouped under the Logistics tab. The names
of these groups can be modified. The modifications are done in WebSphere Product Center and they reflect
in GDS.
To change the names of
Attributes Groups:
1.
Go to Data Model
Manager>Attribute Collections>Attribute Collection Console.
2.
Click on the attribute group that you
want to modify. The list of specs associated with the group is
displayed.
3.
Under Specs in Collection,
double-click on the spec. The list of attributes for that spec is displayed
under Attributes for Collection in Spec.
4.
To delete the attribute(s), select
those attributes that you want to delete, and click Remove selected
attributes.
5.
To add attributes, click Search.
The list of attributes is displayed.
6.
Select the attributes that you want to
add and click Selected. The selected attributes are added to the
attribute collection.
7.
Click Save to commit your
changes.
Configure Target Markets
The list of target markets
that are accessible in the IBM Global Data Synchronization for WebSphere Product Center solution is preset
using WebSphere Product Center.
To setup the Target
Markets:
1.
Go to Product Manager>Lookup
Tables> Lookup Table Console.
2.
Select Target_Market_Lookup and
click on the search button.
3.
You can add new target markets, edit or
remove existing target markets.
4.
You can also enable or disable target
markets.
5.
Save your settings.
All these changes should reflect in the IBM Global Data
Synchronization for WebSphere Product Center application.
Configure
Target Market Sub-division Codes
The list of Target Market
sub- divisions are accessible in the IBM Global Data Synchronization for
WebSphere
Product
Center
solution and can be preset using WebSphere Product Center.
To setup the Target
Markets sub-division codes:
1. Go to the drop down box and select
Target_Market_Hierarchy under the Hierarches
Hierarchies table.
2. In the 'Show real time search' area, a list of
Target Markets and their sub-divisions are mentioned. Select the appropriate one
using the first letter of the State as your search criteria.
Example: for US-CA, search under ' C '
3. Under Target_market_Spec, check the enabled
box.
Select Languages in the Lookup table
1.
Go to Product Manager>Lookup
Tables> Lookup Table Console.
2.
Select Languages_Lookup and
click on the search icon. The Lookup Table is displayed.
3.
Sort the key field and click on the
edit button against the key that you want to select.
4.
Check selected and Save
your settings.
The chosen languages will be displayed in Languages
field in the Create Item screen in the GDS application.
For a particular language
,for example,en_US, there is a possibility that the incoming message may contain
variations such as:en-Us, en_Us or en. To synchronize the messages to a single
language, the incoming language has to be mapped to the appropriate locale .
To map:
1. Go to Product
Manager> Lookup
Tables >Lookup Table
Console.
2. Select Languages _ Locale _Lookup and click on the search
button, the Languages lookup Locale table is displayed.
3. Click on the key that you want to map
4. Modify the value to where you want it mapped.
5. Click save .
WebSphere Product Center provides the ability to localize attribute values for any
catalog attribute or hierarchy node. Locales are created based on
language/country pairs, which provide variances across countries (that is, U.S.
English, British English). You can localize a single attribute value or display
name.
To localize the Language
Specific Attributes:
1.
Go to Data Model
Manager>Security> Company Attributes.
2.
Select the language/country pairs
supported.
3.
You can also remove the supported
languages and countries.
4.
Click Save to save the
spec.
5.
Go to the spec which contains Global
and Global Local attributes, and enable the Localized option. The set of
locales are displayed. Select the locale and click Add.
6.
Click on the attribute to localize the
attribute's display name.
7.
Enable the Localized option under
Attribute Collection Associations. The attribute is localized for all the
locales.
8.
Save your settings.
9.
To view these localized attributes data
from the UI perspective go to Home->My Settings and Add Locales
from the Available Locales to Selected Locales and save the settings.
Configure Trade Item Status
A trade item goes through
a number of statuses in the IBM Global Data Synchronization for WebSphere Product Center application. If
the status display name is changed in WebSphere Product Center, the same will be
reflected in IBM Global Data Synchronization for WebSphere Product Center
UI.
To change the display name
for the Trade Item Status:
1.
Go to Product Manager>Lookup
Tables> Lookup Table Console.
2.
For Item_Status_Lookup and click
on the search button.
3.
Click on the status name or the
Edit icon to rename the status.
4.
Click Save to commit the
changes.
Configure Enrichment Completion
Criteria
To configure the
Enrichment Completion Criteria:
1.
Go to Data Model
Manager>Attribute Collections>Attribute Collection Console.
2.
Click Required.
3.
Under Specs in Collection,
double-click on the spec. The list of attributes for that spec is displayed
under Attributes for Collection in Spec.
4.
To delete the attribute(s), select
those attributes that you want to delete, and click Remove selected
attributes.
5.
To add attributes, click Search.
The list of attributes is displayed.
6.
Select the attributes that you want to
add and click Selected. The selected attributes are added to the
attribute collection.
7.
Click Save to commit your
changes.
Configure Approval Process
The approval process for
trade items, trade item links, and trading partners can be automated. This is
done by setting the required approval process to ON or OFF in the gds.properties
file.
To set the Approval
Process:
1.
At the command prompt, type
><> GDS
Installed Directory
>
$TOP/etc/default/gds.properties.
2.
Change the settings to ON or
OFF.
Configure Classification Scheme
Classification scheme is a
hierarchical structure of product categories. Currently, along with an internal
classification scheme, IBM Global Data Synchronization for WebSphere Product Center supports the UDEX
classification scheme and GPC scheme.
The configuration can be
done through the hierarchy mapping console or selecting the hierarchy from the
left navigation pane.
To configure the
Classification Scheme:
1.
Go to ><> GDS Installed
Directory
>
$TOP/etc/default/gds.properties
file using any editor.
2.
To configure the classification scheme,
set the values Internal_Classification_Scheme to any one of the following three values in the file
gds.properties
.
Internal _hierarchy
.
UDEX_Hierarchy_UCCNET
.
GPC_Hierarchy.
3.
Restart the server.
By default the primary
classification scheme is Internal Hierarchy classification.
To associate an attribute
collection with the classification scheme:
1.
Go to Product Manager> Hierarchy
console.
2.
Select the classification scheme that
you want to associate attribute collection to Internal internal _hierarchy.
3.
In the right navigation, select the
user defined core attribute collection. For example if you choose internal
hierarchy the attribute collection is internal hierarchy attributes.
To enable the categories
in a classification scheme:
1.
From the left navigation pane, select
the hierarchy.
2.
Select a category at the leaf node.
In the above example, under internal hierarchy alcohol is
the leaf node and under alcohol Cocktails and Wine are leaf nodes.
3.
In the right pane displayed for that
category, select the check box for Enabled for each of these leaf
nodes.
This completes the configuration of the classification
scheme.
The roles are pre-seeded
in the solution. The users need to be created. For a sample scenario of
configuring roles, refer the Appendix-Sample Scenarios.
To create a new
user:
1.
In the left navigation pane, from the
drop-down menu, select Default Organization Hierarchy. The hierarchy is
displayed under the drop-down menu.
2.
Click on the plus sign to expand
Default Organization Hierarchy.
3.
Point the cursor on Default
Organization. Right-click and select Add User.
4.
Fill in the fields under User
Profile.
5.
Specify the password for this
user.
6.
From the list of roles that are
displayed, select a role for this user.
Note: GDS_ALL_WF_Role
has to be selected as a default selection along with the other role.
7.
Click Save.
8.
Refresh the left navigation
pane.
9.
Click on view users. The User
Console displays the newly created user.
10. Enable the new user.
Configure Workflows
During solution setup, you
have the option to turn on/off the global attributes enrichment process, variant
attribute enrichment process, and the approval process. The following list of
approval process can be turned on/off. If any of the approval process is turned
OFF, then it is automated within the solution.
.
New Item Approval
.
Modify Item Approval
.
Delete Item Approval
.
New Link Approval
.
Delete Link Approval
.
Modify Link Approval
.
New Trading Partner Approval
.
Modify Trading Partner Approval
.
Delete Trading Partner Approval
To configure the
workflows:
11. Go to < GDS Installed Directory >
$TOP/etc/default/gds.properties
file using any editor.
12. For configuring the global enrichment, set
global_enrichment to true or false. Similarly for switching the variant
enrichment, set local_enrichment to true or false.
13. For configuring the approval processes, set the respective
process to ON or OFF.
14. Restart the server.
Note: This configuration can be done when installing the
solution using the Install Shield.
The list of information
providers that are accessible in the IBM Global Data Synchronization for
WebSphere
Product
Center
solution is preset using WebSphere Product Center.
To configure the
Information Providers:
1.
In the left navigation pane, from the
drop-down menu, select Trading_Partner_Catalog. The hierarchy is
displayed under the drop-down menu.
2.
Right-click on the country and click
Add Item. The details page for the trading partner is
displayed.
3.
Specify the following:
a.
In the Name field, type the name for
the Information Provider.
b.
In the GLN field, type the Global
Location Number.
c.
In the GLN Identifier field, select any
of the available options. Options available are Manufacturer, Exchange,
Retailer, and Supplier.
d.
In the Country field, type the country
of the Information Provider.
e.
Specify the status as Approved and the
TP status as Active.
f.
Select the item type as Information
Provider.
4. Click Save to save the settings.
Note: When creating selections, ensure that the Information
Provider that is configured is selected. For more information, refer Create
Selections in Chapter 4 : Administration.
Configure Trade Item
Data Compliance Check [for supply side]
Once the trade item has been
enriched, it should be submitted for a compliance check. The validation rules
for this compliance check are setup using WebSphere Product Center.
To configure Trade Item Data
Compliance Check:
1.
Go to Data Model
Manager>Scriptings>Scripts Console.
2.
From the drop-down menu, select
Distribution Script. The Scripts Console is displayed.
3.
Click on the Edit icon next to
Trade Item Link Validation or Trade Item Validation.
4.
Edit the script and click Save
to commit the changes.
Internal Category is the
categories maintained by the organization. UDEX-UK category is the category in
the UDEX UK data pool.
To map the attributes
between the Internal Category and the UDEX Category:
5.
Go to Product Manager>Hierarchy
Maps>Hierarchy Mapping Console.
6.
You can create a new map or modify an
existing map.
7.
Click New to create a new map.
8.
Select the Internal Category and then
the UDEX category. This maps the selected internal category to the UDEX
category.
9.
The settings are saved
automatically.
Note: Ensure that mapping to UDEX Categories are done only for
the Categories accessible by a user. Also, the field
"udex_to_internal_hierarchy_mapping_without_security_breach" should be set to
true in the gds.properties file. If this is not set to true, there will be a
performance penalty.
Mapping
between Internal Category and the GPC Category (only for supply-side)
Internal Category is the
categories maintained by the organization. GPC category is the category offered
by the global registry GS1. If your organization is GS1 enabled then you can map
the internal category to the GPC category.
To map the attributes
between the Internal Category and the UDEX Category:
1. Go to Product Manager>Hierarchy Maps>Hierarchy
Mapping Console.
2. You can create a new map or modify an existing
map.
3. Click New to create a new map.
4. Select the Internal Category and then the GPC category.
This maps the selected internal category to the GPC category.
5. The settings are saved automatically.
Internal Category is the
categories maintained by the organization. To map the attributes between the
UDEX Category and the Internal Category:
1. Go to Product Manager>Hierarchy Maps>Hierarchy
Mapping Console.
2. You can create a new map or modify an existing
map.
3. Click New to create a new map.
4. Select the UDEX Category and then the internal category.
This maps the selected UDEX category to the internal category.
5. The settings are saved automatically.
Internal Category is the
categories maintained by the organization. GPC category is the category offered
by the global registry GS1.
To map the attributes
between the GPC Category and the Internal Category:
1. Go to Product
Manager>Hierarchy Maps>Hierarchy Mapping Console.
2. You can create
a new map or modify an existing map.
3. Click New to create a new map.
4. Select the GPC Category and then the internal category.
This maps the selected GPC category to the internal category.
5. The settings are saved automatically.
Note:
The internal category mentioned above is in accordance with the classification
scheme set in gds.properties.
Configure Interoperability Attributes- (only supply side)
Categories are defined for
different data pools. Currently, UDEX-UK and WWRE are supported.
To configure the
interoperability attributes:
1.
Go to Product Manager>Lookup
table>Lookup Table Console.
2.
Choose the Interoperability Lookup and
table and click on the Browse Lookup table icon.
3.
Click on the Edit icon for
interoperability. For example: WWRE Interoperability
4.
Enable the interoperability value and
click Save to save the values
Note: All the UDEX-UK interoperability attributes are not pre
-seeded. For attributes that are not preseeded
pre-seeded, refer Transora UDEX-UK interoperability.
1.
In the left navigation pane, from the
drop-down menu, select the data pool for which you want to configure the
attributes. The list of categories for the selected data pool is
displayed.
2.
Click on a category. The details for
the category are displayed on the right side.
3.
If the specs are pre-seeded, edit the
spec.
4.
If there are no specs, you need to
create a new spec.
5.
Once the spec is created, add it to the
attribute collection.
This chapter describes how to uninstall WebSphere
Product Center . The uninstaller can run using the Graphical Uninstaller or
silently from the command line.
The Graphical Uninstaller presents you with a
wizard that allows you to uninstall Global Data Synchronization forWebSphere
Product Center . The Uninstaller is invoked by running executables from the
Global Data Synchronization for WebSphere Product Center installation
directory.
Example in UNIX
This section describes how to invoke Uninstaller
for WebSphere Product Center on a Unix environment.
If you are running CDE on the UNIX computer
: If you are running the Common Desktop Environment (CDE) and working on the
UNIX computer directly then you can navigate to the uninstallation directory of
a Global Data Synchronization for WebSphere Product Center installation and
double-click the .bin file to invoke the Uninstaller.
If you are connecting to the UNIX computer
through X emulation software : If you are using a Windows computer to
connect to the UNIX computer through X emulation software do the following to
invoke the installer:
1. Configure your environment for X emulation
software.
2. Execute <install
location>/_uninst/uninstaller.bin
The graphical uninstaller starts on the Windows
computer that you are using to connect to the UNIX computer.
Invoking the graphical uninstaller at the command line
To execute the graphical
uninstaller for WebSphere Product Center, execute the following command at the
command line:
<install
location>/_uninst/uninstaller.bin
The uninstaller attempts to clean
up the installation directory, except possibly for a log file, as well as any
files created by the user after the product was installed. For the cleanup of
the installation directory to take place, ensure that no shell, or application
is using the _uninst directory as its current directory, or locking it in any
other way (Graphical file managers for example that display the contents of the
_uninst directory, may or may not be locking the _uninst directory, so these
shells and applications should be closed, before invoking the uninstaller).
Do the following to uninstall
WebSphere Product Center using the graphical uninstaller:
1. At the
"Welcome" screen click Next.
2. The ">Summary "Summary screen lists the components that
will be uninstalled and the product directory from which they will be removed.
Verify the information and then click Next.
3. After the
uninstaller finishes successfully, click Finish.
The uninstaller attempts to clean
up the installation directory, except possibly for a log file, as well as any
files created by the user after the product was installed. For the cleanup of
the installation directory to take place, ensure that no shell, or application
is using the _uninst directory as its current directory, or locking it in any
other way (Graphical file managers for example that display the contents of the
_uninst directory, may or may not be locking the _uninst directory, so these
shells and applications should be closed, before invoking the uninstaller).
To perform a silent uninstallation
for WebSphere Product Center, execute the following command at the command
line:
<install
location>/_uninst/uninstaller.bin
-silent
This appendix provides
information about the various Roles, Access Control Groups (ACGs), and
Selections. It also provides the list of accessible features and operations that
can be performed by the respective roles. Keeping the sample scenario as an
example you can create various ACGs and assign roles.
Consider a company XYZ. This
company has four main departments such as Lighting, Consumer Electronics,
Software, and Components. Each of these departments has a Global Brand Manager.
They are:
.
Lighting Global Brand Manager
.
Consumer Electronics Global Brand Manager
.
Software Global Brand Manager
.
Components Global Brand Manager
Note: The naming convention is [UDEX CAT SPECIFIC] Global Brand
Manager. That is, Lighting is the UDEX specific category.
The Global Brand Managers are
responsible for creating a GTIN. Each of these Global Brand Managers has product
executives. Once the Global Brand Manager creates the GTIN, a notification is
sent to the product executives to enrich the global attributes. The respective
product executives are:
.
Lighting Global Product Executive
.
Consumer Electronics Global Product Executive
.
Software Global Product Executive
.
Components Global Product Executive
Note: The Global Brand Manager can also enrich some or all the
global attributes.
When all the product
executives have completed enriching the global attributes, only then is the
global enrichment process complete. A notification that the global enrichment
for the trade item is complete is sent to the Global Brand Manager.
Now, if company XYZ has
business relations with US, Holland, and Singapore, there will be
target market specific Brand Managers for each category. They are:
.
Lighting US Brand Manager
.
Lighting Holland Brand Manager
.
Lighting Singapore Brand Manager
.
Consumer Electronics US Brand Manager
.
Consumer Electronics Holland Brand Manager
.
Consumer Electronics Singapore Brand Manager
.
Similarly there will be target market specific Brand Managers for each category.
The Global Brand Managers will
send the notification to these target market specific Brand Managers to enrich
the variants. Each of the target market specific Brand Managers has Product
Executives. The Product Executives enrich the variant attributes. Once the
variant attributes have been enriched, a notification for variant enrichment
completion is sent to the brand managers.
The various roles that are
>preseeded pre-seeded in the IBM Global Data
Synchronization for WebSphere Product Center Supply solution are:
.
WebSphere Product Centre Administrator
.
Global Data Synchronization Administrator
.
[UDEX CAT SPECIFIC] Global Brand Manager
.
[UDEX CAT SPECIFIC] Global Product Executive
.
[UDEX CAT - TM SPECIFIC] Brand Manager
.
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] Product Executive
.
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] User
.
Links Publisher
.
[UDEX CAT - TM SPECIFIC] Variant Publisher
.
[TM Specific] Marketing Manager
Note: These roles can be changes based on your
requirements.
WebSphere Product Centre
Administrator
The WebSphere Product Centre
Administrator has access to the data model. Typically, the administrator is the
PSS user.
The operations that can be
setup for IBM Global Data Synchronization for WebSphere Product Center solution and
WebSphere
Product
Center are
provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Create
. Edit
. View
. Modify
. Delete
. Explore
. Create
Variant
. Delete
Variant
. Enrich
Global
. Enrich
Variant
. Approve
/Reject
. Publish
New Item
. Send
Initial Load
. Add
Item
. Synchronize
Changes
|
. Create
. Edit
. View
. List
. Modify
. Delete
. Explore
. Approve/Reject |
. Create
. Edit
. View
. List
. Modify
. Delete
. Approve/Reject
. Add
Item Link |
. Publish
Transactions
. View
Generated XML
. Item
Transactions
. Hierarchy
Transactions
. Trading
Partner Transactions |
. Publications
. Initial
Load
. Item
Add
. Item
Link Add
. New
Item Request
. Item
Change Request
. New
Item Hierarchy Request
. Item
Hierarchy Change Request
. New
Trading Partner Request
. Trading
Partner Change Request |
.Run
Publi-
cation Reports
.View
Publi-
cation Reports
.Run
Item Reports
.View
Item Reports
.Run
Trading Partner Reports
.View
Trading Partner Reports |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
. Edit
Catalog Views
. View
Items
. Add
Items
. Modify
Items
. Delete
Items
. Recategorize Items
. Summary
Items
. Export
Attributes>/p>
. Differences
. Rollback
. Search
. Delete
. Run
Preview Script |
. List
. Edit
Hierarchy Views
. View
Hierarchy Nodes
. Add
Hierarchy Nodes
. Modify
Hierarchy Node Attributes
. Delete
Hierarchy Nodes
. Recategorize
Hierarchy Nodes
. Summary
Hierarchy Nodes
. Specmap
Hierarchy Nodes
. Attributes
. Rollback
. Delete |
. List
. Edit
Rule
. Delete |
. List
. Perform
Import
. Delete |
. View
Items
. Add
Items
. Modify
Items
. Delete
Items
. Recategorize
Items
. View
Hierarchy Nodes
. Add
Hierarchy Nodes
. Modify
Hierarchy Node Attributes
. Delete
Hierarchy Nodes
. Recategorize
Hierarchy Nodes
. Specmap
Hierarchy Nodes |
. View
Files
. Delete
Files |
|
WebSphere Product Center |
|
Workflow |
Collaboration Area |
Spec |
Screen |
Script |
Scheduler |
|
. List
. Edit
. Delete |
. List
. Checkout
Entries |
. Modify
Spec
. Modify
Spec Map |
. View |
. Create
Modify Scripts |
. View
Company Jobs |
Global Data Synchronization
Administrator
The IBM Global Data
Synchronization for WebSphere Product Center administrator has access to all the functionalities in IBM
Global Data Synchronization for WebSphere Product Center and some of the
functionalities in WebSphere Product Centre such as import/export & user
management. The IBM Global Data Synchronization for WebSphere Product Center administrator does
not have access to the data model.
The IBM Global Data
Synchronization for WebSphere Product Center Administrator has access to the
following:
.
Notifications
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partners
.
Publish New Item, Send Initial Load, Add Item, Add Link, and Synchronize
Changes
.
Explore Transactions
.
Manage Items (Create GTIN, Create GTIN Variant (that is, target market and
Information provider), View/Edit GTIN Global Attributes, View/Edit Variant
Attributes, Enrich GTIN Global Attributes, Enrich Variant Attributes, Delete
GTIN, and Delete GTIN Variant)
.
Approve/Reject Items
.
Create/View/Edit/Delete/Approve Trading Partner
.
Import/Export Items, Item Links
.
User Management & Security
The operations that can be
setup for IBM Global Data Synchronization for WebSphere Product Center solution and
WebSphere
Product
Center are
provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Supply Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Create
. Edit
. View
. Modify
. Delete
. Explore
. Create
Variant
. Delete
Variant
. Enrich
Global
. Enrich
Variant
. Approve
/Reject
. Publish
New Item
. Send
Initial Load
. Add
Item
. Synchronize
Changes
|
. Create
. Edit
. View
. List
. Modify
. Delete
. Explore
. Approve/Reject |
. Create
. Edit
. View
. List
. Modify
. Delete
. Approve/Reject
. Add
Item Link |
. Publish
Transactions
. View
Generated XML
. Item
Transactions
. Hierarchy
Transactions
. Trading
Partner Transactions |
. Publications
. Initial
Load
. Item
Add
. Item
Link Add
. New
Item Request
. Item
Change Request
. New
Item Hierarchy Request
. Item
Hierarchy Change Request
. New
Trading Partner Request
. Trading
Partner Change Request |
. Run
Publi-
cation Reports
. View
Publi-
cation Reports
. Run
Item Reports
. View
Item Reports
. Run
Trading Partner Reports
. View
Trading Partner Reports |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
. List
. Perform
Import
. Delete |
. View
Items |
|
|
WebSphere Product Center |
|
Workflow |
Collaboration Area |
Spec |
Screen |
Script |
Scheduler |
|
|
|
|
. View |
. Create
Modify Scripts |
. View
Company Jobs |
[UDEX CAT SPECIFIC] Global Brand
Manager
The Global Brand Manager is
responsible for creating new trade items (global variant). The Global Brand
Manager can also edit local variant, delete an item and its local variant, and
has the privilege of approving/disapproving an item. There will be one Global
Brand Manager for each category.
The Global Brand Manager has
access to the following:
.
Notifications
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partners
.
Explore Transactions
.
Manage Items (Create GTIN, View/Edit GTIN Global Attributes, View/Edit Variant
Attributes, Delete GTIN, and Delete GTIN Variant)
.
Approve/Reject Items
.
View Trading Partner
.
Reports
The operations that the Global
Brand Manager can perform in IBM Global Data Synchronization for WebSphere Product Center solution and
WebSphere
Product
Center are
provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
|
. List
. Create
. Edit
. View
. Modify
. Delete
. Delete Variant
. Explore
|
. View
. List
. Explore
|
. Create
. Edit
. View
. List
. Delete
. Approve/Reject |
. Item Transactions
. Hierarchy Transactions
. Trading Partner
Transactions |
. New Item Request
. Item Change Request
. New Item Hierarchy Request
. Item Hierarchy Change
Request |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List |
. List |
. List |
|
. View Items |
. View Files
. Delete
Files |
[UDEX CAT Specific] Global Product
Executive
The Global Product Executive
can enrich GTIN global attributes and also view or edit the variant
attributes.
The Global Product Executive
has access to the following:
.
Notifications
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partners
.
Manage Items (View/Edit GTIN Global Attributes, View/Edit Variant Attributes,
and Enrich GTIN Global Attributes)
.
View Trading Partner
The operations that the Global
Product Executive can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Edit
. View
. Modify
. Explore
. Enrich
Global |
. List
. View
. Explore |
. List
. Create
. Edit
. View
. Modify
. Delete |
|
. New
Item Request |
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
|
[UDEX CAT : TM Specific] Brand
Manager
The [UDEX CAT : TM
Specific] Brand Manager can create, enrich, delete a variant of an item.,
approve, or disapprove the variant..
The Brand Manager has access
to the following:
.
Notifications
.
Quick Search, Basic Search , and Advanced Search for Trade Items, Trade Item
Links, and Trading Partners
.
Explore Transactions
.
Manage Items (Create GTIN Variant, View GTIN Global Attributes, View/Edit
Variant Attributes, Enrich Variant Attributes, and Delete GTIN Variant)
.
Approve/Disapprove GTIN Variant
The operations that the Brand
Manager can perform in IBM Global Data Synchronization for WebSphere Product Center and WebSphere Product Center are provided in
the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Edit
. View
. Modify
. Explore
. Create
Variant
. Enrich
Variant
. Delete
Variant
. Approve/Reject |
. List
. View
. Explore |
. View |
. Item
Transactions |
. New
Item Request
. Item
Change Request |
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
|
[UDEX CAT - TM - ATTR GROUP SPECIFIC] Product
Executive
The [UDEX CAT : TM : ATTR
GROUP SPECIFIC] Product Executive can enrich variant attributes.
The Product Executive has
access to the following:
.
Notifications
.
Quick Search, Basic Search , and Advanced Search for Trade Items, Trade Item
Links, and Trading Partner
.
Manage Items (View GTIN Global Attributes, View/Edit Variant Attributes, and
Enrich Variant Attributes)
.
View Trading Partner
The operations that the
Product Executive can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Edit
. View
. Modify
. Explore
. Enrich
Variant |
. List
. View
. Explore |
. List
. View |
|
. New
Item Request |
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
|
[UDEX CAT - TM - ATTR GROUP SPECIFIC]
User
The [UDEX CAT : TM : ATTR
GROUP SPECIFIC] User can only view GTIN global attributes, view variant
attributes and trading partner information.
The User has access to the
following:
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partner
.
Manage Items (View GTIN Global Attributes, View Variant Attributes)
.
View Trading Partner
The operations that the User
can perform in IBM Global Data Synchronization for WebSphere Product Center and WebSphere Product Center are provided in
the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. View
. Explore |
. List
. View
. Explore |
. List
. View |
|
|
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
|
Links Publisher
The Links Publisher can
publish the links to the data pool and has access to the following:
.
Notifications
.
Quick Search, Basic Search , and Advanced Search for Trade Items, Trade Item
Links, and Trading Partner
.
Add Link
.
Explore Transactions
.
Manage Items (View GTIN Global Attributes, View Variant Attributes)
.
View Trading Partner
The operations that the Links
Publisher can perform in IBM Global Data Synchronization for WebSphere Product Center and WebSphere Product Center are provided in
the table.
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. View
. Explore |
. List
. View
. Explore |
. List
. View
. Add
Item Link |
. Publish
Transactions
. View
Generated XML |
. Publications
. Item
Link Add
|
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
|
[UDEX CAT - TM SPECIFIC] Variant
Publisher
The [UDEX CAT - TM SPECIFIC]
Variant Publisher can publish the variants to the data pool and has access to
the following:
.
Notifications
.
Quick Search, Basic Search , and Advanced Search for Trade Items, Trade Item
Links, and Trading Partner
.
Publish New Item, Send Initial Load, Add Item, Synchronize Changes
.
Explore Transactions
.
Manage Items (View GTIN Global Attributes, View Variant Attributes)
.
View Trading Partner
The operations that the
Variant Publisher can perform in IBM Global Data Synchronization for
WebSphere
Product
Center and
WebSphere
Product
Center are
provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. View
. Explore
. Publish
New Item
. Send
Initial Load
. Add
Item
. Synchronize
Changes |
. List
. View
. Explore |
. List
. View |
. Publish
Transactions
. View
Generated XML |
. Publications
. Initial
Load
. Item
Add
|
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List |
. List |
. List |
|
. View
Items |
|
[TM Specific] Marketing Manager
The [TM Specific] Marketing
Manager can create, view, edit, delete, approve or reject a Trading Partner for
a specific target market.
The Marketing Manager has
access to the following:
.
Notifications
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partner
.
Explore Transactions
.
Manage Items (View GTIN Global Attributes, View Variant Attributes)
.
Create/View/Edit/Delete/Approve Trading Partner
The operations that the
Marketing Manager can perform in IBM Global Data Synchronization for
WebSphere
Product
Center and
WebSphere
Product
Center are
provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. View
. Explore |
. List
. Create
. Edit
. View
. Modify
. Delete
. Explore
. Approve/Reject |
. List
. View |
. Trading
Partner Transactions |
. New
Trading Partner Request
. Trading
Partner Change Request
|
. Run
Trading Partner Reports
. View
Trading Partner Reports |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
|
The following workflow roles
are preceded in the solution. The user needs to have these roles to do actions
related to workflows. When creating new users to do some action(s) in a
specified workflow, then that user should be assigned with a specific
role(s).
.
GDS_Approve_Item_WF_Role: This role is required to approve an item.
.
GDS_Approve_Modified_TP_WF_Role: This role is required to approve a modified
Trading Partner.
.
GDS_Approve_New_TP_WF_Role: This role is required to approve a new Trading
Partner.
.
GDS_Approve_TP_Deletion_WF_Role: This role is required to approve a deleted
Trading Partner.
.
GDS_Enrich_Global_Attributes_WF_Role: This role is required to enrich the global
attributes.
.
GDS_Enrich_Local_Attributes_WF_Role: This is required to enrich the local
attributes.
.
GDS_Modify_Global_And_Check_Compliance _WF_Role: This is required to change
global attributes of a registered item and perform the compliance check.
.
GDS_Approve_Modify_Global_Item _WF_Role: This role is required to approve
changes in global attributes of a registered item.
.
GDS_Modify_Local_And_Check_Compliance _WF_Role: This role is required to change
local attributes of a registered item and perform the compliance check.
.
GDS_Approve_Modify_Local_Item _WF_Role: This role is required to approve changes
in local attributes of a registered item.
.
GDS_Approve_ Modify_Link_WF_Role: This role is required to approve links. This
may be a new link approval or modify link approval or deletion link
approval.
Examples of UDEX Category and
Target Market Specific ACGs are provided in the following table.
|
ACG |
Roles |
|
|
ALCOHOL BASED MIXERS ACG |
ALCOHOL BASED MIXERS Global Brand Manager |
[UDEX CAT SPECIFIC] Global Brand Manager |
|
ALCOHOL BASED MIXERS Global Product Executive |
[UDEX CAT SPECIFIC] Global Product Executive |
|
ALCOHOL BASED MIXERS - US Brand Manager |
[UDEX CAT - TM SPECIFIC] Brand Manager |
|
ALCOHOL BASED MIXERS UK Brand Manager |
|
ALCOHOL BASED MIXERS - US - Logistics Product
Executive |
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] Product
Executive |
|
ALCOHOL BASED MIXERS - US - Measures Product
Executive |
|
ALCOHOL BASED MIXERS - US - Nutrition Product
Executive |
|
ALCOHOL BASED MIXERS - UK - Logistics Product
Executive |
|
ALCOHOL BASED MIXERS - UK - Measures Product
Executive |
|
ALCOHOL BASED MIXERS - UK - Nutrition Product
Executive |
|
US ACG |
ALCOHOL BASED MIXERS - US Brand Manager |
[UDEX CAT - TM SPECIFIC] Brand Manager |
|
ALCOHOL BREWING_MAKING KITS US Brand Manager |
|
ALCOHOL BASED MIXERS - US - Logistics Product
Executive |
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] Product
Executive |
|
ALCOHOL BASED MIXERS - US - Measures Product
Executive |
|
ALCOHOL BASED MIXERS - US - Nutrition Product
Executive |
|
ALCOHOL BREWING_MAKING KITS - US - Logistics Product
Executive |
|
ALCOHOL BREWING_MAKING KITS - US - Measures Product
Executive |
|
ALCOHOL BASED MIXERS - US - Logistics User |
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] User |
|
ALCOHOL BASED MIXERS - US - Measures User |
|
ALCOHOL BASED MIXERS - US - Nutrition User |
|
ALCOHOL BREWING_MAKING KITS - US - Logistics
User |
|
ALCOHOL BASED MIXERS - US Variant Publisher |
[UDEX CAT - TM SPECIFIC] Variant Publisher |
|
ALCOHOL BREWING_MAKING KITS US Variant
Publisher |
The following Selections have
been pre-seeded into the model.
|
Selection |
ACG |
Catalog |
Hierarchy |
Selected Categories |
|
UNET_ALCOHOL BASED MIXES/MIXERS |
Alcohol ACG |
Global_Catalog |
UDEX_Hierarchy_UCCNet |
. ALCOHOL
BASED MIX/
MIXERS
. ALCOHOL
BASED COCKTAIL/
MIX
. ALCOHOL
BASED MIXERS |
|
UNET_ANIMAL/PET ACCESSORIES OTHER |
Animal Pet ACG |
Global_Catalog |
UDEX_Hierarchy_UCCNet |
. ANIMAL/PET
ACCES-
SORIES OTHER
. ANIMAL/PET
ACCES-
SORIES OTHER
. ANIMAL/PET
ACCES-
SORIES OTHER VARIETY PACKS/SETS |
|
UNET_CEREAL GRAINS WITH ADDITIONS - DRY (SHELF
STABLE) |
Cereal Grains ACG |
Global_Catalog |
UDEX_Hierarchy_UCCNet |
. CEREAL
GRAINS WITH ADDITIONS - DRY (SHELF STABLE)
.
BULGUR WHEAT WITH ADDITIONS - DRY (SHELF STABLE)
.
CEREAL GRAINS OTHER WITH ADDITIONS - DRY (SHELF STABLE) |
|
TM_Africa |
Africa ACG |
Global_Local_Catalog |
Target_Market_Hierarchy |
. EG
. SA |
|
TM_NorthAmerica |
North America ACG |
Global_Local_Catalog |
Target_Market_Hierarchy |
. US
. CA |
This appendix provides
information about the various Roles, Access Control Groups (ACGs), and
Selections. It also provides the list of accessible features and operations that
can be performed by the respective roles. Keeping the sample scenario as an
example you can create various ACGs and assign roles.
For every IBM Global Data
Synchronization for WebSphere Product Center user a set of Roles can be assigned. As an example,
consider the company XYZ. This company has four main departments such as
Lighting, Consumer Electronics, Software, and Components. Each of these
departments has a Global Brand Manager. They are:
.
Lighting Global Brand Manager
.
Consumer Electronics Global Brand Manager
.
Software Global Brand Manager
.
Components Global Brand Manager
Note: The naming convention is [UDEX CAT SPECIFIC] Global Brand
Manager. That is, Lighting is the UDEX specific category.
The Global Brand Managers
are responsible for creating a GTIN. Each of these Global Brand Managers has
product executives. Once the Global Brand Manager creates the GTIN, a
notification is sent to the product executives to enrich the global attributes.
The respective product executives are:
.
Lighting Global Product Executive
.
Consumer Electronics Global Product Executive
.
Software Global Product Executive
.
Components Global Product Executive
Note: The Global Brand Manager can also enrich some or all the
global attributes.
When all the product
executives have completed enriching the global attributes, only then is the
global enrichment process complete. A notification that the global enrichment
for the trade item is complete is sent to the Global Brand Manager.
Now, if company XYZ has
business relations with US, Holland, and Singapore, there will be
target market specific Brand Managers for each category. They are:
.
Lighting US Brand Manager
.
Lighting Holland Brand Manager
.
Lighting Singapore Brand Manager
.
Consumer Electronics US Brand Manager
.
Consumer Electronics Holland Brand Manager
.
Consumer Electronics Singapore Brand Manager
.
Similarly there will be target market specific Brand Managers for each category.
The Global Brand Managers
will send the notification to these target market specific Brand Managers to
enrich the variants. Each of the target market specific Brand Managers has
Product Executives. The Product Executives enrich the variant attributes. Once
the variant attributes have been enriched, a notification for variant enrichment
completion is sent to the brand managers.
The various roles that are
pre-seeded in the IBM Global Data Synchronization for WebSphere Product Center solution
are:
.
WebSphere Product Centre Administrator
.
Global Data Synchronization Administrator
.
[UDEX CAT SPECIFIC] Global Brand Manager
.
[UDEX CAT SPECIFIC] Global Product Executive
.
Target Market Brand Manager
.
Target Market Product Executive
.
Marketing Manager
.
Marketing Executive
.
Data Sync Manager
.
Data Sync Executive
Note: These roles can be changed based on your
requirements.
The WebSphere Product
Centre Administrator has access to the data model. Typically, the administrator
is the PSS user.
The operations that can be
setup for IBM Global Data Synchronization for WebSphere Product Center solution and
WebSphere
Product
Center are
provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Create
. Edit
. View
. Modify
. Delete
. Explore
. Create
Variant
. Delete
Variant
. Enrich
Global
. Enrich
Variant
. Approve
/Reject
. Publish
New Item
. Send
Initial Load
. Add
Item
. Synchronize
Changes
|
. Create
. Edit
. View
. List
. Modify
. Delete
. Explore
. Approve/Reject |
. Create
. Edit
. View
. List
. Modify
. Delete
. Approve/Reject
. Add
Item Link |
. Publish
Transactions
. View
Generated XML
. Item
Transactions
. Hierarchy
Transactions
. Trading
Partner Transactions |
. Publications
. Initial
Load
. Item
Add
. Item
Link Add
. New
Item Request
. Item
Change Request
. New
Item Hierarchy Request
. Item
Hierarchy Change Request
. New
Trading Partner Request
. Trading
Partner Change Request |
. Run
Publi-
cation Reports
. View
Publi-
cation Reports
. Run
Item Reports
. View
Item Reports
. Run
Trading Partner Reports
. View
Trading Partner Reports |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
. Edit
Catalog Views
. View
Items
. Add
Items
. Modify
Items
. Delete
Items
. Recategorize
Items
. Summary
Items
. Export
Attributes
. Differences
. Rollback
. Search
. Delete
. Run
Preview Script |
. List
. Edit
Hierarchy Views
. View
Hierarchy Nodes
. Add
Hierarchy Nodes
. Modify
Hierarchy Node Attributes
. Delete
Hierarchy Nodes
. Recategorize
Hierarchy Nodes
. Summary
Hierarchy Nodes
. Specmap
Hierarchy Nodes
. Attributes
. Rollback
. Delete |
. List
. Edit
Rule
. Delete |
. List
. Perform
Import
. Delete |
. View
Items
. Add
Items
. Modify
Items
. Delete
Items
. Recategorize
Items
. View
Hierarchy Nodes
. Add
Hierarchy Nodes
. Modify
Hierarchy Node Attributes
. Delete
Hierarchy Nodes
. Recategorize
Hierarchy Nodes
. Specmap
Hierarchy Nodes |
. View
Files
. Delete
Files |
|
WebSphere Product Center |
|
Workflow |
Collaboration Area |
Spec |
Screen |
Script |
Scheduler |
|
. List
. Edit
. Delete |
. List
. Checkout
Entries |
. Modify
Spec
. Modify
Spec Map |
. View |
. Create
Modify Scripts |
. View
Company Jobs |
The IBM Global Data
Synchronization for WebSphere Product Center administrator has access to all the functionalities in IBM
Global Data Synchronization for WebSphere Product Center and some of the
functionalities in WebSphere Product Centre such as import/export & user
management. The IBM Global Data Synchronization for WebSphere Product Center administrator does
not have access to the data model.
The IBM Global Data
Synchronization for WebSphere Product Center Administrator has access to the
following:
.
Notifications
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partners
.
Publish New Item, Send Initial Load, Add Item, Add Link, and Synchronize
Changes
.
Explore Transactions
.
Manage Items (Create GTIN, Create GTIN Variant (that is, target market and
Information provider), View/Edit GTIN Global Attributes, View/Edit Variant
Attributes, Enrich GTIN Global Attributes, Enrich Variant Attributes, Delete
GTIN, and Delete GTIN Variant)
.
Approve/Reject Items
.
Create/View/Edit/Delete/Approve Trading Partner
.
Import/Export Items, Item Links
.
User Management & Security
.
Reports
The operations that can be
setup for IBM Global Data Synchronization for WebSphere Product Center solution and
WebSphere
Product
Center are
provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Create
. Edit
. View
. Modify
. Delete
. Explore
. Create
Variant
. Delete
Variant
. Enrich
Global
. Enrich
Variant
. Approve
/Reject
. Publish
New Item
. Send
Initial Load
. Add
Item
. Synchronize
Changes
|
. Create
. Edit
. View
. List
. Modify
. Delete
. Explore
. Approve/Reject |
. Create
. Edit
. View
. List
. Modify
. Delete
. Approve/Reject
. Add
Item Link |
. Publish
Transactions
. View
Generated XML
. Item
Transactions
. Hierarchy
Transactions
. Trading
Partner Transactions |
. Publications
. Initial
Load
. Item
Add
. Item
Link Add
. New
Item Request
. Item
Change Request
. New
Item Hierarchy Request
. Item
Hierarchy Change
. New
Trading Partner Request
. Trading
Partner Change Request |
. Run
Public-
ation Reports
. View
Publi-
cation Reports
. Run
Item Reports
. View
Item Reports
. Run
Trading Partner
. View
Trading
. Partner
Reports
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
. List
. Perform
Import
. Delete |
. View
Items |
|
|
WebSphere Product Center |
|
Workflow |
Collaboration Area |
Spec |
Screen |
Script |
Scheduler |
|
|
|
|
. View |
. Create
Modify Scripts |
. View
Company Jobs |
[UDEX CAT SPECIFIC] Global Brand
Manager
The Global Brand Manager
is responsible for creating new trade items (global variant). The Global Brand
Manager can also edit local variant, delete an item and its local variant. There
will be one Global Brand Manager for each category.
The Global Brand Manager
has access to the following:
.
Notifications
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partners
.
Explore Transactions
.
Manage Items (Create GTIN, View/Edit GTIN Global Attributes, View/Edit Variant
Attributes, Delete GTIN, and Delete GTIN Variant)
.
View Trading Partner
.
Item Reports
The operations that the
Global Brand Manager can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Create
. Edit
. View
. Modify
. Delete
. Delete Variant
. Explore
|
. View
. List
. Explore |
. Create
. Edit
. View
. List
. Modify
. Delete
. Approve/Reject |
. Item Transactions
. Hierarchy Transactions
. Trading Partner
Transactions |
. New Item Request
. Item Change Request
. New Item Hierarchy Request
. Item Hierarchy Change
Request |
Run Item reports
View Item reports |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List |
. List |
. List |
|
. View Items |
. View Files
. Delete
Files |
The Global Product
Executive can enrich GTIN global attributes and also view or edit the variant
attributes.
The Global Product
Executive has access to the following:
.
Notifications
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partners
.
Manage Items (View/Edit GTIN Global Attributes, View/Edit Variant Attributes,
and Enrich GTIN Global Attributes)
.
View Trading Partner
The operations that the
Global Product Executive can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Edit
. View
. Modify
. Explore
. Enrich
Global |
. List
. View
. Explore |
. List
. View
|
. Item
Transaction |
New Item Request |
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items
. |
. View
Files
. Delete
Files |
Target Market Brand Manager
The [UDEX CAT : TM
Specific] Brand Manager can create, delete a variant of an item, approve,
or disapprove the variant.
The Brand Manager has
access to the following:
.
Notifications
.
Quick Search, Basic Search , and Advanced Search for Trade Items, Trade Item
Links, and Trading Partners
.
Explore Transactions
.
Manage Items (Create GTIN Variant, View GTIN Global Attribues, View/Edit Variant
Attributes, Enrich Variant Attributes and Delete GTIN Variant)
.
Approve/Disapprove GTIN Variant
The operations that the
Target Market Brand Manager can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
Reports |
|
. List
. Edit
. View
. Modify
. Explore
. Create
Variant
. Delete
Variant
|
. List
. View
. Explore |
. List
. View
. Edit
. Delete
. Create
. Modify |
. Item
Transactions
. Hierarchy
Transactions |
. New
Item Request
. Item
Change Request
. New
Item Hierarchy Request
. Item
Hierarchy Change Request |
. Run
Tra-
ding Partner
. View Trading
Partner
reports |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
. View
Files
. Delete
Files |
The Target Market Product
Executive can enrich variant attributes.
The Target Market Product
Executive has access to the following:
.
Notifications
.
>Quick Search, Basic Search , and Advanced Search for Trade Items, and
Trading Partner
.
Manage Items (View GTIN Global Attributes, View/Edit Variant Attributes, and
Enrich Variant Attributes)
.
View Trading Partner
The operations that the
Target Market Product Executive can perform in IBM Global Data Synchronization
for WebSphere Product Center solution and WebSphere Product Center are provided in
the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
|
. List
. Edit
. View
. Modify
. Explore
. Enrich
Variant |
. List
. View
. Explore |
|
|
. New
Item Request
. Item
Change Request |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items
|
View Files
Delete Files
|
Marketing Manager
The Marketing Manager can
view trade Items and trading partner information.
The Marketing Manager has
access to the following:
.
Notifications
.
Quick Search, Basic Search, and Advanced Search for Trade Items, Trade Item
Links, and Trading Partner
.
Manage Items (View GTIN Global Attributes, View Variant Attributes)
.
View Trading Partner
.
.
.
The operations that the
Marketing Manager can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications
|
|
. List
. View
. Explore |
. List
. View
. Edit
. Delete
. Create
. Modify
. Explore
. Approve/Reject |
. List
. View |
Trading Partner Transactions |
New Trading Partner Request
Trading Partner Change Request |
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
View Files
Delete Files |
Marketing Executive
The Marketing Executive
can view Trade Items and Trading Partner Information
.
Notifications
.
Quick Search, Basic Search , and Advanced Search for Trade Items, Trade Item
Links, and Trading Partner
.
Add Link
.
Explore Transactions
.
Manage Items (View GTIN Global Attributes, View Variant Attributes)
.
View Trading Partner
The operations that the
Marketing Executive can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
|
. List
. View
. Explore |
. List
. View
. Edit
. Delete
. Create
. Modify
. Explore |
. List
. View
|
. Trading
Partner Transactions |
New Trading Partner Request
Trading Partner Change Request
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
View Files
Delete Files |
Data Sync Manager
The Data Sync Manager can
process and approve Subscriptions and has access to the following:
.
Notifications
.
Quick Search, Basic Search , and Advanced Search for Trade Items
.
Publish New Item, Send Initial Load, Add Item, Synchronize Changes, Request for
Publication, Process Initial Load and Process Item Change and Item Delist
.
Explore Transactions
.
.
.
.
.
.
.
.
The operations that the
Data Sync Manager can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
|
. Request
For Publication
. Stop
Synchronization
. Process
Initial Load
. Process
New Item
. Process
Item Change
. Process
Item Delist
. Process
item withdraw
. Submit
For Enrichment
. Classify
Item
. Synchronize
Internally
. Publication
Explore
. Query
Item
|
|
|
. Publish
Transactions
. View
Generated XML |
. New
Item Publications
. Initial
Load Publications
. Item
Change Publication
. Item
Delist Publication
. Item
Withdraw Publication
. Subscription
Request
. Filter
Request
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
View Files
Delete Files |
Data Synch Executive
The Data Synch Executive
can process Subscriptions and Filters.
The Data Synch Executive
has access to the following:
.
Notifications
.
Publish New Item, Send Initial Load, Add Item, Synchronize Changes, Request for
Publication, Process Initial and Query Items
.
Explore Transactions
The operations that the
Marketing Manager can perform in IBM Global Data Synchronization for
WebSphere
Product
Center
solution and WebSphere Product Center are provided in the table.
|
IBM Global Data Synchronization for WebSphere Product
Center Solution |
|
Trade Item |
Trading Partner |
Trade Item Link |
Transactions |
Notifications |
|
. Request
For Publication
. Stop
Synchronization
. Process
Initial Load
. Process
New Item
. Process
Item Change
. Process
Item Delist
. Process
item withdraw
. Submit
For Enrichment
. Classify
Item
. Synchronize
Internally
. Publication
Explore
. Synchronize
Changes
. Classify
Item
. Synchronize
Internally
. Query
Item |
|
|
. Publish
Transactions
. View
Generated XML |
. New
Item Publications
. Initial
Load Publications
. Item
Change Publication
. Item
Delist Publication
. Item
Withdraw Publication
. Subscription
Request
. Filter
Request
|
|
WebSphere Product Center |
|
Catalog |
Hierarchy |
Selection |
Import |
Selection Members |
DocStore |
|
. List
|
. List |
. List |
|
. View
Items |
View Files
Delete Files |
The following workflow roles
are pre-seeded in the solution. The user needs to have these roles to do the
actions related to workflows. When a new user is created to perform certain
action(s) in a specified workflow, that user should be assigned with a specific
role(s). These roles qualify the user to perform the actions.
.
GDS_ALL_WF_Role: This role is usually given to the administrator user. User with
this role can access all workflows
.
GDS_Approve_Filter_Deletion_WF_Role : This role is required to approve filter
deletions.
.
GDS_Approve_Filter_WF_Role: This role is required to approve filter
creations.
.
GDS_Approve_Item_Deletion_WF_Role: This role is required to approve item
deletions.
.
GDS_Approve_Item_WF_Role: This role is required to approve Item creations.
.
GDS_Approve_Link_Deletion_WF_Role: This role is required to approve Item Link
deletions.
.
GDS_Approve_Link_WF_Role: This role is required to approve Link creation.
.
GDS_Approve_Modified_Filter_WF_Role: This role is required to approve filter
modifications.
.
GDS_Approve_Modified_TP_WF_Role: This role is required to approve trading
partner modifications.
.
GDS_Approve_Modify_Link_WF_Role: This role is required to approve Item Link
modifications.
.
GDS_Approve_Modify_Trade_Item_WF_Role: This role is required to approve trade
item modifications.
.
GDS_Approve_New_TP_WF_Role: This role is required to approve creation of new
trading partners.
.
GDS_Approve_Subscription_Deletion_WF_Role: This role is required to approve
subscription deletion.
.
GDS_Approve_Subscription_WF_Role: This role is required to approve subscription
creation.
.
GDS_Approve_TP_Deletion_WF_Role: This role is required to approve trading
partner deletion.
.
GDS_Enrich_Global_Attributes_WF_Role: This role is required to enrich global
attributes for a trade item.
.
GDS_Enrich_Local_Attributes_WF_Role: This role is required to enrich Local
Attributes for a trade item.
.
GDS_Internal_Sync_WF_Role: This role is required to perform internal
synchronization of a trade item.
.
GDS_Modify_Filter_WF_Role: This role is required to modify a filter.
.
GDS_Modify_Trade_Item_WF_Role: This role is required to modify a trade item.
.
GDS_Process_Initial_Load_Publication_WF_Role: This role is required to process
an initial load publication.
.
GDS_Process_Item_Change_Publication_WF_Role: This role is required to process an
item change publication.
.
GDS_Process_Item_Delist_Publication_WF_Role: This role is required to process an
item class=msoDel> delist Delist publication.
.
GDS_Process_Item_Withdraw_Publication_WF_Role: This role is required to process
an item withdraw publication.
.
GDS_Process_New_Item_Publication_WF_Role: This role is required to process new
item publication.
.
GDS_Set_Category_Mapping_WF_Role: This role is required to set category
mapping
.
GDS_Submit_For_Enrichment_WF_Role: This role is required to submit a trade item
for enrichment
Examples of UDEX Category
and Target Market Specific ACGs are provided in the following table.
|
ACG |
Roles |
|
|
ALCOHOL BASED MIXERS ACG |
ALCOHOL BASED MIXERS Global Brand Manager |
[UDEX CAT SPECIFIC] Global Brand Manager |
|
ALCOHOL BASED MIXERS Global Product Executive |
[UDEX CAT SPECIFIC] Global Product Executive |
|
ALCOHOL BASED MIXERS - US Brand Manager |
[UDEX CAT - TM SPECIFIC] Brand Manager |
|
ALCOHOL BASED MIXERS UK Brand Manager |
|
ALCOHOL BASED MIXERS - US - Logistics Product
Executive |
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] Product
Executive |
|
ALCOHOL BASED MIXERS - US - Measures Product
Executive |
|
ALCOHOL BASED MIXERS - US - Nutrition Product
Executive |
|
ALCOHOL BASED MIXERS - UK - Logistics Product
Executive |
|
ALCOHOL BASED MIXERS - UK - Measures Product
Executive |
|
ALCOHOL BASED MIXERS - UK - Nutrition Product
Executive |
|
US ACG |
ALCOHOL BASED MIXERS - US Brand Manager |
[UDEX CAT - TM SPECIFIC] Brand Manager |
|
ALCOHOL BREWING_MAKING KITS US Brand Manager |
|
ALCOHOL BASED MIXERS - US - Logistics Product
Executive |
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] Product
Executive |
|
ALCOHOL BASED MIXERS - US - Measures Product
Executive |
|
ALCOHOL BASED MIXERS - US - Nutrition Product
Executive |
|
ALCOHOL BREWING_MAKING KITS - US - Logistics Product
Executive |
|
ALCOHOL BREWING_MAKING KITS - US - Measures Product
Executive |
|
ALCOHOL BASED MIXERS - US - Logistics User |
[[UDEX CAT - TM - ATTR GROUP SPECIFIC] User |
|
ALCOHOL BASED MIXERS - US - Measures User |
|
ALCOHOL BASED MIXERS - US - Nutrition User |
|
ALCOHOL BREWING_MAKING KITS - US - Logistics
User |
|
ALCOHOL BASED MIXERS - US Variant Publisher |
[UDEX CAT - TM SPECIFIC] Variant Publisher |
|
ALCOHOL BREWING_MAKING KITS US Variant
Publisher |
Selections
The following Selections
have been pre-seeded into the model which means that the following selections
will be added to the model, during the installation process of the
application.
|
Selection |
ACG |
Catalog |
Hierarchy |
Selected Categories |
|
UNET_ALCOHOL BASED MIXES/MIXERS |
Alcohol ACG |
Globa_Catalog |
UDEX_Hierarchy_UCCNet |
. ALCOHOL
BASED MIXES/
MIXERS
. ALCOHOL
BASED COCKTAILS/
MIXES
. ALCOHOL
BASED MIXERS |
|
UNET_ANIMAL/PET ACCESSORIES OTHER |
Animal Pet ACG |
Global_Catalog |
UDEX_Hierarchy_UCCNet |
. ANIMAL/PET
ACCES-
SORIES OTHER
. ANIMAL/PET
ACCES-
SORIES OTHER
. ANIMAL/PET
ACCES-
SORIES OTHER VARIETY PACKS/SETS |
|
UNET_CEREAL GRAINS WITH ADDITIONS - DRY (SHELF
STABLE) |
Cereal Grains ACG |
Global_Catalog |
UDEX_Hierarchy_UCCNet |
. CEREAL
GRAINS WITH ADDITIONS - DRY (SHELF STABLE)
.
BULGUR WHEAT WITH ADDITIONS - DRY (SHELF STABLE)
.
CEREAL GRAINS OTHER WITH ADDITIONS - DRY (SHELF STABLE) |
|
TM_Africa |
Africa ACG |
Global_Local_Catalog |
Target_Market_Hierarchy |
. EG
. SA |
|
TM_NorthAmerica |
North America ACG |
Global_Local_Catalog |
Target_Market_Hierarchy |
. US
. CA |
Appendix C : Installation
Checklist
q
Ensure that the correct version of
WebSphere
Product
Center is
installed.
q
Create a company in WebSphere Product Center that will be used
for Supply Side Data synchronization.
q
Before installing GDS, ensure that
WebSphere
Product
Center is
not running.
q
Run the installer to install GDS for the
required platform.
q
Modify .bashrc for GDS < GDS Installed
Directory >>$TOP variable.
q
Modify .bashrc for WPC_INSTALL_DIR and
WPC_JAR
q
Create a softlink for gds.properties,
gds_system.properties and gdsSupplyTradeItemFunctions.properties,
GDSServiceRegistry.xml, GDSCacheRegistry.xml, GDSCacheManagerRegistry.xml
from GDS installed directory (
<> GDS Installed Directory> > >$TOP/etc/default) to WPC
installed directory.
q
Create a soft link to the messaging folder and
the .bindings file from GDS installed directory to WPC installed
directory.
q
Modify common.properties in GDS to set the
parameter values for db_username, db_password, db_url (should be the same as set
in WebSphere
Product
Center).
q
Modify common.properties in GDS to set the
parameter values for rmi_port, appsrvr_port ( rmi port should be the same as
WebSphere
Product
Center but
the appsrvr_port should be different).
q
Modify init_cgd_vars.sh( < GDS Installed
Directory
>>$TOP/setup) to set the values for WAS_HOME, JDK_HOME,
DB2_HOME, WAS_HOME, WAS_NODENAME, WAS_APPSERVERNAME and WAS_VHOST
q
Modify common.properties for the following
parameters rmi_port
.
app_svr port.
.
db_maxConnection_messaging
.
db_minConnection_messaging
.
db_maxConnection_messaging_gdsmsg
.
db_maxConnection_messaging_default
.
db_maxConnection_messaging_system
.
Under the parameters for workflow engine section, add set the value for the
following parameter: db_maxConnection_workflowengine_gdsmsg
q
Modify gds.properties to set the correct
parameter values for company_code, admin_user, app_type , Language_Specific_Spec_identifier and active
DataPool.
q
Run test_db.sh( < GDS Installed
Directory >>>$TOP/bin) to verify if the
database connection is working.
q
Run create_vhost.sh, create_appsrvr.sh,
install_supply_war.sh scripts (These scripts are available in >< GDS Installed
Directory >>>$TOP/bin/Websphere).
q
Load the supply side datamodel using the
script create_gds_schema.sh for the company as specified during installation of
WebSphere
Product
Center.
q
Run test_java_db.sh( < GDS Installed
Directory >$TOP/bin) to test the
connectivity between the database and the app server
q
Restart
Websphere
Product
Center.
q
Create Roles as required in WebSphere Product Center.
q
Create Access Control Groups(ACG) as required
in WebSphere
Product
Center
Create User and assign Roles accordingly in
WebSphere
Product
Center.
q
Create Selections for the required Access
Control Groups in WebSphere Product Center.
q
Create Catalog Access Privileges in
WebSphere
Product
Center.
q
Restart
WebSphere
Product
Center.
q
Start IBM Global Data Synchronization for
Websphere
Product
Center by
running start_appsvr.sh( < GDS Installed Directory >
$TOP/bin/go/start).
q
Start Global Data Synchronization by running
start_appsvr.sh( < GDS Installed Directory >
$TOP/bin/go/start).
q
Ensure the correct version of WebSphere Product Center is
installed.
q
Create a Company in WebSphere Product Center which will be used
for Demand Side Data Sync.
q
Ensure that Websphere Product Center is not
running.
q
Run the installer to install IBM global Data
Synchronization for WebSphere Product Center for the required platform.
q
Modify .bashrc for GDS < GDS Installed
Directory
> $TOP
variable.
q
Modify .bashrc for WPC_INSTALL_DIR &
WPC_JAR.
q
Create a softlink for .bindings,
gds.properties, gds_system.properties, gdsDemandTradeItemFunctions,
GDSServiceRegistrySupply.xml, GDSServiceRegistryDemand.xml,
GDSCacheRegistry.xml, GDSCacheManagerRegistry.xml from IBM Global Data
Synchronization for WebSphere Product Center directory(
< GDS Installed Directory > $TOP/etc/default).
q
Create a soft link to the messaging folder and
the .bindings file from GDS installed directory to WPC installed
directory.
q
Create a soft link to the
publicationprocess.properties file in case of demand side application using pass
through GDS Model (Custom Workflows)
q
Modify init_cgd_vars.sh ( < GDS Installed
Directory
>
$TOP/setup) to set the values for WAS_HOME, JDK_HOME, DB2_HOME, WAS_HOME,
WAS_NODENAME, WAS_APPSERVERNAME and WAS_VHOST.
q
Modify gds.properties to set the correct
parameter values for Company_code, App_type and activeDataPool.
q
Modify common.properties in IBM Global Data
Synchronization for WebSphere Product Center to set the parameter values for db_username, db_password,
db_url. (Should be same as used for WebSphere Product Center).
q
Modify common.properties in IBM Global Data
Synchronization for WebSphere product Center to set the parameter values for rmi_port, appsrvr_port.
(rmi port should be same as used in WebSphere Product Center, appsrvr_port
should be different).
q
Run test_db.sh( < GDS Installed
Directory
>
$TOP/bin) to verify database connection is working.
q
Run create_vhost.sh, create_appsvr.sh,
install_supply_war.sh scripts(Available in < GDS Installed
Directory
>
$TOP/bin/webpshere).
q
Modify the properties inboundqueue and
outboundqueue in the file properties.xml.
q
Run the script
create_gds_demand_schema.sh for the company as specified while installing
WebSphere
Product
Center.
After running the create_schema script, depending on the ACTIVE_DATAPOOL_IDrun
the script that loads the data
model. This loads the data
model.
q
Start
WebSphere
Product
Center.
q
Create Roles as required in WebSphere Product Center
q
Create Access Control Groups(ACGs) as required
in WebSphere
Product
Center
q
Create User and assign Roles accordingly in
WebSphere
Product
Center
q
Create Selections for the required Access
Control Groups in WebSphere Product Center
q
Create Catalog Access Privileges in
WebSphere
Product
Center.
q
Restart
WebSphere
Product
Center
q
Start IBM Global Data Synchronization for
WebSphere
Product
Center by
running start_appsvr.sh( < GDS Installed Directory >
$TOP/bin/go/start)
Appendix D : Variables in
gds.properties and gds_system.properties
>
|
Variable |
Possible Values |
Remarks |
|
Common Options
|
|
Company_code |
<Name of the company>
|
Specify the value of company created in WPC like
supply-side, Acme etc. |
|
admin_user |
<Admin> |
This is the value for Admin user login to GDS. Default
value is Admin. |
|
gds_app_type |
Demand or Supply |
This is the component of the application that is being
installed. |
|
Enrichment Options |
|
global_enrichment |
True/False |
The possible values are true & false. Global
enrichment workflow will be turned on if the value if true and turned off
if the value if false. |
|
local_enrichment |
True/False |
The possible values are true & false. Local
enrichment workflow will be turned on if the value if true and turned off
if the value if false. |
|
Approval Options |
|
NEW_ITEM_APPROVAL |
On/Off |
New Item Approval workflow will be turned ON if the
value if ON and turned off if the value if OFF |
|
MODIFY_ITEM_APPROVAL |
On/OFF |
Modify Item Approval workflow will be turned ON if the
value if ON and turned off if the value if OFF |
|
MODIFY_ITEM_WORKFLOW =ON |
On/OFF |
If this property is set to Off, the Items will not be
checked out in the Modify Workflow |
|
DELETE_ITEM_APPROVAL |
On/OFF |
Delete Item Approval workflow will be turned ON if the
value if ON and turned off if the value if OFF
|
|
MODIFY_LINK_APPROVAL |
On/Off |
Modify Link Approval workflow will be turned ON if the
value if ON and turned off if the value if OFF |
|
NEW_TP_APPROVAL |
On/Off |
New Trading Partner Approval workflow will ON be turned
ON if the value if ON and turned off if the value if OFF
|
|
MODIFY_TP_APPROVAL |
On/Off |
Modify Trading Partner Approval workflow will ON be
turned ON if the value if ON and turned off if the value if OFF |
|
DELETE_TP_APPROVAL |
On/Off |
Delete Trading Partner Approval workflow will ON be
turned ON if the value if ON and turned off if the value if OFF |
|
Notifications |
|
additional_notif_mode |
<Blank> |
The property 'notif_mode' is changed to
'additional_notif_mode' in gds.properties and the option WORKLIST is
removed. This property is left empty by default.
Set the property 'additional_notif_mode' to EMAIL to
receive the notifications as an email |
|
Internal Hierarchy Classification |
|
udex_to_internal_hierarchy_mapping
|
False/True |
The variable is a flag which specifies automatic
mapping between UDEX Hierarchy and Internal Hierarchy.
If value is set to true, automatic mapping is done. If
false, manual mapping is required to be done. |
|
Internal_Classification_Scheme |
Internal_Hierarchy
UDEX_Hierarchy_UCCNet
GPC_Hierarchy |
This is the primary classification scheme in GDS. All
security setting for selection should be based on this classification.
|
|
Organizational Settings |
|
default_locale |
en_US |
This is the default locale assigned to the user on
first login. |
|
GS1_ENABLED |
True/False |
If set to true, the organization is GS1 enabled and if
false GS1 is disabled. |
|
Setting Batch Limit |
|
Batch_Limit |
<numeric value> |
Sets the Batch limit while generating the XML for trade
items. |
|
Pagination Sizes |
|
pagination_size |
<numeric value> |
This value will set the number of categories to be
displayed in the category tree page |
|
GTIN_SEARCH_PAGINATION_SIZE |
<numeric value> |
This value will set the number of records to be
retrieved from GTIN search criteria. |
|
GLN_SEARCH_PAGINATION_SIZE |
<numeric value> |
This value will set the number of records to be
retrieved from GLN search criteria. |
|
MASS_PUBLICATION_PAGINATION_SIZE |
<numeric value> |
This value will set the number of records to be
retrieved from Mass Publication search criteria. |
|
TRANSACTION_SEARCH_PAGINATION_SIZE |
<numeric value> |
. This value will set the number of records to be
retrieved from transaction search criteria. |
|
SCRIPT_SEARCH_PAGINATION_SIZE |
<numeric value> |
This value will set the number of records to be
retrieved from the script search criteria. |
|
NOTIFICATION_CONSOLE_PAGINATION_SIZE
|
<numeric value> |
This value will set the number of records to be
retrieved from Notification Console Search Criteria |
|
REPORT_SEARCH_PAGINATION_SIZE |
<numeric value> |
This value will set the number of records to be
retrieved from Report Console search criteria. |
|
MASS_TRANSACTION_PAGINATION_SIZE |
<numeric value> |
This value will set the number of records to be
retrieved For mass jobs throughout WPC reports search criteria.
For better performance its recommended to be less than
25 |
|
Demand Side Options |
|
Enabling Workflows |
|
Initial Load |
New Item |
Item Change |
Subscription |
Item Correct |
|
|
INITIAL_LOAD_PUBLICATION_AUTO_REJECT
INITIAL_LOAD_PUBLICATION_APPROVAL
INITIAL_LOAD_PUBLICATION_ENRICHMENT
INITIAL_LOAD_PUBLICATION_INTERNAL_SYNC
INITIAL_LOAD_PUBLICATION_SEND_INTERNAL_SYNC_MSG
|
NEW_ITEM_PUBLICATION_AUTO_REJECT
NEW_ITEM_PUBLICATION_APPROVAL
NEW_ITEM_PUBLICATION_ENRICHMENT
NEW_ITEM_PUBLICATION_INTERNAL_SYNC
NEW_ITEM_PUBLICATION_SEND_INTERNAL_SYNC_MSG
NEW_ITEM_FILTER |
ITEM_CHANGE_PUBLICATION_AUTO_REJECT
P2 ITEM_CHANGE_PUBLICATION_APPROVAL
ITEM_CHANGE_PUBLICATION_ENRICHMENT
ITEM_CHANGE_PUBLICATION_INTERNAL_SYNC
ITEM_CHANGE_PUBLICATION_SEND_INTERNAL_SYNC_MSG
ITEM_DELIST_REVIEW
ITEM_WITHDRAW_REVIEW
|
NEW_SUBSCRIPTION_APPROVAL
MODIFY_SUBSCRIPTION_APPROVAL
DELETE_SUBSCRIPTION_APPROVAL
|
ITEM_CORRECT_PUBLICATION_AUTO_REJECT
ITEM_CORRECT_PUBLICATION_ENRICHMENT
ITEM_CORRECT_PUBLICATION_INTERNAL_SYNC
ITEM_CORRECT_PUBLICATION_SEND_INTERNAL_SYNC_MSG |
On/
Off |
|
UDEX-GPC mapping |
|
udex_to_gpc_hierarchy_mapping
|
True/False |
The property sets the automating mapping between the
UDEX and GPC hierarchy. |
|
|
|
DEFAULT_USER_FOR_PUBLICATION_NOTIFICATION
|
<username> |
A default user can be specified to whom the publication
notifications will be sent in case no users are obtained from the
security.
Example:
DEFAULT_USER_FOR_PUBLICATION_NOTIFICATION=master, Where
master is a user who has publication processing privileges. |
|
UCCNET_GTIN_REGISTRATION
|
True/False |
If set to True, it performs validation for all incoming
publications for the mandatory attributes in the trade item. |
|
Supply Side
Options |
|
gpc_to_internal_hierarchy_mapping |
True/false |
|
|
Messaging Related Properties |
|
Configuring active data pool |
|
ACTIVE_DATA_POOL_ID
|
Possible values:
Transora
UCCNet
WWREV6 |
Sets the active data pool, queue and the doc store path
for the outbound message.
|
|
Configuring Default Language |
|
DEFAULT_LAUNGUAGE |
Transora = specify the data pool specific language
code
UCCNet= specify the data pool specific language
WWREV6= specify the data pool specific language |
This value will be used in setting the default language
code while generating the XML used for messaging. |
|
Language_Specific_Spec_Identifier |
Specify the data pool specific Language |
This is the default attribute name used to identify the
language specific attributes. |
|
|
|
FIRST_LEVEL_MAX_WORKER_COUNT=10 |
<Numeric> |
|
|
SECOND_LEVEL_MAX_WORKER_COUNT=10 |
<Numeric> |
|
|
THIRD_LEVEL_MAX_WORKER_COUNT=10 |
<Numeric> |
|
|
MASS_PUBLICATION_MAX_WORKER_COUNT=10 |
<Numeric> |
|
|
|
|
UCCNET_GTIN_REGISTRATION |
True/False |
|
|
BROWSE_HIERARCHY_DISPLAY |
True/False |
|
|
CATEGORY_TREE_DISPLAY=TRUE. |
True/False |
If the property is set to true then the category tree
display is enabled in the search screens |
|
DROP_DOWN_COUNT_LIMIT |
<Numeric> |
|
|
|
|
|
|
|
|
|
|
Variable |
Possible Values |
Remarks |
|
SystemConfiguration Properties |
|
transactionID
|
<TransactionIDFile>
|
This generates a file with this name in the < GDS
Installed Directory >_ETC_DIR. It is used to
store the current Transaction ID. |
|
batchID
|
BatchIDFile
|
Generates a file with this name in the < GDS
Installed Directory >_ETC_DIR. Used to store the
current Transaction Batch ID. |
|
batchPublishID |
BatchIDPublishFile |
BatchID Sequence for Publish File Name |
|
Attribute groups settings for GTIN |
|
ATTRIBUTE_GROUP_LOOKUP_TABLE |
Attribute_Group_Names_LookUP |
The Lookup table that contains the list of all the
Attribute Collection to be displayed in the GDS UI. |
|
REQUIRED_TYPE_ATTRIBUTE_GROUP_LOOKUP_TABLE
|
Required_Type_Attribute_Group_Names_LookUP
|
The Lookup table that contains the list of all the
required attribute collections to be displayed in the GDS UI.
|
|
SPECIFIC_REQUIRED_TYPE_ATTRIBUTE_GROUP_LOOKUP_TABLE |
Specific_Required_Type_Attribute_Group_Names_LookUP |
The Lookup table that contains the list of all the
specific required attribute collections to be displayed in the GDS
UI. |
|
Attribute groups settings for Trading
Partner |
|
TP_ATTRIBUTE_GROUP_LOOKUP_TABLE |
TradingPartnerGroupNames |
The Lookup table that contains the list of all the
Trading Partner group names. |
|
TP_REQUIRED_TYPE_ATTRIBUTE_GROUP_LOOKUP_TABLE |
RequiredTradingPartnerGroupNames |
The Lookup table that contains the list of all the
required Trading Partner group names. |
|
Sorting |
|
sort_items=false
|
True/False |
If the property is set to true then the Trade Items are
sorted by GTIN_TM_IP in search results |
|
|
|
USE_NEW_METHOD
|
True/false
|
Used for memory profiling.
If USE_NEW_METHOD is true then new method for displaying buttons in Manage
Items will be called otherwise the older GDSUtils.getPossibleActions will
be called. |
|
ENABLE_CATALOG_CACHING |
True/False |
To enable/disable caching of catalogs. |
|
SEND_TO_JMS
|
True/False |
If set to True, the
generated XML messages will be sent to the messaging queue.
|
|
Validation Scripts Path |
|
TRADE_ITEM_VALIDATION_SCRIPT_PATH=/ Path of the Trade
Item Validation Script in WPC
|
Path of the trade item validation script in WebSphere
Product Center
For example:
scripts/distribution/Trade Item
Validation |
This is script used for the compliance check of the
trade item. |
|
TRADE_ITEM_LINK_VALIDATION_SCRIPT_PATH
|
Path of the trade item link validation script in
WebSphere Product Center
For example:
scripts/distribution/Trade Item LinkValidation |
This is script used for the compliance check of the
trade item link. |
Note: The following table is a list of important variables that
need to be configured in Properties.xml. The variables differ depending on the
data pool services being used by the GDS application.
|
Variable |
Possible Values |
Remarks
|
|
|
Common properties in Transora, UCCNet and WWRE,
Outbound |
|
|
ExchangeGln |
<value provided depending on the datapool> |
GLN of the respective exchange. It varies with respect
to the datapool service that you have opted for.
|
|
|
SelfGln |
<value provided depending on the datapool> |
GLN of the trading partner who is using this
application.
|
|
|
UserId |
<User Id> |
UserId to access datapool services
|
|
|
Password |
<Password> |
Password given for the UserId |
|
|
RepresentatingParty |
<13 digit numeric value> |
Default GLN used by the party sending messages to the
data pool. |
|
|
DefaultLocale |
en_US |
Default Locale of the trading partner |
|
|
TimeZone
|
PST |
Time Zone of the trading partner
|
|
|
outBoundQueueName |
<queue name>
|
|
|
|
initialContextFactory |
<initial context>
|
|
|
|
queueConnectionFactory |
<connection factory>
|
|
|
|
DoctypeName |
|
|
|
|
DefaultNamespace |
|
|
|
|
Inbound
|
|
|
inBoundQueueName
|
<queue name>
|
|
|
|
initialContextFactory
|
<initial context>
|
|
|
|
queueConnectionFactory
|
<connection factory>
|
|
|
|
Properties Specific to WWRE, Outbound
|
|
|
DocumentInstanceIdentifier |
http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader
http://www.gs1globalregistry.net/2.0/schemas/sbdh/
StandardBusinessDocumentHeader.xsdurn:ean.ucc:2
http://www.gs1globalregistry.net/2.0/schemas/CatalogueItemConfirmationProxy.xsd
|
|
|
|
CIC_schemaLocation
|
|
Specifies the schema location of the CIC message |
|
|
RFCIN_schemaLocation |
http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader
http://www.gs1globalregistry.net/2.0/schemas/sbdh/StandardBusinessDocumentHeader.xsd
urn:ean.ucc:2
http://www.gs1globalregistry.net/2.0/schemas/RequestForCatalogueItemNotificationProxy.xsd
|
Specifies the schema location of the RFCIN
message |
|
|
CIS_schemaLocation
|
http://www.unece.org/cefact/namespaces/StandardBusinessDocumentHeader
http://www.gs1globalregistry.net/2.0/schemas/sbdh/StandardBusinessDocumentHeader.xsd
urn:ean.ucc:2
http://www.gs1globalregistry.net/2.0/schemas/CatalogueItemSubscriptionProxy.xsd
|
Specifies the schema location of the CIS message |
|
|
communicationVersion |
2.0.2
|
|
|
|
contentVersion |
2.0.2
|
|
|
|
SenderIdentifier |
<Sender GLN - 13
digit numeric value > |
Sender's GLN |
|
|
SenderContact |
<contact's name> |
Contact person's name |
|
|
SenderEmailAddress |
<email address> |
Sender's email address |
|
|
SenderFaxNumber |
<e.g. +1-212-555-1213 > |
Sender's fax number |
|
|
SenderTelephoneNumber |
<e.g. +1-212-555-1213 > |
Sender's telephone number |
|
|
SenderContactTypeIdentifier |
Buyer |
Sender's identifier |
|
|
ReceiverIdentifier |
<Receiver GLN -
13 digit numeric value
> |
Receiver's GLN |
|
|
ReceiverContact |
<contact's name> |
Contact person's name |
|
|
ReceiverEmailAddress |
<email address> |
Receiver's email address |
|
|
ReceiverFaxNumber |
<e.g. +1-212-555-1213 > |
Receiver's fax number |
|
|
ReceiverTelephoneNumber |
<e.g. +1-212-555-1213 > |
Receiver's telephone number |
|
|
ReceiverContactTypeIdentifier |
Seller |
Receiver's identifier |
|
|
Inbound |
|
|
ResponseMessageIdentifier
|
//sh:StandardBusinessDocument/eanucc203:message/gdsn:eANUCCResponse/documentReceived/uniqueCreatorIdentification
|
|
|
|
Command |
//sh:StandardBusinessDocument/sh:StandardBusinessDocumentHeader/sh:DocumentIdentification/sh:InstanceIdentifier |
|
|
|
TargetGLN
|
//sh:StandardBusinessDocument/sh:StandardBusinessDocumentHeader/sh:Sender/sh:Identifier
|
|
|
|
ExceptionResponseMessageIdentifier
|
//sh:StandardBusinessDocument/eanucc203:message/gdsn:gDSNException/originatingMessageIdentifier/uniqueCreatorIdentification |
|
|
|
CatalogName
|
WWREMessageArchiveCatalog
|
|
|
|
MessageIdentifier
|
//sh:StandardBusinessDocument/eanucc203:message/entityIdentification/uniqueCreatorIdentification
|
|
|
|
Properties Specific to UCCNet, Outbound
|
|
|
schemaLocation
|
>http://www.uccnet.org/schemas/2.2/uccnet
http://www.testregistry.net/xmlschema/uccnet/2.2/Envelope.xsd |
|
|
|
StatusOfQueryList
|
Unread
|
|
|
|
CountOfQueryWorkList
|
<1>
|
|
|
|
communicationVersion
|
<2.2> |
|
|
|
Inbound
|
|
|
Command
|
//uccnet:envelope/body/response/acknowledge/acknowledgement/subdocumentValid/subdocumentValid/documentIdentifier/typedEntityIdentification/@type
|
|
|
|
TargetGLN
|
//uccnet:envelope/body/response/acknowledge/acknowledgement/acknowledgementHeader/entityIdentification/globalLocationNumber/gln
|
|
|
|
SecondLevelMessageStatus
|
//uccnet:envelope/body/response/acknowledge/acknowledgement/subdocumentValid/subdocumentValid/@success
|
|
|
|
ThirdLevelMessageStatus
|
//uccnet:envelope/body/response/acknowledge/acknowledgement/subdocumentValid/subdocumentValid/subdocumentValid/@success
|
|
|
|
CatalogName
|
UCCNetMessageArchiveCatalog
|
|
|
|
MessageIdentifier
|
//uccnet:envelope/body/response/acknowledge/acknowledgement/acknowledgementHeader/messageIdentifier/value
|
|
|
|
Properties Specific to Transora, Outbound |
|
|
PartyIdType
|
GLN
|
|
|
|
MessageFormat |
TransoraXML
|
|
|
|
DoctypeSystemId |
http://www.preprod.transora.com/util/pi/TDC_XML/4.0/CatalogueRequest_Envelope.dtd
|
|
|
|
Version |
<2> |
|
|
|
ServiceType
|
TransoraXML version 2.0
|
|
|
|
ServiceValue
|
DataCatalogue
|
|
|
|
ActionValue |
DataCatalogueItem
|
|
|
|
FromGLN
|
Manufacturer
|
|
|
|
ToGLN
|
Exchange
|
|
|
|
Inbound |
|
|
DestinationHeader
|
//Envelope/CatalogResponse/ResponseHeader/DestinationHeader
|
|
|
|
OverallResultCode |
//Envelope/CatalogResponse/ResponseDetail/OverallResultCode
|
|
|
|
OverallResultMessage
|
//Envelope/CatalogResponse/ResponseDetail/OverallResultMessage
|
|
|
|
CatalogName |
TransoraMessageArchiveCatalog |
|
|
|
MessageIdentifier
|
//Envelope/CatalogResponse/ResponseHeader/CorrelationIDHeader
|
|
|
|
Message Part Details |
|
The <messagePartDetails> property defines the
actions that a message sent or received by the data pool has to go
through
<messagePartDetailspartName>
Message Part details can have part names depending on
the message (xml) sent or received.
For example:
If the value messagePartDetails partName="CIN" then the
message is a Catalog Item Notification message.
If the value messagePartDetails partName="CIC" then the
message is a Catalog Item Confirmation message.
If the value messagePartDetails partName="CIS" then the
message is a Catalog Item Subscription message.
Similarly there are other partNames depending on the
data pool being used by the application.
<postProcessingDetails subPartName>
<MessagePartDetails partName> can have sub part
names within a part name depending on the message (xml) sent or received.
The sub part name is defined by the parameter <postProcessingDetails
subPartName>. This defines the processes that a message goes through
after it enters the GDS system. The post processing can be:
Workflow
Script Operation
Processor
Notification
For example:
A messagePartDetails partName="CIN", can have the
following value to the variable
<postProcessingDetailssubPartName>
<postProcessingDetails
subPartName="INITIAL_LOAD">
<workflow/>
</postProcessingDetails>
<postProcessingDetails
subPartName="NEW_ITEM">
<processor/>
</postProcessingDetails>
In the above example if the message is an Initial Load
CIN message, then it enters the default initial load workflow
If the message is a New Item CIN message, then it
invokes the defined service layer process.
|
|
|
|
|
|
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 Global Data Synchronization for
WebSphere Product Center v1.3.0 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 Struts v1.1
- Apache Commons-beanutils v1.6
- Apache Commons-digester v1.4
- Apache Xerces-j v2.4.0
- Apache XMLBeans v1.0.3
- Apache Commons-JXPath v1.2
- XML4J 4.3.3
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
notice to you in connection with this software:
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 other 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, on-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 APACHE NOTICES AND
INFORMATION
________________________________________________________________________
IBM Global Data Synchronization for
WebSphere Product Center also includes the following software, portions of which
were licensed from the World Wide Web Consortium (W3C):
: Apache XMLBeans v1.0.3
: Apache Commons-JXPath v1.2
: Apache XML4J v4.3.3
W3C SOFTWARE NOTICE AND LICENSE
http://www.w3.org/Consortium/Legal/
2002/copyright-software-20021231
This work (and included software,
documentation such as READMEs, or other related items) is being provided by the
copyright holders under the following license. By obtaining, using and/or
copying this work, you (the licensee) agree that you have read, understood, and
will comply with the following terms and conditions.
Permission to copy, modify, and distribute
this software and its documentation, with or without modification, for any
purpose and without fee or royalty is hereby granted, provided that you include
the following on ALL copies of the software and documentation or portions
thereof, including modifications:
1. The full text of this NOTICE in a
location viewable to users of the redistributed or derivative work.
2. Any pre-existing intellectual property
disclaimers, notices, or terms and conditions. If none exist, the W3C Software
Short Notice should be included (hypertext is preferred, text is permitted)
within the body of any redistributed or derivative code.
3. Notice of any changes or modifications
to the files, including the date changes were made. (We recommend you provide
URLs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS
PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY
OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR
DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS
OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT,
SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
DOCUMENTATION.
The name and trademarks of copyright
holders may NOT be used in advertising or publicity pertaining to the software
without specific, written prior permission. Title to copyright in this software
and any associated documentation will at all times remain with copyright
holders.
END OF W3C SOFTWARE NOTICES AND
LICENSE
________________________________________________________________________
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.
UNICODE, INC. LICENSE AGREEMENT - DATA
FILES AND SOFTWARE
Unicode Data Files include all data files
under the directories
http://www.unicode.org/Public/ and
http://www.unicode.org/reports/.
Unicode Software includes any source code
under the directories
http://www.unicode.org/Public/ and
http://www.unicode.org/reports/.
NOTICE TO USER: Carefully read the
following legal agreement. BY DOWNLOADING,
INSTALLING, COPYING OR OTHERWISE USING
UNICODE INC.'S DATA FILES ("DATA FILES"),
AND/OR SOFTWARE ("SOFTWARE"), YOU
UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND
BY, ALL OF THE TERMS AND CONDITIONS OF
THIS AGREEMENT. IF YOU DO NOT AGREE,
DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE
OR USE THE DATA FILES OR SOFTWARE.
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1991-2004 Unicode, Inc. All
rights reserved. Distributed under the
Terms of Use in
http://www.unicode.org/copyright.html.
Permission is hereby granted, free of
charge, to any person obtaining a copy of
the Unicode data files and associated
documentation (the "Data Files") or
Unicode software and associated
documentation (the "Software") to deal in the
Data Files or Software without
restriction, including without limitation the
rights to use, copy, modify, merge,
publish, distribute, and/or sell copies of
the Data Files or Software, and to permit
persons to whom the Data Files or
Software are furnished to do so, provided
that (a) the above copyright notice(s)
and this permission notice appear in all
copies of the Data Files or Software,
(b) both the above copyright notice(s) and
this permission notice appear in
associated documentation, and (c) there is
clear notice in each modified Data
File or in the Software as well as in the
documentation associated with the Data
File(s) or Software that the data or
software has been modified.
THE DATA FILES AND SOFTWARE ARE 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 THE DATA FILES OR
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
these Data Files or Software without prior
written authorization of the
copyright holder.
END OF ICU NOTICES AND LICENSE
IBM WebSphere Product Center includes
InstallShield 10.5 (the "Program") that was licensed by IBM from Macrovision
under the following terms and conditions:
The IBM license agreement and any
applicable notices on the web download page for this product refers You to this
file for details concerning terms and conditions applicable to software code
identified as excluded components in the License Information document and
included in InstallShield 10.5 (the "Program").
Notwithstanding the terms and conditions
of any other agreement you may have with IBM or any of its related or affiliated
entities (collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the terms and conditions of the
License Information document accompanying the Program and not the license terms
that may be contained in the notices below. The notices are provided for
informational purposes.
The Program includes the following
Excluded Components:
* Quick V1.0.1
* HSQLDB V1.7.1
JXML CODE. The Program is accompanied by
the following JXML software:
* Quick V1.0.1
IBM is required to provide you, as the
recipient of such software, with a copy of the following license from JXML:
Copyright (c) 1998, 1999, JXML, Inc.
All rights reserved.
Redistribution and use in source and
binary forms, with or without modification, are permitted provided that the
following conditions are met:
Redistributions of source code must retain
the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must
reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the
distribution.
All product materials mentioning features
or use of this software must display the following acknowledgement:
This product includes software developed
by JXML, Inc. and its contributors: http://www.jxml.com/mdsax/contributers.html
Neither name of JXML nor the names of its
contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY JXML, INC.
AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JXML OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
END OF JXML NOTICES AND INFORMATION
HSQL CODE. The Program is accompanied by
the following HSQL Development Group software:
* HSQLDB V1.7.1
IBM is required to provide you, as the
recipient of such software, with a copy of the following license from the HSQL
Development Group:
Copyright (c) 2001-2002, The HSQL
Development Group
All rights reserved.
Redistribution and use in source and
binary forms, with or without modification, are permitted provided that the
following conditions are met:
Redistributions of source code must retain
the above copyright notice, this list of conditions and the following
disclaimer.
Redistributions in binary form must
reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the
distribution.
Neither the name of the HSQL Development
Group nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT
HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL HSQL
DEVELOPMENT GROUP, HSQLDB.ORG, OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
END OF HSQL NOTICES AND INFORMATION
________________________________________________________________________
All trademarks and registered trademarks
mentioned herein are the property of their respective
owners.
