Installing InfoSphere MDM Version 11 on Linux using the custom installation process

System requirements for InfoSphere Master Data Management

http://www-01.ibm.com/support/docview.wss?uid=swg27035486

Hosts File

The "/etc/hosts" file must contain a fully qualified name for the server.

192.168.X.X mdm mdm

Install IBM Java SDK 6

ibm-java-x86_64-sdk-6.0-11.0

Installation Manager

IBM InfoSphere Master Data Management (InfoSphere MDM) version 11.0 is a J2E application. Like any J2E product, it requires an application server and database. Before you can begin to install InfoSphere MDM version 11.0 using the custom install process, you must first:

Install IBM Installation Manager on your system.
Properly prepare IBM WebSphere Application Server, Oracle database.

Downloading IBM Installation Manager

Before installing InfoSphere MDM version 11.0, you must first download and install IBM Installation Manager version 1.6.

If you do not have IBM Installation Manager, download it using one of the following options:

Download IBM Installation Manager 1.6 from the IBM Passport Advantage web site. Search for and download the package associated with part number CIM79ML.
Extract the IBM Installation Manager 1.6 installation package from the InfoSphere MDM 11.0 part number CIM67ML/disk1/InstallerImage_linux_gtk_x86_64. When you download the InfoSphere MDM 11.0 installation packages, part numberCIM67ML is one of the options.

Installing IBM Installation Manager

It is strongly recommended use a non-root user to perform the InfoSphere MDM 11.0 custom install. In this case, you should also install WebSphere Application Server 8.5.0.2 and IBM Installation Manager using a non-root. We recommend creating wsadmin (a WebSphere Application Server administrative user) to install IBM Installation Manager, WebSphere Application Server 8.5.0.2, and InfoSphere MDM 11.0.

Create the wsadmin user.
Log in using the wsadmin user.
Install IBM Installation Manager using the command $./userinst

When installing IBM Installation Manager, we recommend using the following directories:

IBM Installation Manager shared folder: /home/wsadmin/IBM/IMShared
IBM Installation Manager data location: /home/wsadmin/var/ibm/InstallationManager
IBM Installation Manager installation home directory: /home/wsadmin/IBM/InstallationManager/eclipse

Important: Make sure that you have at least 5 GB of free disk space in /home/wsadmin before installing InfoSphere MDM 11.0.

After installing IBM Installation Manager, start it using the command /home/wsadmin/IBM/InstallationManager/eclipse/IBMIM

Troubleshooting tip: You might encounter the following problem when running IBM Installation Manager in GUI mode:

java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:

/appdata/mdmadmin/software/v11/MDM/disk1/InstallerImage_linux_gtk_x86_64/configuration/org.eclipse.osgi/bundles/92/1/.cp/libswt-pi-gtk-3650.so (libXtst.so.6: cannot open shared object file: No such file or directory)

swt-pi-gtk (Not found in java.library.path)

/tmp/swtlib-64/libswt-pi-gtk-3650.so (libXtst.so.6: cannot open shared object file: No such file or directory)

/tmp/swtlib-64/libswt-pi-gtk.so (/tmp/swtlib-64/liblibswt-pi-gtk.so.so: cannot open shared object file: No such file or directory)

To fix this issue, install the following RPMs:

sudo yum install xorg-x11-fonts-Type1
sudo yum install PackageKit-gtk-module.x86_64
sudo yum install libcanberra-gtk2.x86_64

Installing IBM WebSphere Application Server 8.5.0.2 Network Deployment

To install WebSphere Application Server 8.5.0.2 ND:

Download the following parts from the IBM Passport Advantage web site:

WebSphere Application Server 8.5:
CI6Y3ML
CI6Y4ML
CI6Y5ML
WebSphere Application Server 8.5.0.2 FP (fix pack)
8.5.0-WS-WASSupplements-FP0000002-part1
8.5.0-WS-WASSupplements-FP0000002-part2

Extract the downloaded package files.
While logged in as the wsadmin user, start IBM Installation Manager using the following command:$/home/wsadmin/IBM/InstallationManager/eclipse/IBMIM

