Adding Certificates to trustore

1)Open ikeyman utility : C:\Program Files\IBM\IIB\10.0.0.9\common\jdk\jre\bin

2)Clink Open, then Browse:

3)Navigate to Truststore, then Open: (trustore.jks)

4)click OK

5) Enter pwd then click Ok

6)Select signer certificate from dropdown.

7) Lcisk Add then browse

8) Select Cert to add then click open.

9) Click Ok.

10) Enter a label then OK

11) done, new cert has been added.

Reference: https://www.ibm.com/support/knowledgecenter/en/SSKM8N_8.0.0/com.ibm.etools.mft.doc/ap34020_.htm

Adding an SMTP client policy

Adding an SMTP client policy

How to add an SMTP client policy to a user agent.

About this task

Availability: Appliances with the B2B feature.

The user agent controls the client settings for outgoing SMTP connections for requests that match the URL expression. These client settings can be overridden by query parameters in the URL that initiates the mail transfer.

Procedure

1. In the search field, enter User Agent.
2. From the search results, click User Agent.
3. Click the name of a user agent configuration.
4. Click the SMTP Client Policies tab.
5. Add a policy.
   1. Click Add.
   2. In the URL Matching Expression field, enter a shell-style expression to be the matching pattern for the URL set.
   3. In the Recipient email field, enter the default email address to which to send email messages.
   4. In the Sender email field, enter the default email address that identifies the sender.
   5. In the Subject field, enter the default subject for email messages.
   6. From the Options list, click the check boxes for the SMTP options to enable.
   7. To use the Simple Authentication and Security Layer (SASL) client authentication: From the Client Authentication list, select the authentication method.
   8. Click Apply.
6. Optional: Repeat the previous step to add another policy.
7. Click Apply to save the changes to the running configuration.
8. Optional: Click Save Configuration to save the changes to the persisted configuration.

What's Clustering and how to create it

What is clustering?

Clustering is a way to logically group WebSphere MQ queue managers so that you have: – reduced system administration due to fewer channel, remote queue, and transmission queue definitions. – increased availability and workload balancing due to the ability to define instances of the same queue on multiple queue managers in the cluster and distribute messages to those queues.

How do you create a cluster?
go to servers -> clusters-> new ->give cluster_name->define first member->define other members->finish

How do you add a new cluster member?
go to servers -> clusters->cluster_name ->cluster members ->new ->give name/node/others->apply->ok->save

one of the cluster member (jvm) is having issues. To troubleshoot the issue, you decided to take it out of the cluster. How do you do that?
Make its runtime weight to 0

In a complex environment, there are 10 machines. Machine A is having 8GB RAM and machine B having 2GB of RAM. The administrator decided to send twice as many request as machineB to machineA. How can he achive it?
give machineA twice the weight as machineB

After making some changes on a cluster, it is required to recycle/restart all the cluster JVMs. The lead admin told you to make sure that there should not be any downtime during this recycle. Which option do you use to achieve it?
Ripplestart

A large application which has 5web modules has been deployed on to a cluster. After some months, the developer asked you to update on of the 5web modules. How do you do it?
Rollout

What is a backup cluster?

can you change the cluster name, once it was created
No

WSRR

Setup for WSRR Connectivity

Most services will need WSRR connectivity from IIB:

1)     Execute this mqsichangeproperties command to assign the

WSRR endpointAddress:

Mqsichangeproperties IIBNODE -c ServiceRegistries -o DefaultWSRR -n endpointAddress -v https://xyzs.com:9444/WSRR8_0/services/WSRRCoreSDOPort

2)     Execute this mqsichangeproperties command to assign the WSRR username and password:

mqsisetdbparms IIBNODE -n DefaultWSRR::WSRR -u User -p pwd

3)     Execute this mqsireportproperties command to view your WSRR registry parameters:

mqsireportproperties IIBNODE -c ServiceRegistries -o DefaultWSRR –r

4)     Ececute this mqsicreateconfigurableservice command to create a TRCommon UserDefined Configurable Service Property to store the WSRR URL in DEV:

mqsicreateconfigurableservice IIBNODE -c UserDefined -o TRCommon -n "WSRR_URL" -v https://xyz.com:9444/WSRR/8.5/Metadata/XML/Query/EndpointLookup

DB2 Client Installation on Linux SUSE Linux Enterprise Server & DSN Setup

DB2 Client Installation on Linux SUSE Linux Enterprise Server & DSN Setup

1.     Download the DB2 client v10.1fp5_linuxx64_client.tar.gz from below link.

http://www-933.ibm.com/support/fixcentral/swg/selectFix?source=dbluesearch&product=ibm%2FInformation+Management%2FIBM+Data+Server+Client+Packages&release=10.1.*&platform=Linux+64-bit,x86_64&searchtype=fix&fixids=*-client-*FP005&function=fixId&parent=ibm/Information%20Management

i.                 Use your IBM ID & password to get the DB2 server client software.

2.     Pre-requisite before installation of DB2 client into Linux 64 Bit Suse Linux Enterprise server 10.3.

i.                 Check the operating system compatibility.

http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1319124752192&osPlatform=Linux

