| Author |
Message
|
| anandsitha |
 Posted: Wed Sep 07, 2011 7:51 am Post subject: Error While Creating a Simple Flow Using File Read Node |
 |
|
Acolyte
Joined: 26 Jul 2011
Posts: 59
|
Hi -
My Map would be
File Input Node ---->File Read Node ---->Compute Node ---->File Output Node.
I have installed MB Fix Pack 7.0.0.3. But I while deploying my flow, I am getting the following error.
| Code: |
Begin running task [Deploying [FileReadMsgFlowPrjBAR.bar] to execution group [FileReadExecutionGroup]]
BIP2087E: Broker MB7BROKER was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group 'FileReadExecutionGroup' received an invalid configuration message. See the following messages for details of the error.
The broker was asked to deploy a message flow which contained properties that were not recognized by the broker. This typically results from a message flow requiring a version or type of node that is not supported by the broker installation.
Check that the message flow is only using properties or nodes that are supported on the broker. Check that all necessary user-defined extensions are installed and that they are of a version that is compatible with the message flow.
BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow node type 'ComIbmFileReadNode' in message flow 'FileReadMsgFlw'.
The broker received an instruction to create a message flow node of type 'ComIbmFileReadNode', in message flow 'FileReadMsgFlw'. The broker cannot create nodes of this type because an implementation library for this node type does not exist in the LIL path.
Ensure that the LIL path is correct, and that it contains all the required node implementation libraries, including those supplied by IBM. The node name is case sensitive, therefore check that the toolkit and runtime names match. If the broker is trying to create a node type that ends in 'NodeNode', ensure that when the node was registered with the toolkit the name registered did not end in 'Node'.
Also ensure that you have saved the message flow, and any nested message flows. Redeploy the new configuration to the broker, specifying a complete configuration. If the LIL file is correct, check that the message node type is correct.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation |
Regards
Sithanandam |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Sep 07, 2011 7:57 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| anandsitha |
| Posted: Wed Sep 07, 2011 8:59 pm Post subject: |
|
|
Acolyte
Joined: 26 Jul 2011
Posts: 59
|
Hi-
Initially I got the below output.
| Code: |
Queue Manager = 'MB7QMGR'
User lil path = ''
User exit path = ''
Active user exits = ''
LDAP principal = ''
LDAP crendentials = ''
ICU coverter path = ''
Trusted <fastpath> Queue Manager application = 'false'
Configuaration chagne timeout = '300' seconds
Internal configuaration timeout = '60' minutes
Operation mode = 'enterprise'
Fixpack capability level = 'all' (effective levl 'unrestricted')
Broker registry format = 'v7.0'
Administration security = 'inactive'
Multi-instance Broker = 'false'
Shared Work Path = 'none'
Star as WebSphere MQ Service = 'undefined'
|
After using mqsichangebroker MB7BROKER -v '7.0.0.3' I got the below details.
| Code: |
Queue Manager = 'MB7QMGR'
User lil path = ''
User exit path = ''
Active user exits = ''
LDAP principal = ''
LDAP crendentials = ''
ICU coverter path = ''
Trusted <fastpath> Queue Manager application = 'false'
Configuaration chagne timeout = '300' seconds
Internal configuaration timeout = '60' minutes
Operation mode = 'enterprise'
Fixpack capability level = '7.0.0.3' (effective level '7.0.0.1')
Broker registry format = 'v7.0'
Administration security = 'inactive'
Multi-instance Broker = 'false'
Shared Work Path = 'none'
Star as WebSphere MQ Service = 'undefined' |
[/code] |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu Sep 08, 2011 1:17 am Post subject: Re: Error While Creating a Simple Flow Using File Read Node |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| anandsitha wrote: |
Initially I got the below output.
| Code: |
| Fixpack capability level = 'all' (effective levl 'unrestricted') |
|
Ok.
| anandsitha wrote: |
After using mqsichangebroker MB7BROKER -v '7.0.0.3' I got the below details.
| Code: |
| Fixpack capability level = '7.0.0.3' (effective level '7.0.0.1') |
|
The -f function level parameter may work better. |
|
| Back to top |
|
|
| anandsitha |
| Posted: Thu Sep 08, 2011 2:34 am Post subject: |
|
|
Acolyte
Joined: 26 Jul 2011
Posts: 59
|
Hi-
Still getting the same error. Do you know how to set LIL and setting JAR files.
Regards
Sithanandam.V |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Sep 08, 2011 4:17 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| anandsitha wrote: |
| Still getting the same error. |
Did you follow the advice above? Or just decide it was easier to ask the question again here? 
Finish the upgrade then see if you need to adjust the configuration.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| anandsitha |
| Posted: Tue Oct 11, 2011 1:12 am Post subject: |
|
|
Acolyte
Joined: 26 Jul 2011
Posts: 59
|
Hi-
There are 2 links one for upgrading mbtoolkit and other is for upgrading message broker. Initially i have upgraded mbtoolkit and thought that everything is done. Now i have found it is our mistake. I have upgraded fixpack and my file read node is working fine.
Regards
Sithanandam.V |
|
| Back to top |
|
|
|
|
