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

1 like Updated 7/23/14, 11:28 AM by EGorelenkoTags:

 

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

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:

  1. Install IBM Installation Manager on your system.
  2. Properly prepare IBM WebSphere Application Server, Oracle database and, optionally, LDAP Server and Websphere MQ Server.

 

Downloading IBM Installation Manager

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

Note: If you already have IBM Installation Manager 1.5.3 on your system as a result of having previously installed WebSphere Application Server 8.5.0.2, then you can use IBM Installation Manager 1.5.3 to install InfoSphere MDM 11.0.

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 number CIM67ML 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.

  1. Create the wsadmin user.
  2. Log in using the wsadmin user.
  3. 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: /opt/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.

  1. After installing IBM Installation Manager, start it using the command /opt/IBM/InstallationManager/eclipse/IBMIM

Tip: If you use a remote Linux box, you might need to use PuTTY, Cygwin, Exceed, SSH or other tools to run X server to enable you to run IBM Installation Manager in GUI mode. If you are not able to run IBM Installation Manager in GUI mode, then you can install WebSphere Application Server 8.5.0.2 and InfoSphere MDM 11.0 using IBM Installation Manager in silent mode. For information about using silent mode to install MDM11.0, see the InfoSphere MDM 11.0 documentation about silent installations.

For more information about IBM Installation Manager 1.6, see the IBM Installation Manager 1.6 documentation.

 

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:

  1. 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

Note: Installing MDM11.0 on WebSphere Application Server 8.5.5.1 ND is also supported. Please follow this technote if using WebSphere Application Server 8.5.5.1 ND - http://www-01.ibm.com/support/docview.wss?uid=swg21651788

  • WebSphere Application Server 8.5.5.1 FP (fix pack)
  • 8.5.5-WS-WASSupplements-FP0000001-part1
  • 8.5.5-WS-WASSupplements-FP0000001-part2
  1. Extract the downloaded package files.
  2. While logged in as the wsadmin user, start IBM Installation Manager using the following command: $/opt/IBM/InstallationManager/eclipse/IBMIM

The IBM Installation Manager window opens.

 

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

 

  1. Select WebSphere Application Server Network Deployment Version 8.5.0.2.

 

  1. Read and accept the license agreement.

 

  1. Specify the Shared Resources directory.





 

  1. Specify the WebSphere Application Server 8.5.0.2 installation home directory.

 

  1. Select the languages to install.

 

  1. 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.

 

  1. 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.

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

./manageprofiles.sh -create -profileName Dmgr1 -profilePath /home/wsadmin/WAS8502NDProfiles/Dmgr1 -templatePath /opt/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/WAS8502NDProfiles/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).

  1. Start the Deployment Manager. Run the command $/home/wsadmin/WAS8502NDProfiles/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.

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

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

where:

  • acmelab.com 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.
  1. Start the WebSphere Application Server 8.5.0.2 node agent. Run the command $/home/wsadmin/WAS8502NDProfiles/Node1/bin/startNode.sh

 

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

  1. 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/WAS8502NDProfiles/Node1/bin/startNode.sh
  2. Create a WebSphere Application Server 8.5.0.2 environment variable called ORACLE_JDBC_DRIVER_PATH.
  3. Log in to the WebSphere Application Server 8.5.0.2 administration console.
  4. Select Environment -> WebSphere variables.

 

  1. 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 /home/oracle/app/oracle/product/11.2.0/client_2/jdbc/lib/ojdbc6.jar, then the ORACLE_JDBC_DRIVER_PATH has to be set to /home/oracle/app/oracle/product/11.2.0/client_2

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.

 

  1. Click Apply -> Save changes.
  2. 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:

  1. Install and configure Oracle database server.
  2. Install and configure Oracle Runtime Client.

 

Installing and configuring Oracle database server

  1. Install Oracle database server using its standard installation instructions.
  2. 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.

  1. 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 script create_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.

  1. Download the Startup Toolkit, IBM part CIM6EML, from IBM Passport Advantage
  2. 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 /opt/IBM/MDM/StartupKit, then the create_schema_ora.sql script will be located at /opt/IBM/MDM/StartupKit/CoreData/Full/Oracle/Standard/ddl/create_schema_ora.sql

  1. 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 value DATSPACE.
  • <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 value IDXSPACE.
  • <TABLE_SPPMI> - Replace with the tablespace name for EME index data, replace with the default value EMESPACE2.
  • <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 run create_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

  1. 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=1024M;

ALTER SYSTEM SET db_16k_cache_size=1024M;l

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

 

Installing and configuring the Oracle Runtime Client

