Wednesday, 4 February 2015

More on the IBM Integration Feature

Following on from my earlier post: -


I created a response file to install the IBM Integration Feature into my existing WAS environment: -

<?xml version='1.0' encoding='UTF-8'?>
<agent-input>
  <variables>
    <variable name='sharedLocation' value='/opt/IBM/IMShared'/>
  </variables>
  <server>
    <repository location='/tmp/pickle'/>
  </server>
  <profile id='IBM WebSphere Application Server V8.5' installLocation='/opt/IBM/WebSphere/AppServer'>
    <data key='eclipseLocation' value='/opt/IBM/WebSphere/AppServer'/>
    <data key='user.import.profile' value='false'/>
    <data key='cic.selector.os' value='linux'/>
    <data key='cic.selector.arch' value='x86'/>
    <data key='cic.selector.ws' value='gtk'/>
    <data key='cic.selector.nl' value='en'/>
  </profile>
  <install modify='false'>
    <!-- IBM Integration Bus Administration for Version 8.5 of WebSphere Application Server 9.0.0.0 -->
    <offering profile='IBM WebSphere Application Server V8.5' id='com.ibm.wmb.extension.wasv85' version='9.0.0.20130703_1409' features='com.ibm.wmb.admin.main' installFixes='none'/>
  </install>
  <preference name='com.ibm.cic.common.core.preferences.eclipseCache' value='${sharedLocation}'/>
  <preference name='com.ibm.cic.common.core.preferences.connectTimeout' value='30'/>
  <preference name='com.ibm.cic.common.core.preferences.readTimeout' value='45'/>
  <preference name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount' value='0'/>
  <preference name='offering.service.repositories.areUsed' value='true'/>
  <preference name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode' value='false'/>
  <preference name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication' value='false'/>
  <preference name='http.ntlm.auth.kind' value='NTLM'/>
  <preference name='http.ntlm.auth.enableIntegrated.win32' value='true'/>
  <preference name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts' value='true'/>
  <preference name='com.ibm.cic.common.core.preferences.keepFetchedFiles' value='false'/>
  <preference name='PassportAdvantageIsEnabled' value='false'/>
  <preference name='com.ibm.cic.common.core.preferences.searchForUpdates' value='false'/>
  <preference name='com.ibm.cic.common.core.preferences.import.enabled' value='true'/>
  <preference name='com.ibm.cic.agent.ui.displayInternalVersion' value='false'/>
  <preference name='com.ibm.cic.common.sharedUI.showErrorLog' value='true'/>
  <preference name='com.ibm.cic.common.sharedUI.showWarningLog' value='true'/>
  <preference name='com.ibm.cic.common.sharedUI.showNoteLog' value='true'/>
</agent-input>

resulting in this: -

/opt/IBM/InstallationManager/eclipse/tools/imcl listInstalledPackages

com.ibm.cic.agent_1.8.1000.20141126_2002
com.ibm.bpm.ADV.v85_8.5.5000.20140604_1130
com.ibm.websphere.ND.v85_8.5.5004.20141119_1746
com.ibm.wmb.extension.wasv85_9.0.0.20130703_1409

...
com.ibm.websphere.IHS.v85_8.5.5004.20141119_1746
com.ibm.websphere.PLG.v85_8.5.5004.20141119_1746

/opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -augment -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/dmgr.broker/ -profileName Dmgr01

INSTCONFSUCCESS: Profile augmentation succeeded.

Having started my Deployment Manager: -

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/startManager.sh

I'm now seeing my IIB Integration Nodes ( aka Brokers ): -




For the record: -

Integration nodes

Use this page to view a list of brokers (integration nodes). A broker is a set of execution processes that hosts one or more message flows to route, transform, and enrich in-flight messages. You must create a connection to a broker, before you can view artifacts such as execution groups (integration servers), integration services, applications and message flows.

Integration servers

Use this page to view execution groups (integration servers). An execution group is a named grouping of message flows that have been assigned to a broker (integration node). The broker enforces a degree of isolation between message flows in distinct execution groups by ensuring that they run in separate address spaces or as individual processes.

Integration services

Use this page to view integration services. An integration service is a container for a services solution, and has a defined interface with specified operations that are implemented as separate message subflows.

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...