AS 400 VS XI

[Former Member]

In the olden days, like AS-400 era we have Initiators (The Thread) and also in the Job Control Language we can assign the Priority of that particular job, high or medium or low and that will assign the appropriate que and it will be processed.

But in the modern days like XI I feel they unnecessarily talk about various engines and complicate the stuffs. Still the Ques are not functioning properly even after assigning the High, medium, low(as this is going to help only inside the Integration Engine), then the basis need to work on the number of threads and I belive the recent technologies are not that powerful like AS-400 or IBM Mainframe for sure

[Former Member · Accepted solution]

Pete,

I dont agree with you pete. Even you can prioritize your queues in XI also. Yes I agree with you that we can do that only at integration engine level and not at the adapter level. But still if you want more efficiency I would suggest to have high end hardware and clustering concepts. These would also increase your efficiency.

We cannot compare like the old technolgies with the new ones because you are looking at only one point but there are 'n' number of points in which XI is better than them. I hope you will agree with me.

Regards,

---Satish

[Former Member · Accepted solution]

Would you kindly let me know few points whee XI is better than them (Other than, they can't communicate over the web). Also I know that XI is a middleware and the purpose of XI is totally different compared to the AS-400 or Mainframe.

But what I am trying to say is SAP is unnecessarily talking about all these engines and they are complicating the issues and they are not providing the good service too.

I am not telling that we can't Priorirtize Ques in XI, but its a useless technique thats all I am saying.

[Former Member · Accepted solution]

Hey

>>I am not telling that we can't Priorirtize Ques in XI, but its a useless technique thats all I am saying.

lolz,its not useless Pete,see Prioritizing the queues comes in handy when we have some very important messages to pass and we dont want that to fail.

main advantage of XI over other middleware tools is that it provides excellent central monitoring and adminstration functionality.

see you need to understand that XI is fairly new,its still in its infancy and SAP is taking efforts to groom it,we can't expect it to do magic for us:)

its just my view

Thanx

Ahmad

[Former Member · Accepted solution]

Coming to the Que's Let us say we have two messages Message 1 and message 2.

Message 1 (Low prirority) and Message 2(High Priority).

Message 1 hits the Adapter Engine first and its been processed, and Message 2 stand behind message 1 until message 1 is been released to IE and only in the IE the Priorities really take the meaning and not at the Adapter Engine Level, thats why I said Prioritizing is meaningless.

And how long SAP is going to claim that XI is a Baby???? Even after another 20 years they will say XI is relatively NEW, who know.

[Former Member · Accepted solution]

Hey Pete

yes i agree with you that we cant prioritize the messages at adapter engine level yet,but just coz of few things we cant simply scarp a tool,XI is gradually improving,they had XI 2.0 which had no BPM,all sync scenario were split into two separate async scenario,then came up XI 3.0 which has lots of good stuffs,and they are still releasing SP to make the product better.

i have seen a blog where it has been mentioned that PI7.1 will have the capability to bypas IS ,which means all message mapping and routing will be performed at Adapter engine level.every tool has some hiccups and same holds for XI too.

Thanx

Ahmad

Message was edited by:

Ahmad