You must install an Oracle Runtime Client in the following locations:

  • On machines where WebSphere Application Server 8.5.0.2 Deployment Manager is deployed and where the InfoSphere MDM 11.0 Installer will be run. The InfoSphere MDM 11.0 installation application uses Oracle Runtime Client to run sqlplus to create tables and to load physical MDM data.
  • On each machine where WebSphere Application Server 8.5.0.2 managed nodes are deployed. Oracle Runtime Client is required to provide a JDBC driver to manage database connections. Each managed node locates JDBC the driver using the ORACLE_JDBC_DRIVER_PATH environment variable that you set up earlier in this process.

 

  1. For each of the locations described above, use Oracle universal installer to install Oracle Runtime Client.

Important: When installing Oracle Runtime Client, make sure the sqlldr (SQL Loader) utility is included in the installation and available at <ORACLE_CLIENT_HOME>/bin/sqlldr. The InfoSphere MDM  installation application locates and invokes sqlldr to insert physical MDM data into the database.

  1. After installing Oracle Runtime Client on the machine where WebSphere Application Server Deployment Manager is deployed and where the InfoSphere MDM 11.0 installation application is supposed to run, create the TNS name entry in the <ORACLE_CLIENT_HOME>/network/admin/tnsnames.ora file to connect the Oracle Runtime Client with the remote Oracle database.

For example:

ACMEDB =

 (DESCRIPTION =

   (ADDRESS_LIST =

     (ADDRESS = (PROTOCOL = TCP)(HOST = acmedb.com)(PORT = 1521))

   )

 (CONNECT_DATA =

   (SERVICE_NAME = acmedb)

 )

)

  1. Test the database connection using sqlplus. Ensure that the connection works and that the InfoSphere MDM 11.0 installation application can use it.

    To test the connection with sqlplus, run:

sqlplus myusername/mypassword@TNS_NAME;

Tip: Make sure that the sqlplus utility is included in a PATH. By including the sqlplus utility in a PATH, the InfoSphere MDM installer can locate sqlplus and use it to automatically create tables and insert data for physical MDM during the InfoSphere MDM installation. For example:

If <ORACLE_CLIENT_HOME> is /home/oracle/app/oracle/product/11.2.0/client_2

[wsadmin@acme.com ~]$ echo $PATH

/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/wsadmin/sqllib/bin:/home/wsadmin/sqllib/adm:/home/wsadmin/sqllib/misc:/home/wsadmin/bin:/opt/mqm/bin:/home/oracle/app/oracle/product/11.2.0/client_2/bin:/opt/ibm/SDP/jdk/bin


 

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.

  1. 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
  1. 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.
  2. If your deployment scenario uses remote WebSphere MQ server, refer to Installing MDM11.0 with using WebSphere MQ.
  3. If your deployment scenario uses remote LDAP authentication, refer to Installing MDM11.0 with using external LDAP.

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.

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

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

cic.appDataLocation=/home/egorelen/var/ibm/InstallationManager_MDM11)

  1. Start IBM Installation Manager.

 

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

 

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

 

  1. Read and accept the license agreement.

 

  1. Specify a value for the Shared Resource Directory.

 

  1. Specify the InfoSphere MDM installation home directory.

 

  1. Choose the languages to install.

 

  1. 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.

 

  1. Specify the parameters of your database deployment.
  2. 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 /home/oracle/app/oracle/product/11.2.0/client_2 then the installation application will try to locate /home/oracle/app/oracle/product/11.2.0/client_2/oracore. If the installer cannot find <ORACLE_CLIENT_HOME>/oracore, then there will be a connection error, "The database home is not valid."

 

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

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

 

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

 

  1. 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'.

 

  1. 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.

 

  1. Continue specifying configuration parameters. Click Next.

For more information about the mdmadmin user, see Managing security users and groups when Installing MDM11.0.

 

  1. Specify a deployment target for the Business Administration user interface.

 

  1. Specify a deployment target for the Data Stewardship user interface.

 

  1. Specify a deployment target for the Product Maintenance user interface.

 

  1. Specify a deployment target for the Inspector user interface.

 

  1. Specify a deployment target for the Enterprise Viewer user interface.

 

  1. Specify a deployment target for the Web Reports user interface.

 

  1. Click Install and watch the installation progress.

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

 

 

  1. 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 /opt/IBM/MDM/E550/mdm/IVT/testCases/xml/response 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"?>

<TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="tCRMResponse.xsd">

    <ResponseControl>

        <ResultCode>SUCCESS</ResultCode>

        <ServiceTime>1161</ServiceTime>

        <DWLControl>

            <requesterLanguage>100</requesterLanguage>

            <requesterLocale>en</requesterLocale>

            <requesterName>mdmadmin</requesterName>

            <requestID>22222</requestID>

            <userRole>mdm_admin</userRole>

            <requesterTimeZone>EST5EDT</requesterTimeZone>

        </DWLControl>

    </ResponseControl>

    <TxResponse>

        <RequestType>addContract</RequestType>

        <TxResult>

            <ResultCode>SUCCESS</ResultCode>

        </TxResult>

        <ResponseObject>

            <TCRMContractBObj>

                <BillingType>5</BillingType>

                <BillingValue>Payroll Deduction</BillingValue>

                <ContractIdPK>111111111</ContractIdPK>

                <ContractLastUpdateDate>2013-05-16 12:18:21.216</ContractLastUpdateDate>

                <ContractLastUpdateTxId>263336872110090101</ContractLastUpdateTxId>

                <ContractLastUpdateUser>mdmadmin</ContractLastUpdateUser>

                <CurrencyType>1</CurrencyType>

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

                <FrequencyModeType>1</FrequencyModeType>

                <FrequencyModeValue>Annual</FrequencyModeValue>

                <NextBillingDate>2001-09-11 23:59:59.0</NextBillingDate>

                <DWLStatus>

                    <Status>0</Status>

                </DWLStatus>

                <TCRMContractComponentBObj>

                    <ContractComponentIdPK>111111111</ContractComponentIdPK>

                    <ContractComponentLastUpdateDate>2013-05-16 12:18:21.268</ContractComponentLastUpdateDate>

                    <ContractComponentLastUpdateTxId>263336872110090101</ContractComponentLastUpdateTxId>

                    <ContractComponentLastUpdateUser>mdmadmin</ContractComponentLastUpdateUser>

                    <ContractId>111111111</ContractId>

                    <ContractStatusType>6</ContractStatusType>

                    <ContractStatusValue>Terminated</ContractStatusValue>

                    <ProductType>6</ProductType>

                    <ProductValue>Endowment</ProductValue>

                    <DWLStatus>

                        <Status>0</Status>

                    </DWLStatus>

                    <TCRMContractPartyRoleBObj>

                        <ContractComponentId>111111111</ContractComponentId>

                        <ContractPartyRoleLastUpdateDate>2013-05-16 12:18:21.348</ContractPartyRoleLastUpdateDate>

                        <ContractPartyRoleLastUpdateTxId>263336872110090101</ContractPartyRoleLastUpdateTxId>

                        <ContractPartyRoleLastUpdateUser>mdmadmin</ContractPartyRoleLastUpdateUser>

                        <ContractRoleIdPK>111111111</ContractRoleIdPK>

                        <DistributionPercentage>2.03</DistributionPercentage>

                        <IrrevokableIndicator>N</IrrevokableIndicator>

                        <PartyId>111111111</PartyId>

                        <RoleType>4</RoleType>

                        <RoleValue>Insured Primary</RoleValue>

                        <StartDate>2001-07-07 00:00:00.0</StartDate>

                        <DWLStatus>

                            <Status>0</Status>

                        </DWLStatus>

                        <TCRMPersonBObj>

                            <AddPartyStatus>1</AddPartyStatus>

                            <AlertIndicator>N</AlertIndicator>

                            <ClientImportanceType>2</ClientImportanceType>

                            <ClientImportanceValue>High</ClientImportanceValue>

                            <ClientPotentialType>1</ClientPotentialType>

                            <ClientPotentialValue>Client</ClientPotentialValue>

                            <ClientStatusType>1</ClientStatusType>

                            <ClientStatusValue>Active</ClientStatusValue>

                            <ComputerAccessType>1</ComputerAccessType>

                            <ComputerAccessValue>14.4K Baud</ComputerAccessValue>

                            <ConfidentialIndicator>N</ConfidentialIndicator>

                            <CreatedDate>2013-05-16 12:18:21.096</CreatedDate>

                            <DisplayName>Paint</DisplayName>

                            <MandatorySearchDone>Y</MandatorySearchDone>

                            <NewPartyIdReference>2244</NewPartyIdReference>

                            <PartyActiveIndicator>Y</PartyActiveIndicator>

                            <PartyId>111111111</PartyId>

                            <PartyLastUpdateDate>2013-05-16 12:18:21.138</PartyLastUpdateDate>

                            <PartyLastUpdateTxId>263336872110090101</PartyLastUpdateTxId>

                            <PartyLastUpdateUser>mdmadmin</PartyLastUpdateUser>

                            <PartyType>P</PartyType>

                            <PreferredLanguageType>100</PreferredLanguageType>

                            <PreferredLanguageValue>English</PreferredLanguageValue>

                            <SearchPartyDone>Y</SearchPartyDone>

                            <SolicitationIndicator>N</SolicitationIndicator>

                            <StatementFrequencyType>1</StatementFrequencyType>

                            <StatementFrequencyValue>Annually</StatementFrequencyValue>

                            <AgeVerifiedWithType>1</AgeVerifiedWithType>

                            <AgeVerifiedWithValue>Birth Certificate</AgeVerifiedWithValue>

                            <BirthDate>1973-09-01 00:00:00.0</BirthDate>

                            <GenderType>F</GenderType>

                            <HighestEducationType>3</HighestEducationType>

                            <HighestEducationValue>College Diploma</HighestEducationValue>

                            <NumberOfChildren>2</NumberOfChildren>

                            <PersonLastUpdateDate>2013-05-16 12:18:21.141</PersonLastUpdateDate>

                            <PersonLastUpdateTxId>263336872110090101</PersonLastUpdateTxId>

                            <PersonLastUpdateUser>mdmadmin</PersonLastUpdateUser>

                            <PersonPartyId>111111111</PersonPartyId>

                            <UserIndicator>N</UserIndicator>

                            <DWLStatus>

                                <Status>0</Status>

                            </DWLStatus>

                            <TCRMPartyAddressBObj>

                                <AddressGroupLastUpdateDate>2013-05-16 12:18:21.192</AddressGroupLastUpdateDate>

                                <AddressGroupLastUpdateTxId>263336872110090101</AddressGroupLastUpdateTxId>

                                <AddressGroupLastUpdateUser>mdmadmin</AddressGroupLastUpdateUser>

                                <AddressId>111111111</AddressId>

                                <AddressUsageType>1</AddressUsageType>

                                <AddressUsageValue>Primary Residence</AddressUsageValue>

                                <EffectEndMonthDay>0615</EffectEndMonthDay>

                                <EffectStartMonthDay>0720</EffectStartMonthDay>

                                <LocationGroupLastUpdateDate>2013-05-16 12:18:21.19</LocationGroupLastUpdateDate>

                                <LocationGroupLastUpdateTxId>263336872110090101</LocationGroupLastUpdateTxId>

                                <LocationGroupLastUpdateUser>mdmadmin</LocationGroupLastUpdateUser>

                                <PartyAddressIdPK>111111111</PartyAddressIdPK>

                                <PartyId>111111111</PartyId>

                                <StartDate>2001-06-11 00:00:00.0</StartDate>

                                <UndeliveredReasonType>1</UndeliveredReasonType>

                                <UndeliveredReasonValue>Moved</UndeliveredReasonValue>

                                <DWLStatus>

                                    <Status>0</Status>

                                </DWLStatus>

                                <TCRMAddressBObj>

                                    <AddressIdPK>111111111</AddressIdPK>

                                    <AddressLastUpdateDate>2013-05-16 12:18:21.174</AddressLastUpdateDate>

                                    <AddressLastUpdateTxId>263336872110090101</AddressLastUpdateTxId>

                                    <AddressLastUpdateUser>mdmadmin</AddressLastUpdateUser>

                                    <AddressLineOne>12 Pinto Rd</AddressLineOne>

                                    <City>Toronto</City>

                                    <CountryType>31</CountryType>

                                    <CountryValue>Canada</CountryValue>

                                    <CountyCode>1</CountyCode>

                                    <LatitudeDegrees>180</LatitudeDegrees>

                                    <LongitudeDegrees>90</LongitudeDegrees>

                                    <ProvinceStateType>108</ProvinceStateType>

                                    <ProvinceStateValue>ON</ProvinceStateValue>

                                    <ResidenceNumber>211</ResidenceNumber>

                                    <ResidenceType>1</ResidenceType>

                                    <ResidenceValue>Apartment</ResidenceValue>

                                    <StandardFormatingIndicator>Y</StandardFormatingIndicator>

                                    <StandardFormatingOverride>N</StandardFormatingOverride>

                                    <ZipPostalCode>ZZZYYY</ZipPostalCode>

                                    <DWLStatus>

                                        <Status>0</Status>

                                    </DWLStatus>

                                </TCRMAddressBObj>

                            </TCRMPartyAddressBObj>

                            <TCRMPartyIdentificationBObj>

                                <IdentificationIdPK>111111111</IdentificationIdPK>

                                <IdentificationNumber>291292293</IdentificationNumber>

                                <IdentificationStatusType>2</IdentificationStatusType>

                                <IdentificationStatusValue>Active</IdentificationStatusValue>

                                <IdentificationType>1</IdentificationType>

                                <IdentificationValue>Social Security Number</IdentificationValue>

                                <PartyId>111111111</PartyId>

                                <PartyIdentificationLastUpdateDate>2013-05-16 12:18:21.16</PartyIdentificationLastUpdateDate>

                                <PartyIdentificationLastUpdateTxId>263336872110090101</PartyIdentificationLastUpdateTxId>

                                <PartyIdentificationLastUpdateUser>mdmadmin</PartyIdentificationLastUpdateUser>

                                <StartDate>1969-06-09 00:00:00.0</StartDate>

                                <DWLStatus>

                                    <Status>0</Status>

                                </DWLStatus>

                            </TCRMPartyIdentificationBObj>

                            <TCRMPersonNameBObj>

                                <LastName>Paint</LastName>

                                <LastUpdatedBy>mdmadmin</LastUpdatedBy>

                                <LastUpdatedDate>2013-05-16 12:18:21.153</LastUpdatedDate>

                                <NameUsageType>1</NameUsageType>

                                <NameUsageValue>Legal</NameUsageValue>

                                <PersonNameIdPK>111111111</PersonNameIdPK>

                                <PersonNameLastUpdateDate>2013-05-16 12:18:21.153</PersonNameLastUpdateDate>

                                <PersonNameLastUpdateTxId>263336872110090101</PersonNameLastUpdateTxId>

                                <PersonNameLastUpdateUser>mdmadmin</PersonNameLastUpdateUser>

                                <PersonPartyId>111111111</PersonPartyId>

                                <StartDate>2013-05-16 12:18:21.153</StartDate>

                                <StdLastName>Paint</StdLastName>

                                <DWLStatus>

                                    <Status>0</Status>

                                </DWLStatus>

                            </TCRMPersonNameBObj>

                        </TCRMPersonBObj>

                    </TCRMContractPartyRoleBObj>

                </TCRMContractComponentBObj>

            </TCRMContractBObj>

        </ResponseObject>

    </TxResponse>

