Quotes

Thursday, February 16, 2017

IBM Integration Bus Tech Reference

Webcast replay: WebSphere Message Broker - Security Administration


Webcast replay: Integrating WebSphere Message Broker V7 with SAP



Webcast: Migrating to IBM Integration Bus V10



Index: IBM Integration Bus and WebSphere Message Broker trace directions



Webcast replay: Debugging top 5 memory problems in IBM Integration Bus (IIB)



Open Mic Replay: Security in WebSphere Message Broker



Webcast replay: Implementing SSL with HTTP nodes in WebSphere Message Broker



Webcast replay: WebSphere Message Broker - Security in SOAP nodes



Webcast Replay: IBM Integration Bus - What's new



Webcast replay: Common Problems While Configuring SSL in v8 Message Broker



Webcast replay: How do you use .Net with the Broker



Webcast replay: Using TCP/IP Based Applications with WebSphere Message Broker



Webcast replay: Events-Based Messaging Monitoring in WebSphere Message Broker V7



Webcast replay: Using WebSphere Message Broker Configurable Services



Webcast replay: Packaging and Deploying Java Based Solutions to WebSphere Message Broker


Webcast Replay: Tools and techniques for performance testing IBM Integration Bus (IIB) solutions


This procedure is typically run to track down problems in IBM Integration Bus (IIB) or Websphere Message Broker (WMB) with database connectivity such as user access and dropped database connections. Gathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.


The following is a list of answers to frequently asked questions (FAQ) about Migration in IBM Integration Bus (IIB) and WebSphere Message Broker (WMB) for new and experienced users.


The following is a list of answers to frequently asked questions (FAQ) about Database in IBM Integration Bus (IIB) and WebSphere Message Broker (WMB) for new and experienced users.


Performance is degraded when IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) calls stored procedures.


Use this procedure to capture a user or service level trace of an IBM Integration Bus (IIB) message flow at an Integration Server level or a WebSphere Message Broker (WMB) message flow at an execution group level. 

Gathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.


This Index is a compilation of links to documents that provide instructions for gathering various trace data on IBM Integration Bus (IIB) and WebSphere Message Broker (WMB) and related products.
Content
Trace can gather additional details required for problem solving. Follow the directions provided in these documents to gather trace details.


Use this procedure to capture a service level trace of the "Admin agent" (bipbroker process) in Websphere Message Broker or IBM Integration Bus. 

Gathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.


Use the procedures below to take a startup trace of a broker or execution group in WebSphere Message Broker (WMB). 

IBM Integration Bus (IIB) V9 replaces Execution Group with Integration Server. Similar instructions are provided below for collecting Integration Server startup trace. 

Gathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.


Use this procedure to capture a IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) trace of a failing deploy to a broker. 

Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Integration Server or Execution Group memory growing
Your IBM Integration Bus (IIB) Integration Servers or WebSphere Message Broker (WMB) Execution Groups appear to be growing in memory indefinitely.

Increasing the maximum JVM heap size of the WebSphere Message Broker HTTP listener

The broker-wide listener process (biphttplistener) handles both inbound requests and outbound replies for the HTTPInput and HTTPReply nodes across an entire broker. By default, this listener is started with a maximum JVM heap size of 192MB. 

It is possible, based on inbound request rates and message sizes, that the default maximum size is not sufficient.



Configuring and administering multi-instance brokers for high availability in IBM WebSphere Message Broker - Part 1
This article describes multi-instance brokers, a feature introduced in WebSphere Message Broker V7 that helps you configure high-availability environments. The feature is based on multi-instance queue managers in WebSphere MQ V7.0.1, which provide multiple instances of a queue manager residing on separate physical servers to provide a highly available configuration. In WebSphere MQ, the multi-instance queue manager's configuration is hosted on shared network storage, so that if the active queue manager fails, another instance automatically assumes the stopped queue manager's configuration and becomes active. Similarly, in Message Broker V7 and V8, a broker's configuration is hosted on network storage to enable the high-availability function.

Configuring and administering multi-instance brokers for high availability in IBM WebSphere Message Broker - Part 2
This article describes the active-active technique for high availability using both vertical and horizontal clustering, which compared to the active-passive technique, improves continuous availability, performance, throughput, and scalability in WebSphere MQ and WebSphere Message Broker.

IBM Datapower Developerworks Articles


IBM Datapower DeveloperWorks Articles
4.    Integrating the WebSphere DataPower SOA Appliance XI50 with the WebSphere Application Server V7 default JMS messaging provider
6.    Using OAuth on IBM WebSphere DataPower Appliances
7.     SOA governance using WebSphere DataPower and WebSphere Service Registry and Repository
8.    Leverage DataPower SOA Appliances to extend InfoSphere Master Data Management Server security capabilities
9.    Using WebSphere DataPower and WebSphere MQ File Transfer Edition to manage file transfers
10.  Configuring a WebSphere DataPower Kerberos-secured backend server
11.   Overriding the WebSphere DataPower WSDL optimization conversion
13.  Using the WebSphere DataPower Option for Application Optimization to demonstrate self-balancing across multiple DataPower appliances and intelligent load distribution to backend servers
14.  Integrating WebSphere DataPower SOA Appliances with WebSphere MQ
15.  Performance advantages of using WebSphere DataPower XC10 Appliance as a side cache for a Java application
16.  Integrating DataPower with WebSphere Message Broker using the Broker Explorer
17.  Integrating WebSphere DataPower XML Security Gateway XS40 with WebSphere Message Broker
20. Integrating Web applications with the DataPower Web application firewall service
21.  Managing WebSphere DataPower SOA Appliance configurations for high availability, consistency, and control, Part 1
22. Managing WebSphere DataPower Device configurations for high availability, consistency, and control, Part 2: Application promotion strategies
24. Using DataPower SOA Appliances to query WebSphere Service Registry and Repository