ii.                For DB2 client installation, /opt/ibm & /tmp filesystem should be 1 to 2 GB free.

iii.               Verify the Library files.

http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/r0008865.html?cp=SSEPGG_10.5.0%2F2-0-1-2-2-4

iv.               Verify the Kernel parameters. If needed then change the kernel parameters in /etc/sysctl.conf file.

http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/t0008238.html?cp=SSEPGG_10.5.0%2F2-0-1-2-2-0-10-3

http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/c0057140.html?cp=SSEPGG_10.5.0%2F2-0-1-2-2-0-10-1

v.                Below are the kernel parameters which are already fulfilled for DB2 client installation.

3.     Copy the v10.1fp5_linuxx64_client.tar.gz file, wherever you have free disk space.

I have copied into /MQHA/BDBKRD01/wmb path.

Execute the below command for gunzip & then extract the tar file which will create client folder as shown below.

/usr/bin/gunzip v10.1fp5_linuxx64_client.tar.gz

tar –xvf v10.1fp5_linuxx64_client.tar

Go to client folder.

4.     You can check the DB2 client pre-requisite by using following command.

./db2prereqcheck -c -v 10.1.0.5

5.     There are 4 types of DB2 client installation but we have used the response file installation method for DB2 client.

http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.qb.server.doc/doc/c0008711.html?lang=en

i.                 You can take the copy of sample response file (/MQHA/BDBKRD01/wmb/client/db2/linuxamd64/samples/db2client.rsp) & keep it in another folder (/MQHA/BDBKRD01/wmb/client/db2client.rsp) as well as update it with accept the license.

ii.                Installation of DB2 client with Response file installation method by using root ID. Execute the below command

db2setup -r /MQHA/BDBKRD01/wmb/client/db2client.rsp -l /MQHA/BDBKRD01/wmb/client/db2setup_eimb.log -t /MQHA/BDBKRD01/wmb/client/db2setup_eimb.trc

You can verify the logs & trace files of DB2 client installation.

 

                              NOTE:- DB2 client & drivers will be installed in /opt/ibm/db2/V10.1 path.

iii.               Once you installed DB2 client by using root ID, then db2inst1 User ID & db2iadm1 group ID will get create by default.

iv.               You can work with unix team & set the password for db2inst1 user ID. For example password of db2inst1 User ID is Start123

6.     DB2 Validation.

i.                 Login to server with db2inst1 user ID & execute the below commands.

db2level :- verify the DB2 client installation version.

              

               db2val :- db2 validation.

7.     Installed the DB2 Client licenses.

You need to contact to IBM DB2 team to buy the license. We have purchased below one.

IBM DB2 Connect 10.1 Unlimited Edition for System i Quick Start and Activation Multiplatform Multilingual        CI6N8ML         db2consv_is.lic

i.                 db2licm is the command which we used to add the license.

eimb@j700s013:/MQHA/BDBKRD01/wmb/client/db2/license> db2licm -a db2consv_is.lic

LIC1402I  License added successfully.

LIC1426I  This product is now licensed for use as outlined in your License Agreement.  USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE AGREEMENT, LOCATED IN THE FOLLOWING DIRECTORY: "/opt/ibm/db2/V10.1/license/en_US.iso88591"

ii.                Get the db2 licenses details.

eimb@j700s013:/MQHA/BDBKRD01/wmb/client/db2> db2licm -l

Product name:                     "DB2 Connect Unlimited Edition for iSeries"

License type:                     "Client Device"

Expiry date:                      "Permanent"

Product identifier:               "db2consv"

Version information:              "10.1"

iii.               Add the db2jcc_license_cisuz.jar file in /home/db2inst1/sqllib/java path.

iv.               Export /home/db2inst1/sqllib/java/db2jcc_license_cisuz.jar path in CLASSPATH variable.

v.                Export /opt/ibm/IE02 path in IE02_PATH variable.

8.     DB2 commands, Driver configuration & connection setup

i.                 Configure the db2 driver. Go to /opt/ibm/db2/V10.1/cfg path & update the db2dsdriver.cfg file with below details.

vi.               Create the connection with DB2 Database by using following commands.

eimb@j700s013:/opt/ibm/db2/V10.1/bin> db2 catalog tcpip node NANTESD remote DEV.CG.EU.JCI.COM server 446

eimb@j700s013:/opt/ibm/db2/V10.1/bin> db2 catalog database S4427047 at node NANTESD

eimb@j700s013:/opt/ibm/db2/V10.1/bin> db2 connect to S4427047 user UNITYUSR using UnItY15

db2 list database directory

9.     WMB DSN Setup.

i.                 Work with unix team & asked them to add eimb user ID in db2iadm1 group ID as well as add dbinst1 user ID in mqbrkrs group ID.

ii.                Login to sever with your global ID & then sudo with eimb user ID. Add the below command in eimb profile file (/home/eimb/.profile).

# DB2 Profile

. /home/db2inst1/sqllib/db2profile

iii.               Once above both the things completed successfully then you can execute the DB2 commands by eimb user ID.

iv.               Go to /var/mqsi/odbc path & update .odbc.ini file with below details & execute the commands as shown below.