</TCRMService>

 

ResponseTCRMaddOrganization.xml

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

<TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="tCRMResponse.xsd">

    <ResponseControl>

        <ResultCode>SUCCESS</ResultCode>

        <ServiceTime>10594</ServiceTime>

        <DWLControl>

            <requesterLanguage>100</requesterLanguage>

            <requesterLocale>en</requesterLocale>

            <requesterName>mdmadmin</requesterName>

            <requestID>22456</requestID>

            <userRole>mdm_admin</userRole>

            <requesterTimeZone>EST5EDT</requesterTimeZone>

        </DWLControl>

    </ResponseControl>

    <TxResponse>

        <RequestType>addOrganization</RequestType>

        <TxResult>

            <ResultCode>SUCCESS</ResultCode>

        </TxResult>

        <ResponseObject>

            <TCRMOrganizationBObj>

                <AddPartyStatus>1</AddPartyStatus>

                <AlertIndicator>Y</AlertIndicator>

                <ClientImportanceType>4</ClientImportanceType>

                <ClientImportanceValue>Medium</ClientImportanceValue>

                <ClientPotentialType>2</ClientPotentialType>

                <ClientPotentialValue>Suspect</ClientPotentialValue>

                <ComputerAccessType>1</ComputerAccessType>

                <ComputerAccessValue>14.4K Baud</ComputerAccessValue>

                <ConfidentialIndicator>N</ConfidentialIndicator>

                <CreatedDate>2013-05-16 12:18:10.545</CreatedDate>

                <DisplayName>Active</DisplayName>

                <MandatorySearchDone>Y</MandatorySearchDone>

                <NewPartyIdReference>330499</NewPartyIdReference>

                <PartyActiveIndicator>Y</PartyActiveIndicator>

                <PartyId>311111111</PartyId>

                <PartyLastUpdateDate>2013-05-16 12:18:12.347</PartyLastUpdateDate>

                <PartyLastUpdateTxId>645836872108921801</PartyLastUpdateTxId>

                <PartyLastUpdateUser>mdmadmin</PartyLastUpdateUser>

                <PartyType>O</PartyType>

                <PreferredLanguageType>100</PreferredLanguageType>

                <PreferredLanguageValue>English</PreferredLanguageValue>

                <SearchPartyDone>Y</SearchPartyDone>

                <SolicitationIndicator>N</SolicitationIndicator>

                <BuySellAgreementType>2</BuySellAgreementType>

                <BuySellAgreementValue>Cross Purchase Agreement</BuySellAgreementValue>

                <EstablishedDate>1977-01-01 00:00:00.0</EstablishedDate>

                <IndustryType>9</IndustryType>

                <IndustryValue>Trade</IndustryValue>

                <OrganizationLastUpdateDate>2013-05-16 12:18:12.397</OrganizationLastUpdateDate>

                <OrganizationLastUpdateTxId>645836872108921801</OrganizationLastUpdateTxId>

                <OrganizationLastUpdateUser>mdmadmin</OrganizationLastUpdateUser>

                <OrganizationPartyId>311111111</OrganizationPartyId>

                <OrganizationType>1</OrganizationType>

                <OrganizationValue>Corporation</OrganizationValue>

                <ProfitIndicator>Y</ProfitIndicator>

                <DWLStatus>

                    <Status>0</Status>

                </DWLStatus>

                <TCRMPartyAddressBObj>

                    <AddressGroupLastUpdateDate>2013-05-16 12:18:14.804</AddressGroupLastUpdateDate>

                    <AddressGroupLastUpdateTxId>645836872108921801</AddressGroupLastUpdateTxId>

                    <AddressGroupLastUpdateUser>mdmadmin</AddressGroupLastUpdateUser>

                    <AddressId>311111111</AddressId>

                    <AddressUsageType>1</AddressUsageType>

                    <AddressUsageValue>Primary Residence</AddressUsageValue>

                    <LocationGroupLastUpdateDate>2013-05-16 12:18:14.777</LocationGroupLastUpdateDate>

                    <LocationGroupLastUpdateTxId>645836872108921801</LocationGroupLastUpdateTxId>

                    <LocationGroupLastUpdateUser>mdmadmin</LocationGroupLastUpdateUser>

                    <PartyAddressIdPK>311111111</PartyAddressIdPK>

                    <PartyId>311111111</PartyId>

                    <StartDate>2001-06-11 00:00:00.0</StartDate>

                    <DWLStatus>

                        <Status>0</Status>

                    </DWLStatus>

                    <TCRMAddressBObj>

                        <AddressIdPK>311111111</AddressIdPK>

                        <AddressLastUpdateDate>2013-05-16 12:18:14.702</AddressLastUpdateDate>

                        <AddressLastUpdateTxId>645836872108921801</AddressLastUpdateTxId>

                        <AddressLastUpdateUser>mdmadmin</AddressLastUpdateUser>

                        <AddressLineOne>115 Milan St.</AddressLineOne>

                        <City>Paris</City>

                        <CountryType>31</CountryType>

                        <CountryValue>Canada</CountryValue>

                        <LatitudeDegrees>180</LatitudeDegrees>

                        <LongitudeDegrees>90</LongitudeDegrees>

                        <ProvinceStateType>101</ProvinceStateType>

                        <ProvinceStateValue>AB</ProvinceStateValue>

                        <ResidenceType>2</ResidenceType>

                        <ResidenceValue>Detached House</ResidenceValue>

                        <StandardFormatingIndicator>N</StandardFormatingIndicator>

                        <StandardFormatingOverride>N</StandardFormatingOverride>

                        <ZipPostalCode>M5A 1P4</ZipPostalCode>

                        <DWLStatus>

                            <Status>0</Status>

                        </DWLStatus>

                    </TCRMAddressBObj>

                </TCRMPartyAddressBObj>

                <TCRMPartyIdentificationBObj>

                    <IdentificationIdPK>311111111</IdentificationIdPK>

                    <IdentificationNumber>919293</IdentificationNumber>

                    <IdentificationStatusType>2</IdentificationStatusType>

                    <IdentificationStatusValue>Active</IdentificationStatusValue>

                    <IdentificationType>2</IdentificationType>

                    <IdentificationValue>Corporate Tax Identification</IdentificationValue>

                    <PartyId>311111111</PartyId>

                    <PartyIdentificationLastUpdateDate>2013-05-16 12:18:14.627</PartyIdentificationLastUpdateDate>

                    <PartyIdentificationLastUpdateTxId>645836872108921801</PartyIdentificationLastUpdateTxId>

                    <PartyIdentificationLastUpdateUser>mdmadmin</PartyIdentificationLastUpdateUser>

                    <StartDate>2002-02-02 00:00:00.0</StartDate>

                    <DWLStatus>

                        <Status>0</Status>

                    </DWLStatus>

                </TCRMPartyIdentificationBObj>

                <TCRMOrganizationNameBObj>

                    <NameUsageType>1</NameUsageType>

                    <NameUsageValue>Legal</NameUsageValue>

                    <OrganizationName>Active</OrganizationName>

                    <OrganizationNameIdPK>311111111</OrganizationNameIdPK>

                    <OrganizationNameLastUpdateDate>2013-05-16 12:18:14.497</OrganizationNameLastUpdateDate>

                    <OrganizationNameLastUpdateTxId>645836872108921801</OrganizationNameLastUpdateTxId>

                    <OrganizationNameLastUpdateUser>mdmadmin</OrganizationNameLastUpdateUser>

                    <OrganizationPartyId>311111111</OrganizationPartyId>

                    <SOrganizationName>ACTIVE</SOrganizationName>

                    <StartDate>2001-08-11 00:00:00.0</StartDate>

                    <DWLStatus>

                        <Status>0</Status>

                    </DWLStatus>

                </TCRMOrganizationNameBObj>

            </TCRMOrganizationBObj>

        </ResponseObject>

    </TxResponse>

