Hi,
Since upgrading from 12.0.12 Build(9) to 12.2.5 Build(66), we have an issue with internal calls to XMIIMESSAGELISTENER.
In Link Editor of the http post action block we set 3 parameters:
URL = http://<server>:<port>/XMII/Illuminator?service=WSMessageListener&mode=WSMessageListenerServer&Session=false&IllumLoginName=<user>&IllumLoginPassword=<pwd>&format=xml&NAME=<MessageType>
ContentType = text/xml
PostData = Input XML via Assign Value
This still works fine when called by schedulers which are set up without credentials.
I assume some background user with admin rights is running the scheduler in this case?
When called during development (aka with a user provided with SAP_XMII_Developer and SAP_XMII_Administrator roles), it also works like a charm.
The problem occurs when it's called during a call stack initiated out of a Adobe Flex application (running on the same machine),
initiated by someone with only SAP_XMII_User role.
Our transaction which contains the http post, seems to always run the http call with the credentials of the user who works with the flex application.
This leads to an "Unauthorized to call service WSMessageListener" exception in the NW logs, and obviously no delivery of the message to the MII queue.
On the http post block I already tried using a credential alias from the global credential store
and providing the credentials in LinkEditor (UserName/UserPassword parameters).
Neither having the credentials added to the URL, nor the other two options helped.
The NW log always shows an error for the WSMessageListener call and the user in the log entry is the one working on the Flex application.
Is there any way to force the http call to use different credentials to the user which is running the transaction?
I'd expect using the credential alias in configuration screen should do the trick, but apparently it does not. (Bug?)
Currently I solved this by calling the transaction performing the http post not directly, but with a WebService call.
For the WebService action block, MII seems to use the credentials from the configured credential alias.
Since to my knowledge (please correct me if I'm wrong),
MII ignores changes to the WSDLBaseUrl done dynamically during runtime via LinkEditor mapping,
This means that we have to go into configuration of the WebService call after each deployment of our solution.
Therefore in this case the http post is easier to handle from a configuration point of view (global parameter for the URL).
Also this is not the only transaction where we have issues with credentials on http post.
I couldn't find any related thread, so bare with me if this question is already answered 
regards,
Julian