I have a simple sequence where all I want to do is to connect to the Tamino and update first record with the received XML. I?ve tried Tamino Logger component, but it looks like it is not suitable for this task as it keeps adding to the collection. I want to have always only one record in the collection, hence the decision was made to go with TaminoConnection and TaminoSingleAccessor. The following error is thrown in the log:
[slf5s.start]21 Oct 2004 15:12:06,921[slf5s.DATE] Thread-4[slf5s.THREAD] ERROR[slf5s.PRIORITY] xbd[slf5s.CATEGORY] - SagSequencer - SEQUENCER ERROR: sequence “file:/c:/Mediator/Dev/sequences/NVD718N.xml”, line 7, : com.softwareag.xbridge.exceptions.XException: Failed to perform start-session server http://localhost/tamino is not available . Connection name=NVD718N[slf5s.MESSAGE]
com.softwareag.xbridge.exceptions.XException: Failed to perform start-session server http://localhost/tamino is not available . Connection name=NVD718N
http://localhost/tamino is definitely available.
Here is the sequence XML:
<?xml version="1.0" encoding="UTF-8" ?>
-
-
-
-
-
We are just starting with Mediator & Tamino, so any leads and suggestions are really appreciated :).
Regards
Mikhail
Hello Mikhail,
I don’t think there is any real trick to accessing Tamino Databases. Most applications I have seen have worked without any problems.
Could it be that your database is set up with security?
Have you set up the proxy in the ComponentFactory? If so, did you add localhost to the list of nonProxyHosts?
The last and most important questions… What version of Mediator and Tamino are you using?
Regards,
- Matthew G.
Matthew,
>> Could it be that your database is set up with security?
I am sure it doesn’t have security. I can log XML into the database without any issues if TaminoLogger component is used. Also I can ping the database.
>>Have you set up the proxy in the ComponentFactory?
Not as I am aware of. I checked ComponentFactory settings through System Management Hub and didn’t find anything about proxy. So, I guess it hasn’t been set.
>>What version of Mediator and Tamino are you using?
Mediator 7.3.1
Tamino 4.2.1.2
Hi Mikhail,
I suggest you rerun the sequence with the Component Factory log level set to DEBUG and post any messages from the TaminoConnection component.
Best regards,
Mike
Mike & Matthew
The issue is solved. It took a second pair of eyes to see the problem? It was a typo in the database name. Stupid I know. :o
Thank you for your suggestions.