| Author |
Message
|
| marquies |
 Posted: Mon Apr 23, 2012 12:22 am Post subject: Unable to deploy EmailOutputNode to the Broker v7.0.0.3 |
 |
|
Novice
Joined: 01 Feb 2012
Posts: 15
|
Begin running task [Deploying [SMTP.msgflow] to execution group [Mail]]
BIP2087E: Broker SANGAM_WMB 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 'Mail' 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 'ComIbmEmailOutputNode' in message flow 'SMTP'.
The broker received an instruction to create a message flow node of type 'ComIbmEmailOutputNode', in message flow 'SMTP'. 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. |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Apr 23, 2012 12:38 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
What is your effective fixpack level?
mqsiservice <broker> |
|
| Back to top |
|
|
| marquies |
| Posted: Mon Apr 23, 2012 1:30 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 15
|
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepage=ISO-8859-1, in ascii=ISO-8859-1
JAVA console codepage name=ISO-8859-1
BIP8996I: Version: 7003
BIP8997I: Product: WebSphere Message Broker
BIP8998I: CMVC Level: S700-FP03
BIP8999I: Build Type: Production, 64 bit, rios_aix_4 |
|
| Back to top |
|
|
| marquies |
| Posted: Mon Apr 23, 2012 1:33 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 15
|
The above output for for mqsiservice -v
Please find below the output of mqsiservice <broker>
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepage=ISO-8859-1, in ascii=ISO-8859-1
JAVA console codepage name=ISO-8859-1
Install Path = /usr/mqsi
Shared Work Path = /var/mqsi/mqsi
Local Work Path = /var/mqsi
Component UUID = 85199b4c-b60e-11e0-b09d-000000000000
process id = 7209060
queue manager = QMGR01
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
Fixpack capability level = (effective level 7.0.0.1) |
|
| Back to top |
|
|
| marquies |
| Posted: Mon Apr 23, 2012 1:51 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 15
|
| Hi Zpat, Can I execute the command "mqsichangebroker MB7BROKER -f 7.0.0.3" and then try delpoying the flow with the emailoutputnode? Because I observe that the Broker Runtime version is 7.0.0.3 and the Fixpack capability level = (effective level 7.0.0.1) is for the broker component. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Apr 23, 2012 2:08 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| You certainly can. Personally I always use -f all |
|
| Back to top |
|
|
| marquies |
| Posted: Mon Apr 23, 2012 2:28 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 15
|
Zpat, it didn't work. Getting the same error as above while deploying the flow with an emailoutputnode into the broker.
Any other suggestion? |
|
| Back to top |
|
|
| marquies |
| Posted: Mon Apr 23, 2012 2:32 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 15
|
I executed the command "mqsichangebroker <broker> -f all"
The o/p of the mqsiservice <broker> is now
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepage=ISO-8859-1, in ascii=ISO-8859-1
JAVA console codepage name=ISO-8859-1
Install Path = /usr/mqsi
Shared Work Path = /var/mqsi/mqsi
Local Work Path = /var/mqsi
Component UUID = 85199b4c-b60e-11e0-b09d-000000000000
process id = 13697270
queue manager = QMGR01
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
Fixpack capability level = all (effective level 7.0.0.3) |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Apr 23, 2012 3:43 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| And you can deploy other flows OK? Sounds like PMR time to me. |
|
| Back to top |
|
|
| marquies |
| Posted: Mon Apr 23, 2012 4:13 am Post subject: |
|
|
Novice
Joined: 01 Feb 2012
Posts: 15
|
Is it? But I'm able to deploy the same msgflow into a Windows Broker v7.0.0.3.
Facing this issue only whiling deploying the msgflow into an AIX Broker v7.0.0.3. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Apr 23, 2012 4:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
it's either an install issue or a configuration issue - i.e. the AIX broker might be configured as an edition that does not allow use of the EmailOutput node.
But I would expect that the error message would indicate that - i.e. that you're using a Remote Adapter Edition rather than an Enterprise edition or etc.
So, again, open a PMR. |
|
| Back to top |
|
|
|
|
