|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
installation of rules and formatter for message broker 6.1 |
« View previous topic :: View next topic » |
Author |
Message
|
ins0mniac2 |
Posted: Fri Jun 13, 2008 7:42 am Post subject: installation of rules and formatter for message broker 6.1 |
|
|
Apprentice
Joined: 25 Jul 2005 Posts: 33
|
Can anyone point me to the documentation of how to install rules and formatter for Message broker 6.1 on AIX for the runtime and windows for toolkit.
Thank you |
|
Back to top |
|
 |
mqmatt |
Posted: Fri Jun 13, 2008 8:33 am Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
Very little (if anything) has changed over v6.0; you can follow the 6.0 documentation you'll already have. IBM no longer offers R&F to new MB customers. |
|
Back to top |
|
 |
ins0mniac2 |
Posted: Fri Jun 13, 2008 10:38 am Post subject: |
|
|
Apprentice
Joined: 25 Jul 2005 Posts: 33
|
I followed the installation of the rules and formatter, however, the broker does not recognize the neon formatter nodes and I get the following error when I try to deply bar files containing neon formatter nodes.
Quote: |
BIP2241E: Loadable Implementation Library (.lil, .jar or .par) not found for message flow node type 'NEONTransformNode' in message flow 'TPI_SAP_ORDER_V1_4'.
The message broker received an instruction to create a message flow node of type 'NEONTransformNode', in message flow 'TPI_SAP_ORDER_V1_4'. The broker does not have the capability to create nodes of this type because an implementation library for this node type was not found in the LIL path.
Ensure that the LIL path is correct and contains all the necessary node implementation libraries, including those supplied by IBM. The node name is case sensitive so ensure the toolkit and runtime names match. If the broker is trying to create a node type that ends in 'NodeNode' then ensure that when the node was registered with the toolkit the name registered didn't end in 'Node'. Then ensure that the message flow and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
|
Here is my environment variable list on AIX
Quote: |
CGI_DIRECTORY=/var/docsearch/cgi-bin
CLASSPATH=/opt/IBM/mqsi61/6.1/classes/derby.jar:/opt/IBM/mqsi61/6.1/classes/ConfigManagerProxy.jar:/opt/IBM/mqsi61/6.1/classes/configutil.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib/connector.jar:/opt/IBM/mqsi61/6.1/messages:/var/mqsi/common/wsrr:
DEFAULT_BROWSER=netscape
DISTHUB_PATH=/opt/IBM/mqsi61/6.1
DOCUMENT_DIRECTORY=/usr/docsearch/html
DOCUMENT_SERVER_MACHINE_NAME=localhost
DOCUMENT_SERVER_PORT=49213
ERRNO=0
EXTENDED_HISTORY=ON
FCEDIT=/usr/bin/ed
HOME=/home/maxmqs6
IFS='
'
LANG=en_US
LATEST_NNSY_CSD=0
LC__FASTMSG=true
LIBPATH=/oinstall/9206_0_64/lib32:/opt/IBM/rf42/rfe/lil:/opt/IBM/rf42/rfe/bin:/opt/IBM/mqsi61/6.1/jre15/ppc64/bin:/opt/IBM/mqsi61/6.1/jre15/ppc64/bin/classic:/opt/IBM/rf42/rfe/bin:/usr/mqm/java/lib64:/usr/mqm/lib64:/opt/IBM/mqsi61/6.1/ODBC64/V5.3/lib:/opt/IBM/mqsi61/6.1/xml4c/lib64:/opt/IBM/mqsi61/6.1/xlxpc/lib64:/opt/IBM/mqsi61/6.1/lib:/opt/IBM/mqsi61/6.1/bin:
LIBPATH64=/oinstall/9206_0_64/lib32:/opt/IBM/rf42/rfe/lil:/opt/IBM/rf42/rfe/bin:
LINENO=1
LOCPATH=/usr/lib/nls/loc
LOGIN=maxmqs6
LOGNAME=maxmqs6
MAIL=/usr/spool/mail/maxmqs6
MAILCHECK=600
MAILMSG='[YOU HAVE NEW MAIL]'
MANPATH=/usr/share/man:/usr/dt/man:/usr/local/bin:/opt/freeware/man
MINIMUM_MB_LEVEL=0
MQSI_CATALINA_HOME=/opt/IBM/mqsi61/6.1/catalina
MQSI_DEVELOPMENT=/var/mqsi/registry
MQSI_EXMLTCONFIGPATH=/opt/IBM/mqsi61/6.1/exmltConfig
MQSI_FAD=4
MQSI_FILEPATH=/opt/IBM/mqsi61/6.1
MQSI_JARPATH=/opt/IBM/mqsi61/6.1/classes:/opt/IBM/mqsi61/6.1/messages
MQSI_JREPATH=/opt/IBM/mqsi61/6.1/jre15
MQSI_LIBPATH32=/opt/IBM/mqsi61/6.1/jre15/bin:/opt/IBM/mqsi61/6.1/jre15/bin/classic:/opt/IBM/rf42/rfe/bin:/opt/mqm/java/lib:/usr/mqm/lib:/opt/IBM/mqsi61/6.1/ODBC32/V5.3/lib:/opt/IBM/mqsi61/6.1/xml4c/lib:/opt/IBM/mqsi61/6.1/xlxpc/lib
MQSI_LIBPATH64=''
MQSI_LILPATH=:/opt/IBM/rf42/rfe/lil:
MQSI_LILPATH32=/opt/IBM/mqsi61/6.1/lil32:/opt/IBM/mqsi61/6.1/jplugin:/opt/IBM/rf42/rfe/lil
MQSI_LILPATH64=/opt/IBM/mqsi61/6.1/lil:/opt/IBM/mqsi61/6.1/jplugin:/opt/IBM/rf42/rfe/lil
MQSI_REGISTRY=/var/mqsi
MQSI_SECURITY_PROVIDER_PATH32=/opt/IBM/mqsi61/6.1/SecurityProviders32
MQSI_SECURITY_PROVIDER_PATH64=/opt/IBM/mqsi61/6.1/SecurityProviders
MQSI_VERSION=6.1.0.2
MQSI_VERSION_F=2
MQSI_VERSION_M=0
MQSI_VERSION_R=1
MQSI_VERSION_V=6
MQSI_WORKPATH=/var/mqsi
NEON_HOME=/opt/IBM/rf42
NLSPATH=/opt/IBM/rf42/rfe/messages/6.0/En_US/%N:/opt/IBM/rf42/rfe/messages/6.1/En_US/%N:/opt/IBM/mqsi61/6.1/messages/%L/%N:/opt/IBM/mqsi61/6.1/messages/En_US/%N:/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat
NNSY_CATALOGUES=/opt/IBM/rf42/rfe/NNSYCatalogues
NNSY_ROOT=/opt/IBM/rf42/rfe
NN_CONFIG_FILE_PATH=/opt/IBM/rf42/rfe/install.sql_rulfmt42/inst_db
ODBCINI=/opt/IBM/mqsi61/6.1/ODBC64/V5.3/odbc64.ini
ODMDIR=/etc/objrepos
OLDPWD=/opt/IBM/mqsi61/6.1
OPTIND=1
ORACLE_BASE=/home/maxmqs6
ORACLE_HOME=/oinstall/9206_0_64
PATH=/opt/IBM/mqsi61/6.1/jre15/ppc64/bin:/opt/IBM/rf42/rfe/bin:/opt/IBM/mqsi61/6.1/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home/maxmqs6/bin:/usr/bin/X11:/sbin:/opt/IBM/mqsi61/6.1/bin:/opt/IBM/rf42/rfe/bin:.:/oinstall/9206_0_64/bin
PPID=1241298
PS1='$USER\@rhux15\:${PWD##*/} \# '
PS2='> '
PS3='#? '
PS4='+ '
PWD=/opt/IBM/mqsi61/6.1/lil
RANDOM=5922
SCRIPT=/var/mqsi/common/profiles/com.sybase.nnsy.sh
SECONDS=85363
SHELL=/usr/bin/ksh
SYMCLI_WAIT_ON_GK=1
TERM=vt100
TERM_DEFAULT=lft
TMOUT=0
TNS_ADMIN=/oracle/app/MQ6/network
TZ=CUT0
USER=maxmqs6
WMB61_HOME=/opt/IBM/mqsi61/6.1
|
|
|
Back to top |
|
 |
prk |
Posted: Fri Jun 13, 2008 9:04 pm Post subject: |
|
|
Centurion
Joined: 17 Feb 2004 Posts: 102
|
Do you have the nnsyreg.dat file on the AIX server needed by NEON. There are a series of steps that you will have to run on WMB 6.0 after installing R&F, but am not sure for 6.1. |
|
Back to top |
|
 |
ins0mniac2 |
Posted: Tue Jun 17, 2008 5:31 am Post subject: |
|
|
Apprentice
Joined: 25 Jul 2005 Posts: 33
|
yes the file exists, however it is 0 bytes. Also I think that file is for configuring the DB, I would expect to see a different error rather then the one I am receiving. It seems that the broker can't detect the lil file on the AIX server even though I have MQSI_LILPATH pointed to lil and MQSI_LILPATH32 pointed to lil32 directory. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|