</TCRMService>

 

ResponseTCRMaddPerson.xml

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

<TCRMService xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="tCRMResponse.xsd">

    <ResponseControl>

        <ResultCode>SUCCESS</ResultCode>

        <ServiceTime>391</ServiceTime>

        <DWLControl>

            <requesterLanguage>100</requesterLanguage>

            <requesterLocale>en</requesterLocale>

            <requesterName>mdmadmin</requesterName>

            <requestID>92345</requestID>

            <userRole>mdm_admin</userRole>

            <requesterTimeZone>EST5EDT</requesterTimeZone>

        </DWLControl>

    </ResponseControl>

    <TxResponse>

        <RequestType>addPerson</RequestType>

        <TxResult>

            <ResultCode>SUCCESS</ResultCode>

        </TxResult>

        <ResponseObject>

            <TCRMPersonBObj>

                <AddPartyStatus>1</AddPartyStatus>

                <AlertIndicator>N</AlertIndicator>

                <ClientImportanceType>4</ClientImportanceType>

                <ClientImportanceValue>Medium</ClientImportanceValue>

                <ClientPotentialType>1</ClientPotentialType>

                <ClientPotentialValue>Client</ClientPotentialValue>

                <ClientStatusType>1</ClientStatusType>

                <ClientStatusValue>Active</ClientStatusValue>

                <ComputerAccessType>1</ComputerAccessType>

                <ComputerAccessValue>14.4K Baud</ComputerAccessValue>

                <ConfidentialIndicator>N</ConfidentialIndicator>

                <CreatedDate>2013-05-16 12:18:19.676</CreatedDate>

                <DisplayName>Vanessa Dana</DisplayName>

                <MandatorySearchDone>Y</MandatorySearchDone>

                <PartyActiveIndicator>Y</PartyActiveIndicator>

                <PartyId>911111111</PartyId>

                <PartyLastUpdateDate>2013-05-16 12:18:19.82</PartyLastUpdateDate>

                <PartyLastUpdateTxId>588236872109967301</PartyLastUpdateTxId>

                <PartyLastUpdateUser>mdmadmin</PartyLastUpdateUser>

                <PartyType>P</PartyType>

                <PreferredLanguageType>100</PreferredLanguageType>

                <PreferredLanguageValue>English</PreferredLanguageValue>

                <SearchPartyDone>Y</SearchPartyDone>

                <SolicitationIndicator>N</SolicitationIndicator>

                <StatementFrequencyType>1</StatementFrequencyType>

                <StatementFrequencyValue>Annually</StatementFrequencyValue>

                <AgeVerifiedWithType>2</AgeVerifiedWithType>

                <AgeVerifiedWithValue>Passport</AgeVerifiedWithValue>

                <BirthDate>1942-07-01 00:00:00.0</BirthDate>

                <BirthPlaceType>1</BirthPlaceType>

                <BirthPlaceValue>Afghanistan</BirthPlaceValue>

                <CitizenshipType>1</CitizenshipType>

                <CitizenshipValue>Afghanistan</CitizenshipValue>

                <GenderType>F</GenderType>

                <HighestEducationType>4</HighestEducationType>

                <HighestEducationValue>University Degree</HighestEducationValue>

                <MaritalStatusType>2</MaritalStatusType>

                <MaritalStatusValue>Single</MaritalStatusValue>

                <NumberOfChildren>2</NumberOfChildren>

                <PersonLastUpdateDate>2013-05-16 12:18:19.835</PersonLastUpdateDate>

                <PersonLastUpdateTxId>588236872109967301</PersonLastUpdateTxId>

                <PersonLastUpdateUser>mdmadmin</PersonLastUpdateUser>

                <PersonPartyId>911111111</PersonPartyId>

                <UserIndicator>N</UserIndicator>

                <DWLStatus>

                    <Status>0</Status>

                </DWLStatus>

                <TCRMPersonNameBObj>

                    <GivenNameOne>Vanessa</GivenNameOne>

                    <LastName>Dana</LastName>

                    <LastUpdatedBy>mdmadmin</LastUpdatedBy>

                    <LastUpdatedDate>2013-05-16 12:18:19.913</LastUpdatedDate>

                    <NameUsageType>1</NameUsageType>

                    <NameUsageValue>Legal</NameUsageValue>

                    <PersonNameIdPK>911111111</PersonNameIdPK>

                    <PersonNameLastUpdateDate>2013-05-16 12:18:19.913</PersonNameLastUpdateDate>

                    <PersonNameLastUpdateTxId>588236872109967301</PersonNameLastUpdateTxId>

                    <PersonNameLastUpdateUser>mdmadmin</PersonNameLastUpdateUser>

                    <PersonPartyId>911111111</PersonPartyId>

                    <StartDate>2008-01-12 00:00:00.0</StartDate>

                    <StdGivenNameOne>Vanessa</StdGivenNameOne>

                    <StdLastName>Dana</StdLastName>

                    <DWLStatus>

                        <Status>0</Status>

                    </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>

 

 