The IBM Installation Manager window opens.

Select File -> Preferences -> Repositories, then add the repositories for WebSphere Application Server 8.5 ND and WebSphere Application Server 8.5.0.2 FP.

Select WebSphere Application Server Network Deployment Version 8.5.0.2.

Read and accept the license agreement.

Specify the Shared Resources directory.

Specify the WebSphere Application Server 8.5.0.2 installation home directory.

Select the languages to install.

Select the WebSphere Application Server features to install.

Tip: We recommend that you accept the default installation features.

Important: Do not remove the 'Stand-alone thin clients and resource adapters' feature from the WebSphere Application Server installable features list. If it is removed, the InfoSphere MDM installation application will not be able to communicate with WebSphere Application Server during InfoSphere MDM installation.

Click Install to install WebSphere Application Server 8.5.0.2 Network Deployment.

Creating WebSphere Application Server Deployment Manager and Application Server profiles

After completing the installation for WebSphere Application Server 8.5.0.2 Network Deployment, you must create Deployment Manager and Application Server profiles.

You can use the WebSphere Application Server Profile Creation Tool in either Console mode or GUI mode.

Important: Enable WebSphere Application Server administration security at the same time that you create the WebSphere Application Server profiles.

Create the Deployment Manager profile. In console mode, run the following command:

./manageprofiles.sh -create -profileName Dmgr1 -profilePath /home/wsadmin/IBM/WebSphere/AppServer/profiles/Dmgr1 -templatePath /home/wsadmin/IBM/WebSphere/AppServer/profileTemplates/management -serverType DEPLOYMENT_MANAGER -enableAdminSecurity true -adminUserName mdmadmin -adminPassword mdmadmin

The command will create the Deployment Manager profile at /home/wsadmin/IBM/WebSphere/AppServer/profiles/Dmgr1 and enable WebSphere Application Server administration security, and also create the mdmadmin user in a WebSphere Application Server 8.5.0.2 federated repository (internal LDAP).

Start the Deployment Manager. Run the command $/home/wsadmin/IBM/WebSphere/AppServer/profiles/Dmgr1/bin/startManager.sh

The Deployment Manager must be started before you create the WebSphere Application Server 8.5.0.2 Application Server profile in console mode.

Create the Application Server profile. In console mode, run the following command:

./manageprofiles.sh -create -profileName Node1 -profilePath /home/wsadmin/IBM/WebSphere/AppServer/profiles/Node1 -templatePath /home/wsadmin/IBM/WebSphere/AppServer/profileTemplates/managed -federateLater false -dmgrAdminUserName mdmadmin -dmgrAdminPassword mdmadmin -dmgrHost mdm -dmgrPort 8879

where:

mdm is the hostname of the machine where you have installed WebSphere Application Server 8.5.0.2.
8879 is a SOAP port to connect to the Deployment Manager.

Start the WebSphere Application Server 8.5.0.2 node agent. Run the command$/home/wsadmin/IBM/WebSphere/AppServer/profiles/Node1/bin/startNode.sh

Preparing IBM WebSphere Application Server 8.5.0.2 Network Deployment for MDM11.0 installation.

Ensure that the WebSphere Application Server 8.5.0.2 node agent is running. If not, start the node agent using the command$/home/wsadmin/IBM/WebSphere/AppServer/profiles/Node1/bin/startNode.sh
Create a WebSphere Application Server 8.5.0.2 environment variable called ORACLE_JDBC_DRIVER_PATH.
Log in to the WebSphere Application Server 8.5.0.2 administration console.
Select Environment -> WebSphere variables.

Specify the value for ORACLE_JDBC_DRIVER_PATH. Use the directory path value for the location of the Oracle thin or oci8 JDBC driver.

Tip: Ensure that the ORACLE_JDBC_DRIVER_PATH is set properly. If the JDBC driver jar file location is /u01/app/oracle/product/11.2.0/db_1/jdbc/lib/ojdbc6.jar, then the ORACLE_JDBC_DRIVER_PATH has to be set to /u01/app/oracle/product/11.2.0/db_1

