| Author |
Message |
 Topic: Statistics Monitoring Issue |
deepnair
Replies: 3
Views: 2615
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 26, 2012 9:28 pm Subject: Statistics Monitoring Issue |
Also two nodes in the flow - a label node and a compute node have the same name - "Initialization", will this have an impact ?
Two nodes in the same flow - can have the same name if i und ... |
| Topic: Statistics Monitoring Issue |
deepnair
Replies: 3
Views: 2615
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 26, 2012 9:26 pm Subject: Statistics Monitoring Issue |
We have an issue where in an EG when we turn on the 'Statistics Monitoring', the flow fails with below exception
--------------------------------------------
+BIP2121E LPTPBRKR LPTPEG13 84 THE THREA ... |
| Topic: Deploy Flow without queues defined |
deepnair
Replies: 4
Views: 2950
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 10, 2012 10:13 am Subject: Deploy Flow without queues defined |
yes i did attend all broker trainings, also could not find this info in infocenter links.
will definitely experiment this - a solution that i can think of now is - we can deploy but keep the flows ... |
| Topic: Deploy Flow without queues defined |
deepnair
Replies: 4
Views: 2950
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 10, 2012 7:37 am Subject: Deploy Flow without queues defined |
Hi - if we deploy a broker flow to an execution group with an input queue that does not exist, will it give any errors ?
We want to deploy a flow to meet timelines and keep it in cold state till cl ... |
| Topic: XI50 vs Broker |
deepnair
Replies: 26
Views: 13281
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 26, 2012 12:55 pm Subject: XI50 vs Broker |
| The things thats happening in our env is that - almost all services are getting pushed to XI50 i.e. only when in XI50 + Stylesheet - the transformations get difficult or hard to implement (example spe ... |
| Topic: XI50 vs Broker |
deepnair
Replies: 26
Views: 13281
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jun 25, 2012 11:22 am Subject: XI50 vs Broker |
Its a frequent discussion that comes up in design sessions. For e.g. I have a requirement - XML Format A needs to be transformed to XML Format B, load is 30 transactions per second
In such a case, ... |
| Topic: XI50 vs Broker |
deepnair
Replies: 26
Views: 13281
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jun 20, 2012 2:17 pm Subject: XI50 vs Broker |
Hi - one question that keeps coming up in many discussions is - broker cannot perform at very high loads (the performance degrades) - so xi50 is required. Is this a true statement ? Please comment.
... |
| Topic: Rolling File Appender using WMB nodes |
deepnair
Replies: 14
Views: 10101
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 12, 2012 1:53 pm Subject: Rolling File Appender using WMB nodes |
zpat
I think log files are a symptom of the casual approach to development that seems common these days.
I spent my time as a developer without ever using a log file. I simply made sure my code ... |
| Topic: Message Broker and Source Control |
deepnair
Replies: 19
Views: 15410
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 12, 2012 1:39 pm Subject: Message Broker and Source Control |
| IBM Clearcase or Oracle Perforce |
| Topic: MRM XML Validation with PARSE Statement Not validating |
deepnair
Replies: 16
Views: 10289
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 17, 2012 12:48 pm Subject: MRM XML Validation with PARSE Statement Not validating |
| @Kimbert - Yes you are right, they can do at the input node but I think @satya is planning to reuse an exisitng message set and an exisitng flow that caters to non XML too, so they cannot modify the i ... |
| Topic: MRM XML Validation with PARSE Statement Not validating |
deepnair
Replies: 16
Views: 10289
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 17, 2012 6:58 am Subject: MRM XML Validation with PARSE Statement Not validating |
Another way is to check if your coming message is XML (convert BLOB to string and check for XML), if yes then only for validation purpose - parse it as XMLNSC and throw error.
If there is no except ... |
| Topic: Handling two different version of the same code |
deepnair
Replies: 16
Views: 7778
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 16, 2012 10:16 am Subject: Handling two different version of the same code |
You can do the same kind of thing from ESQL without needing to go into Java.
The advantage I see here of java is that we need not deploy the flow with the business logic again (thus needing regres ... |
| Topic: Handling two different version of the same code |
deepnair
Replies: 16
Views: 7778
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 16, 2012 9:44 am Subject: Handling two different version of the same code |
I think you should externalize such logic into java and invoke java from esql based on conditions, for e.g.
ESQL Code
call Core java translation
Java Code
Identify input type (take it as ke ... |
| Topic: Checking for CData in JCN |
deepnair
Replies: 3
Views: 2605
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 10, 2012 6:45 am Subject: Checking for CData in JCN |
Kimbert
It certainly does process it in a 'particular' way - but I am struggling to understand why. Can you explain why you are not just doing this?
SET SoapBodyString = InputRoot.XMLNSC.*:Envelop ... |
| Topic: Checking for CData in JCN |
deepnair
Replies: 3
Views: 2605
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 09, 2012 2:00 pm Subject: Checking for CData in JCN |
Hi - I have the esql code as below
IF FIELDTYPE(InputRoot.XMLNSC.*:Envelope.*:Body) = XMLNSC.CDataField THEN
SET TempBlob = ASBITSTREAM(InputRoot.XMLNSC.*:Envelope ... |