Installing InfoSphere MDM 11.0 with external LDAP

If using external LDAP, create MDM users and groups in external LDAP before installing MDM following this page in a MDM Info Center - http://pic.dhe.ibm.com/infocenter/mdm/v11r0/topic/com.ibm.swg.im.mdmhs.release.install.doc/Topics/adding_user_to_mdmgroup.html?resultof=%22%6d%64%6d%5f%61%64%6d%69%6e%22%20

 

Installing InfoSphere MDM 11.0 with WebSphere MQ

If installing MDM11.0 using WebSphere MQ messaging provide and if WebSphere MQ is on separate box then where Installer runs, configure WebSphere MQ following this page in a MDM Info Center - http://pic.dhe.ibm.com/infocenter/mdm/v11r0/topic/com.ibm.swg.im.mdmhs.release.install.doc/Topics/t_to_manually_install_the_mdm_server_msging_component.html?resultof=%22%6d%71%73%63%22%20 before running Installer.

 

Managing security users and groups when installing InfoSphere MDM 11.0

The mdmadmin user is an internal user that, by default, acts in two different roles. Optionally, these two roles can be split amongst two different users.

  • For development and QA environments, we recommend using the combined, default mdmadmin user.
  • For preproduction and production environments, we recommend that the WebSphere Application Server Administration Security user and the WebSphere Application Server Application Security Role Mapping user should be different users. These two users should use names that are different than mdmadmin.

 Using a different user name than mdmadmin in InfoSphere MDM V11.0

 The first role is a WebSphere Application Server administration security user. This security user can also be used as a demo user to log in to the InfoSphere MDM user interface applications, but there is no requirement to use it as a login ID for any end users. The WebSphere Application Server administration security user has to be created when enabling WebSphere Application Server administration security. It can be stored in a WebSphere Application Server local file based registry (WebSphere Application Server Internal LDAP) or in external LDAP. When deploying and then running InfoSphere MDM V11.0, the mdmadmin user name for WebSphere Application Server administration security is considered to be a default name. If nessesary, the WebSphere Application Server administration security name being used with InfoSphere MDM V11.0 can be different than mdmadmin. You can specify the different user name as a user input when installing InfoSphere MDM V11.0.