Important: Ensure that you install the Full Oracle client and not Oracle Instant client to be used with InfoSphere MDM V11.0. Oracle Instant client is not suitable for installing InfoSphere MDM V11.0 because it does not include the sqlldr utility and also because it has sqlplus and JDBC drivers in different directories than where the InfoSphere MDM installation process expects it to be.

Click Apply -> Save changes.
Use the Deployment Manager to synchronize the managed node (or all nodes if this is a cluster deployment).

Preparing the Oracle database for InfoSphere MDM 11.0 installation

To prepare an Oracle database for InfoSphere MDM 11.0 installation, there are two major tasks:

Install and configure Oracle database server.

Installing and configuring Oracle database server

Install Oracle database server using its standard installation instructions.
Create the Oracle MDM database.

Important: When you create the database, specify UTF-8 encoding for InfoSphere MDM 11.0. For example: CREATE DATABASEdname…CHARACTER SET AL32UTF8

If you do not specify UFT-8 encoding, then Hybrid MDM features might not work properly.

Create the Oracle database schema to be used by InfoSphere MDM 11.0.
InfoSphere MDM 11.0 installation requires that the Oracle database schema is created using the scriptcreate_schema_ora.sql, which is part of the InfoSphere MDM 11.0 distribution.

Tip: You can obtain create_schema_ora.sql from the InfoSphere MDM 11.0 Startup Toolkit.

Download the Startup Toolkit, IBM part CIM6EML, from IBM Passport Advantage
Install the Startup Toolkit using IBM Installation Manager.

As part of installing the InfoSphere MDM 11.0 Startup Toolkit, IBM Installation Manager extracts some useful InfoSphere MDM assets, including create_schema_ora.sql.

After the installation of MDM11.0 Startup Toolkit is complete, and assuming that the installation home directory was /home/wsadmin/IBM/MDM_kit/StartupKit, then the create_schema_ora.sql script will be located at /home/wsadmin/IBM/MDM_kit/StartupKit/CoreData/Full/Oracle/Standard/ddl/create_schema_ora.sql

Modify create_schema_ora.sql to replace placeholders with the correct values:

<TABLE_SPACE> - Replace with the tablespace name for user tables data, replace with the default valueDATSPACE.
<TABLE_SPPMD> - Replace with the tablespace name for EME user tables data, replace with the default value EMESPACE1.
<INDEX_SPACE> - Replace with the tablespace name for index data, replace with the default valueIDXSPACE.
<TABLE_SPPMI> - Replace with the tablespace name for EME index data, replace with the default valueEMESPACE2.
<LONG_SPACE> - Replace with the tablespace name for CLOB and XML datatypes, replace with the default value LOBSPACE.
<TABLE_MDS4K> - Replace with the tablespace name for user tables 4K reference on sto files as <TBS4K>, replace with the default value TBS4K.
<TABLE_MDS8K> - Replace with the tablespace name for user tables 8K reference on sto files as <TBS8K>, replace with the default value TBS8K.
<TABLE_SPMDS> - Replace with the tablespace name for MDS user tables 16K reference on sto files as <TBS16K>, replace with the default value TBS16K.
<SCHEMA> - Replace with the user name being created.
<NEWPASSWORD> - Replace with the password for the user name just created.
<TABLESPACE_LOCATION> - Replace with the location of the tablespace. For example:/home/oracle/oradata/<dbname>

Note: These placeholders must be replaced before a database administrator (DBA) can runcreate_schema_ora.sql.

Tip: See the InfoSphere MDM documentation for more details on the table spaces used by the InfoSphere MDM 11.0 database component -http://pic.dhe.ibm.com/infocenter/mdm/v11r0/topic/com.ibm.swg.im.mdmhs.release.install.doc/Topics/preparing_oracle_for_installation.html?resultof=%22%63%72%65%61%74%65%5f%73%63%68%65%6d%61%5f%6f%72%61%22%20

Run the following SQL before running create_schema_ora.sql. This SQL ensures that the cache size is set to the size required to run create_schema_ora.sql successfully.

