cancel
Showing results for 
Search instead for 
Did you mean: 

XML Query doesnt run from Scheduler

former_member192939
Active Participant
0 Kudos

Hi ..

XML Qry runs fine when it is run by a user in the transaction.

If the same trx is executed from the scheduler .. the XML Qry fails..

URL used in the XML Qry is /XMII/Illuminator?service=SystemInfo&Mode=Status&Content-Type=text/xml

Any work arounds or a ticket ?

- Ajay

Accepted Solutions (0)

Answers (1)

Answers (1)

agentry_src
Active Contributor
0 Kudos

Hi Ajay,

Can you provide the MII version and build, and if applicable, which NW version and SP?

Thanks,

Mike

former_member192939
Active Participant
0 Kudos

Hi Mike ..

MII Version >> 12.1.9 Build(121)

NW >> 7.11.5

Thanks

Ajay

Edited by: Ajay Malempati on Feb 2, 2012 2:30 PM

jcgood25
Active Contributor
0 Kudos

The WB has a user for permission to execute the XMLQuery template's data server (whoever is logged in).

Does your scheduled job have user credentials for the RunAs effect?

former_member192939
Active Participant
0 Kudos

Hi Jeremy,

I am not passing user credentials to the scheduler...

I will try that, but, how to get around the Message Processing Rule.

One of the collegue tried with user id and password, it dint work throwing out same error ..

"org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed.'

Thanks

Ajay

Edited by: Ajay Malempati on Feb 2, 2012 4:35 PM

0 Kudos

Message processing rules also have credentials that you can set, just like the scheduler...

Sam

former_member192939
Active Participant
0 Kudos

Hi Sam,

I am using 12.1.5.

I wasn't able to see anything in the "Message Processing Rules" where we can pass the credentials. Is there any other place I need to look into.

Thank you

Ajay.

0 Kudos

Ajay,

No, I was mistaken about the credentials being visible in the processing rules and have verified this against the latest 12.1 and 12.2 versions. In the XML Query try using the following URL instead:

server://XMII/Illuminator?service=SystemInfo&Mode=Status&Content-Type=text/xml

Regards,

Sam

former_member192939
Active Participant
0 Kudos

Thank you Sam..

I have tried .. it still has the same error ..

org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed.

- Ajay

0 Kudos

Ajay,

If you submit a ticket you will probably be asked to upgrade to the latest release of 12.1; which as of today is 12.1.9 Patch 3.

Sam

former_member192939
Active Participant
0 Kudos

Its already in the latest patch Sam... Version 12.1.9 Build(121)

Thanks

Ajay

0 Kudos

Ajay,

Try using the Post action block and specifying credentials in the action using a credential alias.

Sam

former_member192939
Active Participant
0 Kudos

I have tried with HTML Loader passing credentials. It seems working, only issue is to maintain another user in MII.

Thanks

Ajay.

0 Kudos

I would recommend against the HTML Loader because you have to parse the HTML response...you should be using the Web -> HTTP Post action block with the following configuration:

content-type = text/xml

URL = /XMII/Illuminator?service=SystemInfo&Mode=Status&Content-Type=text/xml

Credential Editor should point to an alias that has local MII permissions

The ReturnAsXML outgoing property will give you the same XML as the XMLQuery template did but it allows you to authenticate your request at runtime even though the transaction is triggered as an unauthenticated request. Either way you would have to maintain a set of credentials for the background task.

- Sam

0 Kudos

Correction to my last post, the URL should be:

URL = server://XMII/Illuminator?service=SystemInfo&Mode=Status&Content-Type=text/xml

and not

URL = /XMII/Illuminator?service=SystemInfo&Mode=Status&Content-Type=text/xml

- Sam

former_member192939
Active Participant
0 Kudos

Thanks Sam ..

It would be great if the issue is fixed in the next service pack.

- Ajay

0 Kudos

Ajay,

If you open a ticket then we can put it in a SP so you don't hit this in the future.

Sam