The second role is a WebSphere Application Server Application Security Role Mapping user. This user is used to secure OSGi and web services. By default, this second role is also assigned to the user named mdmadmin. This second role can also be assigned to a different user, as will be explained later in this section.

The InfoSphere MDM installation application collects the WebSphere Application Server administration security user from a user input field. Then, after connecting to WebSphere Application Server using the supplied credentials, the installation application deploys a number of InfoSphere MDM operational server and user interface application deployment modules. Next, the installation application enables WebSphere Application Server Application Security to secure the InfoSphere MDM EBA and web services. While enabling WebSphere Application Server Application Security, the "second role" mdmadmin user is being used as the Role Mapping user for enabling WebSphere Application Server Application Security.

Changing the WebSphere Application Server administration security user

To have set the WebSphere Application Server administration security user to be different than mdmadmin, you must first use new user name (different than mdmadmin) when enabling WebSphere Application Server Administration Security. Next, you must specify this new name during user input in the following installation application panels (assuming that you are running the installation in GUI mode):

For the InfoSphere MDM operational server:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

For the InfoSphere MDM user interface applications (one panel per application):

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  

To set a WebSphere Application Server Application Security Role Mapping user that is different than mdmadmin (and even different than the WebSphere Application Server Administration Security):

Create a new user in the WebSphere Application Server Federated registry (WebSphere Application Server internal LDAP) of an external LDAP if WAS security is configured using external LDAP.