ALTER SYSTEM SET db_4k_cache_size=128M;

ALTER SYSTEM SET db_16k_cache_size=128M

Ensure that the user who is supposed to run create_schema_ora.sql has sufficient administrative privileges to create users and tablespaces.
Run create_schema_ora.sql to create the schema for the InfoSphere MDM 11.0 database component.

Login as the wsadmin user and add the following lines at the end of the ".bash_profile" file, remembering to adjust them for your specific installation.

#vi .bash_profile

Add following line

# Wsadmin Settings

umask 022

# wsadmin Settings

TMP=/tmp; export TMP

TMPDIR=$TMP; export TMPDIR

ORACLE_HOSTNAME=mdm; export ORACLE_HOSTNAME

ORACLE_UNQNAME=mdm; export ORACLE_UNQNAME

ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE

ORACLE_HOME=$ORACLE_BASE/product/11.2.0/db_1; export ORACLE_HOME

ORACLE_SID=mdm; export ORACLE_SID

PATH=/usr/sbin:$PATH; export PATH

PATH=$ORACLE_HOME/bin:$PATH; export PATH

LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH

CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH

Installing MDM11.0 using custom install

After preparing WebSphere Application Server 8.5.0.2 Network Deployment, Oracle database, WebSphere MQ, and LDAP server, you now can use IBM Installation Manager to install InfoSphere MDM 11.0.

Download the following InfoSphere MDM version 11.0 Standard Edition and Advanced Edition parts from the IBM Passport Advantage web site:

CIR9NML
CIR9PML
CIR9QML
CIR9RML
CIR9SML

Extract all parts packages into the same directory. All of the disk images (disk1, disk2, disk3, disk4, and disk5) must be in the same location.

Tip: If you are installing InfoSphere MDM 11.0 using the same IBM Installation Manager instance that you used before for installing WebSphere Application Server 8.5.0.2 or other IBM products, then the Shared Resource Directory field will be disabled and you cannot change the value. You will be forced use the same shared resource directory to install multiple packages such as WebSphere Application Server 8.5.0.2 and InfoSphere MDM 11.0.

To avoid this, we recommend using a separate IBM Installation Manager data location and a separate Shared Resource Directory when installing InfoSphere MDM. This strategy could help to better manage installation data backups for your IBM products. The IBM Installation Manager data location should be changed before starting IBM Installation Manager.

Locate and edit the file /home/wsadmin/IBM/InstallationManager/eclipse/configuration/config.ini,
Comment out the previously used data location and create new entry specifically for InfoSphere MDM. For example:

#cic.appDataLocation=/home/wsadmin/var/ibm/InstallationManager

cic.appDataLocation=/home/wsadmin/var/ibm/InstallationManager_MDM

Before Starting the installation of MDM server change the SOAP connector timeout value

If you are using WebSphere Application Server network deployment, change the SOAP timeout value in both Dmgr and Node1 profiles.

1. For Dmgr, go to <WAS_PROFILE_HOME>/Dmgr01/properties/soap.client.props. By default, the com.ibm.SOAP.requestTimeout property is set to com.ibm.SOAP.requestTimeout=180. Change the 180 value to 0, which means no time out or unlimited. For example, com.ibm.SOAP.requestTimeout=0

2. For AppSrv, go to <WAS_PROFILE_HOME>/Node1/properties/soap.client.props. Change the 180 value in the com.ibm.SOAP.requestTimeout=180 setting to 0. For example, com.ibm.SOAP.requestTimeout=0

Start IBM Installation Manager.

Select File -> Preferences -> Repositories.
Add the repository for InfoSphere MDM 11.0 Standard Edition and Advanced Edition, ./disk1/diskTag.inf.

Select the InfoSphere MDM Standard Edition or Advanced Edition Version 11.0 installation package.

Read and accept the license agreement.

Specify a value for the Shared Resource Directory.

Specify the InfoSphere MDM installation home directory.

Choose the languages to install.

Choose the InfoSphere MDM features to install. For example, select MDM Database, MDM Operational Server, and all 6 user interface applications.

