| Author |
Message
|
| tzm1802c |
 Posted: Mon Jul 02, 2012 10:09 pm Post subject: File Output with SFTP/FTP |
 |
|
Novice
Joined: 15 Feb 2012
Posts: 16
|
| Deployment of message flow with FileOutput node node with FTP/SFTP fails in WMB 7.0.0.2 and WMB 6.1 What needs to be done to fix this? |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Jul 02, 2012 10:35 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| The usual - look at the WMB error log. See what the problem is - fix it. |
|
| Back to top |
|
|
| tzm1802c |
| Posted: Mon Jul 02, 2012 10:43 pm Post subject: |
|
|
Novice
Joined: 15 Feb 2012
Posts: 16
|
Here is the error: its not self explanatory:
Begin running task [Deploying [FILEOUTPUT.msgflow] to execution group [WEBSERVICE]]
BIP2087E: Broker LOCALBRKR 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 'WEBSERVICE' 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.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jul 02, 2012 11:10 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
What version is the toolkit?
Did you enable all broker function with mqsichangebroker <BRKER> -f all |
|
| Back to top |
|
|
| tzm1802c |
| Posted: Tue Jul 03, 2012 12:45 am Post subject: |
|
|
Novice
Joined: 15 Feb 2012
Posts: 16
|
| Toolkit and MB version is 7.0.0.2. I did run the mqsichangebroker command. |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Jul 03, 2012 1:50 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| See the following messages for details of the error. |
Are there other errors? If so please post them as well...
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| tzm1802c |
| Posted: Tue Jul 03, 2012 4:08 am Post subject: |
|
|
Novice
Joined: 15 Feb 2012
Posts: 16
|
BIP4041E: Execution group 'WEBSERVICE' 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. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jul 03, 2012 4:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tzm1802c wrote: |
| Check that the message flow is only using properties or nodes that are supported on the broker. |
Is it?
| tzm1802c wrote: |
| Check that all necessary user-defined extensions are installed and that they are of a version that is compatible with the message flow. |
Are they?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Tue Jul 03, 2012 5:15 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
If you have defined any configurable services that are used in your message flow (for FTP or SFTP) and are not created on the broker where you are trying to deploy the flow, the deployment will fail in version 7.0.
Cheers, |
|
| Back to top |
|
|
| tzm1802c |
| Posted: Tue Jul 03, 2012 10:00 pm Post subject: |
|
|
Novice
Joined: 15 Feb 2012
Posts: 16
|
| the funny part is that I dont have any configurable services defined in my message flow |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 05, 2012 4:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tzm1802c wrote: |
| the funny part is that I dont have any configurable services defined in my message flow |
If you're using FTP/SFTP that could be the problem. If those nodes in that flow have been coded to use configurable services.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jul 05, 2012 5:15 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Check out the JVM log in the execution group directory. Sometimes can be illuminating.
I wish IBM had not used those long hex strings for the directory names though. |
|
| Back to top |
|
|
| ceteareth |
| Posted: Sun Aug 26, 2012 11:07 pm Post subject: |
|
|
Acolyte
Joined: 12 Aug 2012
Posts: 51
|
I am having the same issue, i modified the file output node sample from the toolkit to be able to output file through FTP. I am able to generate the bar file but receives the error below when deploying the bar file. Another thing is that i can generate and deploy the BAR file if I uncheck Remote Transfer in FTP tab. I am using WMBT version 8
| Quote: |
BIP4041E: Execution group 'FileOutputNodeSampleExecutionGroup' 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. |
Details entered in FTP tab.
| Quote: |
Remote Transfer: checked
Transfer Protocol: FTP
Server and Port: 10.20.20.101
Security identity:
Server directory: ftp
Transfer Mode: Binary
Action if remote file exists: Replace Existing File (PUT)
Retail local file after transfer:
|
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 27, 2012 2:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
My comments above apply regarding configurable services and FTP.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ceteareth |
| Posted: Mon Aug 27, 2012 3:42 pm Post subject: |
|
|
Acolyte
Joined: 12 Aug 2012
Posts: 51
|
| Hi Vitor, thanks for the response. i do not have any configurable service. if i uncheck the Remote Transfer in the FTP tab it works perfectly fine. but once i check remote transfer thats when i get the error. |
|
| Back to top |
|
|
|
|