Specify the new user name as part of the installation user input in the InfoSphere MDM silent install input property file.

Copy the silent install input property file from the Startup Kit and configure it to provide a new user name for the WebSphere Application Server Application Security Role Mapping user:

Modify the values for the following variables to specify user name different then mdmadmin. Also provide a password.

<data key='user.L2.was.admin.user,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.L2.was.admin.password,com.ibm.mdm.advanced' value='mdmadmin'/>

4. Run IBM Installation Manager using the following command so that the installation application will use the WebSphere Application Server Application Security Role Mapping user name and password from the silent install input property file:

./IBMIM -input <mdmsilent.res>

where <mdmsilent.res> is the name of the silent install input property file.

When running the InfoSphere MDM V11.0 installation application in GUI mode with no default WebSphere Application Server Application Security Role Mapping user from an input file,

the following panel will show password input text field for the WebSphere Application Server Application Security Role Mapping user. The value of the password will be fulfilled in a password text field taken from the silent install input property file. You can continue with this value or modify it.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 If you are installing InfoSphere MDM V11.0 in silent mode, use the same variables for the WebSphere Application Server Application Security Role Mapping user name and password:

<data key='user.L2.was.admin.user,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.L2.was.admin.password,com.ibm.mdm.advanced' value='mdmadmin'/>

For the WebSphere Application Server administration security user, use the following values:

<data key='user.was.user,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.password,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.security.user.name,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.security.user.password,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.user.ba,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.password.ba,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.user.ds,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.password.ds,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.user.pui,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.password.pui,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.user.inspector,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.password.inspector,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.user.ev,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.password.ev,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.user.wb,com.ibm.mdm.advanced' value='mdmadmin'/>

<data key='user.was.password.wb,com.ibm.mdm.advanced' value='mdmadmin'/>

 

For more information about the silent input property file see the InfoSphere MDM 11.0 documentation:

http://pic.dhe.ibm.com/infocenter/mdm/v11r0/topic/com.ibm.swg.im.mdmhs.release.install.doc/Topics/sample_responsefile.html

http://pic.dhe.ibm.com/infocenter/mdm/v11r0/topic/com.ibm.swg.im.mdmhs.release.install.doc/Topics/customizingthesilentmoderesponsefile.ht