Note: Business Administration UI, Data StewardShip UI, and Product Maintenance UI are physical MDM applications. Inspector, Enterprise Viewer, Web Reports, Provider Direct are virtual MDM applications.

Specify the parameters of your database deployment.
Click Test Connection to ensure that you have typed the parameters correctly, then click Next.

Note: The installation application verifies the Oracle database home directory input by locating the <ORACLE_CLIENT_HOME>/oracore folder. For example, if <ORACLE_CLIENT_HOME> is /u01/app/oracle/product/11.2.0/db_1/ then the installation application will try to locate/u01/app/oracle/product/11.2.0/db_1/oracore. If the installer cannot find <ORACLE_CLIENT_HOME>/oracore, then there will be a connection error, "The database home is not valid."

Specify additional InfoSphere MDM configuration parameters as required for your deployment.

Tip: Click the help button (?) for details about input parameters.

Specify the connection parameters for the WebSphere Application Server Deployment Manager (or server1 if using WebSphere Application Server Base), then click Retrieve Host Details.

Select a cell and node from the Cell and Node lists or type the server name in the Server field.

Tip: When installing InfoSphere MDM on a development or QA environment, we recommend specifying separate servers or separate clusters for the InfoSphere MDM back end (the operational server and database) and the user interface applications. For the production environment, you can contact the InfoSphere MDM performance team for their recomendations about high availablility environments for deploying InfoSphere MDM.

In this example, we are deploying the InfoSphere MDM back end on server 'mdm-s-E550', the physical MDM UIs on server 'UIs-s1-E550', and the virtual MDM UIs on server 'UIs-s2-E550'.

Click Verify MDM Instance on Server to test whether InfoSphere MDM is installed already on the selected target server. If the target verification is successful, click Next.

Continue specifying configuration parameters. Click Next.

Specify a deployment target for the Business Administration user interface.

Specify a deployment target for the Data Stewardship user interface.

Specify a deployment target for the Product Maintenance user interface.

Specify a deployment target for the Inspector user interface.

Specify a deployment target for the Enterprise Viewer user interface.

Specify a deployment target for the Web Reports user interface.

Click Install and watch the installation progress.

Note: Installation can take 30 to 40 minutes, depending on your installation environment and deployment settings.

After the IBM Installation Manager finishes installing InfoSphere MDM 11.0, check the Installation Verification Tool (IVT) test results.

To check physical MDM IVT, go to /home/wsadmin/IBM/MDM/IVT/testCases/xml/response00001 and look at the following response files:

For example, if the InfoSphere MDM 11.0 installation is successful, then the response files will be similar to the following:

ResponseTCRMaddcontract.xml

<?xml version="1.0" encoding="UTF-8"?>

<ResultCode>SUCCESS</ResultCode>

<requesterName>mdmadmin</requesterName>

<userRole>mdm_admin</userRole>

</DWLControl>

</ResponseControl>

<RequestType>addContract</RequestType>

<ResultCode>SUCCESS</ResultCode>

</TxResult>

<BillingValue>Payroll Deduction</BillingValue>

<ContractLastUpdateUser>mdmadmin</ContractLastUpdateUser>

<CurrencyValue>U.S. Dollar</CurrencyValue>

<FrequencyModeValue>Annual</FrequencyModeValue>

</DWLStatus>

<ContractComponentLastUpdateUser>mdmadmin</ContractComponentLastUpdateUser>

<ContractStatusValue>Terminated</ContractStatusValue>

<ProductValue>Endowment</ProductValue>

</DWLStatus>

<ContractPartyRoleLastUpdateUser>mdmadmin</ContractPartyRoleLastUpdateUser>

<RoleValue>Insured Primary</RoleValue>

</DWLStatus>

<ClientPotentialValue>Client</ClientPotentialValue>

<ClientStatusValue>Active</ClientStatusValue>

<DisplayName>Paint</DisplayName>

<PartyLastUpdateUser>mdmadmin</PartyLastUpdateUser>

<PreferredLanguageValue>English</PreferredLanguageValue>

<StatementFrequencyValue>Annually</StatementFrequencyValue>