WMB Continuous Integration Using ANT and Jenkins

http://godfreym.blogspot.com/2015/11/continuous-deployment-for-ibm.html

Configuring DSN for IBM Integration Bus in Fedora for Oracle


Configuring DSN for IBM Integration Bus in Fedora for Oracle

I had a very troubling time setting up a DSN for IIB in Fedora. To make sure that others don't have to waste a precious weekend and long time on this rather menial subject I thought I would document it for all.

Assumption :- The software is installed at the location - /opt/ibm/mqsi/9.0.0.0

Here are the steps -

  • A sample odbc.ini and odbcinst.ini file are in the 'install_dir/ODBC/unixodbc/' in my case it is /opt/ibm/mqsi/9.0.0.0/ODBC/unixodbc. Copy the files to /var/mqsi/odbc directory. 
           cp /opt/ibm/mqsi/9.0.0.0/ODBC/unixodbc/odbc.ini /var/mqsi/odbc/odbc.ini
           cp /opt/ibm/mqsi/9.0.0.0/ODBC/unixodbc/odbcinst.ini /var/mqsi/odbc/odbcinst.ini

  • Change the owner of the files to mqm:mbrkrs using the following command

           chown mqm:mqbrkrs /var/mqs/odbc/odbc.ini
           chown mqm:mqbrkrs /var/mqs/odbc/odbcinst.ini

  • Open the '/var/mqsi/odbc/odbc.ini' file. Copy the following lines and paste them just above the copied part- 
           ;# Oracle stanza
           [ORACLEDB]
           Driver=<Your Broker install directory>/ODBC/V7.0/lib/UKora26.so
           Description=DataDirect 7.0 ODBC Oracle Wire Protocol
           HostName=<Your Oracle Server Machine Name>
           PortNumber=<Port on which Oracle is listening on HostName>
           ServiceName=<Your Oracle Service Name>
           CatalogOptions=0
           EnableStaticCursorsForLongData=0
           ApplicationUsingThreads=1
           EnableDescribeParam=1
           OptimizePrepare=1
           WorkArounds=536870912
           ProcedureRetResults=1
           ColumnSizeAsCharacter=1
           LoginTimeout=0


           Make the changes as follows for your DSN. In my case I create a DSN as XE for my XE database. The                driver path may be different as per your installation.

           [XE]
           Driver=/opt/ibm/mqsi/9.0.0.0/ODBC/V7.0/lib/UKora26.so
           HostName=localhost
           PortNumber=1521
           ServiceName=XE

           Not to forget, at the end of the file mention the install directory.


           [ODBC]
           InstallDir=/opt/ibm/mqsi/9.0.0.0/ODBC/V7.0
           UseCursorLib=0           IANAAppCodePage=4
           UNICODE=UTF-8

           Save the file.
  • Download the IE02 support pac from the following location - http://www-01.ibm.com/support/docview.wss?uid=swg24026935 . In my case I used the 64 bit version 2.0.1 and the file name is 'ie02_amd64_linux_2.tar'. Extract the archive file and it create a folder-in my case 'amd64_linux_2'- that will contain 'install-ie02.bin' file. Run the .bin file and install it. I had it installed in the location '/opt/ibm/IE02'
  • Now that we have all the files in place we need to setup some environment variables in the .profile file of the user that would control the broker runtime. I have the following variables added to end of my .bash_profile 

           export ODBCINI=/var/mqsi/odbc/odbc.ini
           export ODBCSYSINI=/var/mqsi/odbc/
           export IE02_PATH=/opt/ibm/IE02/2.0.1/


    • Use the mqsisetdbparms command to associate the user id and password to the ODBC. The following example command will prompt you for the password and then set the user id and password -
               mqsisetdbparms WBRK9 -n XE -u system
    • Restart the broker to allow it to absorb the setting and then issue the command to check if the broker runtime can access the DSN. 
              mqsicvp -n XE -u system -p yourpassword

    If the command runs with success you should see the output of the command as follows - 

               BIP8290I: Verification passed for the ODBC environment. 

    BIP8270I: Connected to Datasource 'XE' as user 'SYSTEM'. The datasource platform is 'Oracle', version '11.02.0000 Oracle 11.2.0.2.0'. 
    ===========================
    databaseProviderVersion      = 11.02.0000 Oracle 11.2.0.2.0
    driverVersion                = 07.01.0097 (B0099, U0067)
    driverOdbcVersion            = 03.52
    driverManagerVersion         = 03.52.0002.0002
    driverManagerOdbcVersion     = 03.52
    databaseProviderName         = Oracle
    datasourceServerName         = localhost
    databaseName                 = N/A
    odbcDatasourceName           = XE
    driverName                   = UKora26.so
    supportsStoredProcedures     = Yes
    procedureTerm                = PL/SQL
    accessibleTables             = Yes
    accessibleProcedures         = Yes
    identifierQuote              = "
    specialCharacters            = None
    describeParameter            = Yes
    schemaTerm                   = User Name
    tableTerm                    = Table
    sqlSubqueries                = 31
    activeEnvironments           = 0
    maxDriverConnections         = 0
    maxCatalogNameLength         = 128
    maxColumnNameLength          = 30
    maxSchemaNameLength          = 30
    maxStatementLength           = 0
    maxTableNameLength           = 30
    supportsDecimalType          = Yes
    supportsDateType             = No
    supportsTimeType             = No
    supportsTimeStampType        = No
    supportsIntervalType         = No
    supportsAbsFunction          = Yes
    supportsAcosFunction         = No
    supportsAsinFunction         = No
    supportsAtanFunction         = No
    supportsAtan2Function        = No
    supportsCeilingFunction      = Yes
    supportsCosFunction          = Yes
    supportsCotFunction          = No
    supportsDegreesFunction      = No
    supportsExpFunction          = Yes
    supportsFloorFunction        = Yes
    supportsLogFunction          = Yes
    supportsLog10Function        = Yes
    supportsModFunction          = Yes
    supportsPiFunction           = No
    supportsPowerFunction        = Yes
    supportsRadiansFunction      = No
    supportsRandFunction         = No
    supportsRoundFunction        = Yes
    supportsSignFunction         = Yes
    supportsSinFunction          = Yes
    supportsSqrtFunction         = Yes
    supportsTanFunction          = Yes
    supportsTruncateFunction     = Yes
    supportsConcatFunction       = Yes
    supportsInsertFunction       = Yes
    supportsLcaseFunction        = Yes
    supportsLeftFunction         = Yes
    supportsLengthFunction       = Yes
    supportsLTrimFunction        = Yes
    supportsPositionFunction     = No
    supportsRepeatFunction       = Yes
    supportsReplaceFunction      = Yes
    supportsRightFunction        = Yes
    supportsRTrimFunction        = Yes
    supportsSpaceFunction        = Yes
    supportsSubstringFunction    = Yes
    supportsUcaseFunction        = Yes
    supportsExtractFunction      = No
    supportsCaseExpression       = No
    supportsCastFunction         = No
    supportsCoalesceFunction     = No
    supportsNullIfFunction       = No
    supportsConvertFunction      = Yes
    supportsSumFunction          = Yes
    supportsMaxFunction          = Yes
    supportsMinFunction          = Yes
    supportsCountFunction        = Yes
    supportsBetweenPredicate     = Yes
    supportsExistsPredicate      = Yes
    supportsInPredicate          = Yes
    supportsLikePredicate        = Yes
    supportsNullPredicate        = Yes
    supportsNotNullPredicate     = Yes
    supportsLikeEscapeClause     = Yes
    supportsClobType             = No
    supportsBlobType             = No
    charDatatypeName             = CHAR
    varCharDatatypeName          = VARCHAR2
    longVarCharDatatypeName      = CLOB
    clobDatatypeName             = N/A
    timeStampDatatypeName        = N/A
    binaryDatatypeName           = RAW
    varBinaryDatatypeName        = RAW
    longVarBinaryDatatypeName    = BLOB
    blobDatatypeName             = N/A
    intDatatypeName              = NUMBER
    doubleDatatypeName           = BINARY_DOUBLE
    varCharMaxLength             = 0
    longVarCharMaxLength         = 0
    clobMaxLength                = 0
    varBinaryMaxLength           = 0
    longVarBinaryMaxLength       = 0
    blobMaxLength                = 0
    timeStampMaxLength           = 0
    identifierCase               = Upper
    escapeCharacter              = \
    longVarCharDatatype          = -1
    clobDatatype                 = 0
    longVarBinaryDatatype        = -4
    blobDatatype                 = 0

    BIP8273I: The following datatypes and functions are not natively supported by datasource 'XE' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, TIMESTAMP, INTERVAL, CLOB, BLOB' Unsupported functions: 'ACOS, ASIN, ATAN, ATAN2, COT, DEGREES, PI, RADIANS, RAND, POSITION, EXTRACT, CASE, CAST, COALESCE, NULLIF' 
    Examine the specific datatypes and functions not supported natively by this datasource using this ODBC driver.  
    When using these datatypes and functions within ESQL, the associated data processing is done within IBM Integration Bus rather than being processed by the database provider.  
      
    Note that "functions" within this message can refer to functions or predicates. 


    BIP8071I: Successful command completion. 




    References -

    ftp://public.dhe.ibm.com/software/integration/support/supportpacs/individual/ie02_v2.pdf

    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbk58060_.htm