| Author |
Message |
 Topic: Failed to query JNDI: Failed to connect to the server at tcp |
SABCAS
Replies: 1
Views: 5091
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Tue Oct 14, 2008 5:59 am Subject: Failed to query JNDI: Failed to connect to the server at tcp |
Hello,
there is a Firewall, the problem is solved |
| Topic: Failed to query JNDI: Failed to connect to the server at tcp |
SABCAS
Replies: 1
Views: 5091
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Oct 06, 2008 5:13 am Subject: Failed to query JNDI: Failed to connect to the server at tcp |
Hello
I have a problem with Connection a Broker Message Flow to Tibco EMS Provider. I set the JMS Output node with the following
intialFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactor ... |
| Topic: BIP5005E: No valid body of the document could be found. |
SABCAS
Replies: 3
Views: 6973
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 19, 2008 12:04 am Subject: BIP5005E: No valid body of the document could be found. |
Hallo
I consider your suggestion and it 's working but with a little syntax error I correct, so your Code look like:
SET OutputRoot.XMLNS.(XML.NamespaceDecl)xmlns:xsi= 'http://www.w3.org/2001/XMLSch ... |
| Topic: BIP5005E: No valid body of the document could be found. |
SABCAS
Replies: 3
Views: 6973
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jun 18, 2008 5:56 am Subject: BIP5005E: No valid body of the document could be found. |
Hello
I made a little MessageFlow to split a xml message, this is the input message:
<?xml version="1.0" encoding="ISO-8859-1"?>
<lst xmlns="http://www.swisscom.co ... |
| Topic: DB2 DEADLOCKS OCCURS WHEN USING PROCESS MONITOR |
SABCAS
Replies: 3
Views: 13093
|
Forum: Workflow Engines - IBM MQ Workflow & Business Process Choreographer Posted: Mon May 26, 2008 1:29 am Subject: DB2 DEADLOCKS OCCURS WHEN USING PROCESS MONITOR |
Hi,
yes we used fmczutil to make the rbind of DB2, and it was succesfully terminated, but I still have a timeout when I try on the Process to see the ProcessMonitor.
thanks a Lot
Ciao
Sabato |
| Topic: DB2 DEADLOCKS OCCURS WHEN USING PROCESS MONITOR |
SABCAS
Replies: 3
Views: 13093
|
Forum: Workflow Engines - IBM MQ Workflow & Business Process Choreographer Posted: Thu May 22, 2008 8:41 am Subject: DB2 DEADLOCKS OCCURS WHEN USING PROCESS MONITOR |
Hallo
I use the MQ Workflow 3.6 + SP4 on AIX, and I have a Problem with one Process when I try to use the processMonitor
WEBCLI1_exception.log
Index Occur Time of last Occurence Exception Sourc ... |
| Topic: Parameters could not be match with Database stored procedure |
SABCAS
Replies: 4
Views: 12039
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue May 06, 2008 10:01 pm Subject: Parameters could not be match with Database stored procedure |
OK, It's working
Thanks a lot for your suggestion
Ciao
Sabato  |
| Topic: Parameters could not be match with Database stored procedure |
SABCAS
Replies: 4
Views: 12039
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon May 05, 2008 2:41 am Subject: Parameters could not be match with Database stored procedure |
Hallo,
I change the call to the stored procedure like follow:
CALL INS_SPT_DELTA_MSG(errMsg,
msgid,
vorgang,
vlineid,
pooltype,
terminationtype,
upstreamspeed,
downstreamSpeed,
fix ... |
| Topic: Parameters could not be match with Database stored procedure |
SABCAS
Replies: 4
Views: 12039
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Apr 30, 2008 1:46 am Subject: Parameters could not be match with Database stored procedure |
Hello
I have a problem between the call of stored procedures from MessageFlow and the Stored procedures definition on Oracle Database.
I get from Oracle People the following definition:
Dies ist di ... |
| Topic: ORA-01017: invalid username/password : Logon denied |
SABCAS
Replies: 3
Views: 5610
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 29, 2008 11:49 pm Subject: ORA-01017: invalid username/password : Logon denied |
Hello,
I solved the problem, it was the $ Character into the password with AIX , UNIX, I have to use before the $ Character an Escape Character \.
Thanks
Ciao
Sabato  |
| Topic: ORA-01017: invalid username/password : Logon denied |
SABCAS
Replies: 3
Views: 5610
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 29, 2008 8:51 pm Subject: ORA-01017: invalid username/password : Logon denied |
Hello,
yes I did the following Command
mqsisetdbparms SBE1789 -n NOVISA -u user_esb_spt -p *******
I thing that the problem could be into the special Character in password
The Oracle Admin used a ... |
| Topic: ORA-01017: invalid username/password : Logon denied |
SABCAS
Replies: 3
Views: 5610
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 29, 2008 6:13 am Subject: ORA-01017: invalid username/password : Logon denied |
Hello, I have a problem to connect to Host ORACLE DB, I have update my odbc.ini:
[SERVER]
Driver=/opt/IBM/mqsi/6.0/merant/lib/UKor820.so
Description=DataDirect 5.0 Oracle
EnableDescribeParam=1
Op ... |
| Topic: Broker V6 connection to Host Oracle DB Problem |
SABCAS
Replies: 3
Views: 3416
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 31, 2008 6:49 am Subject: Broker V6 connection to Host Oracle DB Problem |
Hallo
I want to connect via odbc den Broker to a Host Oracle DB hier you can see the odbc.ini File:
[ODBC Data Sources]
I0SIFPAP=IBM DB2 ODBC Driver
WBIMBBK1=IBM DB2 ODBC Driver
WBIMBCM1=IBM DB2 ... |
| Topic: PubSub Problem with non-durable subscription |
SABCAS
Replies: 4
Views: 6526
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jan 10, 2008 2:27 am Subject: PubSub Problem with non-durable subscription |
Hallo
I have in InfoCenter :
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/aq19770_.htm
like it follows
"Client applications that are dev ... |
| Topic: PubSub Problem with non-durable subscription |
SABCAS
Replies: 4
Views: 6526
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jan 09, 2008 7:43 am Subject: PubSub Problem with non-durable subscription |
Hallo
I have a Trace Log and the following Message will be send to Node Publish
**** Input Message to Publication Message Broker ********
2008-01-09 15:14:37.208740
(
(0x01000000):Properties ... |