<AgeVerifiedWithValue>Birth Certificate</AgeVerifiedWithValue>

<HighestEducationValue>College Diploma</HighestEducationValue>

<PersonLastUpdateUser>mdmadmin</PersonLastUpdateUser>

</DWLStatus>

<AddressGroupLastUpdateUser>mdmadmin</AddressGroupLastUpdateUser>

<AddressUsageValue>Primary Residence</AddressUsageValue>

<LocationGroupLastUpdateUser>mdmadmin</LocationGroupLastUpdateUser>

<UndeliveredReasonValue>Moved</UndeliveredReasonValue>

</DWLStatus>

<AddressLastUpdateUser>mdmadmin</AddressLastUpdateUser>

<AddressLineOne>12 Pinto Rd</AddressLineOne>

<City>Toronto</City>

<CountryValue>Canada</CountryValue>

<ResidenceValue>Apartment</ResidenceValue>

<ZipPostalCode>ZZZYYY</ZipPostalCode>

</DWLStatus>

</TCRMAddressBObj>

</TCRMPartyAddressBObj>

<IdentificationStatusValue>Active</IdentificationStatusValue>

<IdentificationValue>Social Security Number</IdentificationValue>

<PartyIdentificationLastUpdateUser>mdmadmin</PartyIdentificationLastUpdateUser>

</DWLStatus>

</TCRMPartyIdentificationBObj>

<LastName>Paint</LastName>

<LastUpdatedBy>mdmadmin</LastUpdatedBy>

<NameUsageValue>Legal</NameUsageValue>

<PersonNameLastUpdateUser>mdmadmin</PersonNameLastUpdateUser>

<StdLastName>Paint</StdLastName>

</DWLStatus>

</TCRMPersonNameBObj>

</TCRMPersonBObj>

</TCRMContractPartyRoleBObj>

</TCRMContractComponentBObj>

</TCRMContractBObj>

</ResponseObject>

</TxResponse>

</TCRMService>

ResponseTCRMaddOrganization.xml

<?xml version="1.0" encoding="UTF-8"?>

<ResultCode>SUCCESS</ResultCode>

<requesterName>mdmadmin</requesterName>

<userRole>mdm_admin</userRole>

</DWLControl>

</ResponseControl>

<RequestType>addOrganization</RequestType>

<ResultCode>SUCCESS</ResultCode>

</TxResult>

<ClientImportanceValue>Medium</ClientImportanceValue>

<ClientPotentialValue>Suspect</ClientPotentialValue>

<DisplayName>Active</DisplayName>

<PartyLastUpdateUser>mdmadmin</PartyLastUpdateUser>

<PreferredLanguageValue>English</PreferredLanguageValue>

<BuySellAgreementValue>Cross Purchase Agreement</BuySellAgreementValue>

<IndustryValue>Trade</IndustryValue>

<OrganizationLastUpdateUser>mdmadmin</OrganizationLastUpdateUser>

<OrganizationValue>Corporation</OrganizationValue>

</DWLStatus>

<AddressGroupLastUpdateUser>mdmadmin</AddressGroupLastUpdateUser>

<AddressUsageValue>Primary Residence</AddressUsageValue>

<LocationGroupLastUpdateUser>mdmadmin</LocationGroupLastUpdateUser>

</DWLStatus>

<AddressLastUpdateUser>mdmadmin</AddressLastUpdateUser>

<AddressLineOne>115 Milan St.</AddressLineOne>

<City>Paris</City>

<CountryValue>Canada</CountryValue>

<ResidenceValue>Detached House</ResidenceValue>

</DWLStatus>

</TCRMAddressBObj>

</TCRMPartyAddressBObj>

<IdentificationStatusValue>Active</IdentificationStatusValue>

<IdentificationValue>Corporate Tax Identification</IdentificationValue>

<PartyIdentificationLastUpdateUser>mdmadmin</PartyIdentificationLastUpdateUser>

</DWLStatus>

</TCRMPartyIdentificationBObj>

<NameUsageValue>Legal</NameUsageValue>

<OrganizationName>Active</OrganizationName>

<OrganizationNameLastUpdateUser>mdmadmin</OrganizationNameLastUpdateUser>

<SOrganizationName>ACTIVE</SOrganizationName>

</DWLStatus>

</TCRMOrganizationNameBObj>

</TCRMOrganizationBObj>

</ResponseObject>

</TxResponse>

</TCRMService>

ResponseTCRMaddPerson.xml

<?xml version="1.0" encoding="UTF-8"?>

<ResultCode>SUCCESS</ResultCode>

<requesterName>mdmadmin</requesterName>

<userRole>mdm_admin</userRole>

</DWLControl>

</ResponseControl>

<RequestType>addPerson</RequestType>

<ResultCode>SUCCESS</ResultCode>

</TxResult>

<ClientImportanceValue>Medium</ClientImportanceValue>

<ClientPotentialValue>Client</ClientPotentialValue>

<ClientStatusValue>Active</ClientStatusValue>

<DisplayName>Vanessa Dana</DisplayName>

<PartyLastUpdateUser>mdmadmin</PartyLastUpdateUser>

<PreferredLanguageValue>English</PreferredLanguageValue>

<StatementFrequencyValue>Annually</StatementFrequencyValue>

<AgeVerifiedWithValue>Passport</AgeVerifiedWithValue>

<BirthPlaceValue>Afghanistan</BirthPlaceValue>

<CitizenshipValue>Afghanistan</CitizenshipValue>

<HighestEducationValue>University Degree</HighestEducationValue>

<MaritalStatusValue>Single</MaritalStatusValue>

<PersonLastUpdateUser>mdmadmin</PersonLastUpdateUser>

</DWLStatus>

<GivenNameOne>Vanessa</GivenNameOne>

<LastUpdatedBy>mdmadmin</LastUpdatedBy>

<NameUsageValue>Legal</NameUsageValue>

<PersonNameLastUpdateUser>mdmadmin</PersonNameLastUpdateUser>

<StdGivenNameOne>Vanessa</StdGivenNameOne>

</DWLStatus>

</TCRMPersonNameBObj>

</TCRMPersonBObj>

</ResponseObject>

</TxResponse>

</TCRMService>

To check virtual IVT results, go to /opt/IBM/MDM/E550/mdm/IVT/testCases/xml_virtual/response and look at the response files.

if the InfoSphere MDM 11.0 installation is successful, then the response files will be similar to the following:

Responsepingdb_request.xml

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><port:virtualInteractionResponse xmlns:port="http://www.ibm.com/mdm/port/VirtualBridge"><ResponseControl xmlns="http://www.ibm.com/mdm/schema"><ResultCode>SUCCESS</ResultCode><ServiceTime>2563</ServiceTime><DWLControl><requesterName>mdmadmin</requesterName><requesterLanguage>100</requesterLanguage><requesterLocale>en</requesterLocale><userRole>mdm_admin</userRole><requestID>1</requestID></DWLControl></ResponseControl><TxResult xmlns="http://www.ibm.com/mdm/schema"><ResultCode>SUCCESS</ResultCode></TxResult><VirtualMDMBObj xmlns="http://www.ibm.com/mdm/schema"><ComponentID>4444</ComponentID><Data>T0sK</Data></VirtualMDMBObj></port:virtualInteractionResponse></soapenv:Body></soapenv:Envelope>

Installation Verification Test (IVT) does not delete the IVT data after the test is complete

IVT data must be manually removed. There is a restriction while accessing the database when IVT is running, because the database is not in the path.

For DB2, follow these steps :

1. At a command prompt, type: db2 connect to <DATABASE_NAME> user <DATABASE_USER> using <DATABASE_PASSWORD>

2. Go to: cd <MDM_HOME>/IVT/sql and type: run db2 -tvf deleteIVTData.sql

For Oracle:

1. Go to: cd <MDM_HOME>/IVT/sql

2. At the command prompt, type:

sqlplus <DATABASE_USER>/<DATABASE_PASSWORD>@<TNS_NAME> @deleteIVTData.sql;

Search This Blog

Guru Of Geeks