SAP ECC 6.0 on AS/400: Is it possible to link with a Windows AS (AppSrvr)?

[Former Member]

Helo BC Guru's,

I'm came to the same conclusion as .

I'm wondering now whether it is possible to connect a Windows Application Server to a AS/400 DB4 SAP instalation or is that a bit to exotic?

I'm intersted in that not only for the DBCON reason but also because uptil now we only have a central instance and no Application Servers which leads to the situation that the DB server has also to do all IO etc

If this would be possible any suggestions on draw-backs, difficulties to expect etc.

I'm just a developer so sorry if this would be a stupid question.

Thanks

Dirk

[Former Member]

I note is as unanswered solely because we didn't do a POC in the end but we will keep in mind all the remarks and come back to it when we will do so in the future.

[Former Member]

Hi Dirk,

An additional AS server on either Windows or Linux is supported on an AS/400 CI/DB.

But that only off-loads CPU and memory resources from the CI, hardly any IO since most IO is database realted, and that stays on the CI.

Installing a AS with MS-SQL kernel will not connect you to the AS/400 CI !

Kind regards,

Paul Hoogendoorn

[Former Member]

Yes, its possible but I would ask the question why? you said you don't have an application server but do you really need one, is performance slow? it's very common for SAP to be installed as central instance, CI/DB/APP all on one server. if sized correctly it would make no difference. Iseries have the database built into the operationg system so you don't have a sperate db application taking up resources. Also with app server you then have to pass the data over the network.

if you do decide to setup a widnows appserver the be sure to use the XDN database connector from windows to iseries the XDA connector had performance issues. Ihave not used the XDN but there is a previous message post about it.

Jack

[Former Member]

Thanks Jack,

The decision whether we will start a POC for this is still not taken but if we will do it we'll take you're remark in account. I will then also try to add our findings here, so long I'll keep this threat open.

I does happen that the server starts constantly swapping at certain moments. It seems to me that from a certain amount of simultaneous dialog users one would want the user sessions not on the CI anymore.

Dirk

[Former Member]

Hello,

All thanks for the contribution. For now our company has decided to go the more easy way and use a file exchange method (Store Procedure on the MS-SQL side and read file on the R3 side) so I will close this topic (for now).

A last experience why I think using AS's next to the CI is best practice:

Recently a single user managed to occupy almost all our dialog WP's (how this was possible is not yet clear, forking programs?). This resulted in a chain of problems because the other users experience sever performance problems and time outs. So everybody starts to try to log on with the expected results that problem becomes bigger and bigger. Having separate AS's might then reduce such a problem to 1 AS iso all users.

By the way something similar we experience with APO regularly. So far we don't know why or whether this can be avoided but APO launches from time to time multiple paralel processes in R3 all in DIA WP's. also this can cause bottlenecks.

Dirk

[former_member204746]

you are mixing things up.

the topic refers to a CI or APPS on Unix trying to connect to an non SAP external MS-SQL server.

This is not your scenario...

you want to install a new APPS server on Windows to a central instance and database instance running on DB2/AIX.

In this case, you need a SAP-delivered DLL file to connect to DB2. This should work fine becasue DB2 is supported on Windows platform and for SAP systems.

[Former Member]

Hoi Eric,

Tnx for the DLL tip.

In first instance just installing an AS is the idea.

My dream in a later stage is, if this AS is a windows this could then also be intalled with the MS-SQL specific Kernel part, next to the CI base. This could then make it possible to set up DBCON for Native SQL with the MS-SQL server.

But as said, in first place it seems to me common sense to free the DB server from IO tasks. Extra benefits are welcome.

Dirk

[Former Member]

Hallo Dirk,

The installation of an NT application server to access a database instance on an IBM i is a pretty common scenario and there should be no problem wih it. You can find the relevant installation guides in the service marketplace:

service,sap,com/instguides -> SAP Netweaver -> Choose relevant release -> Installation -> IBM DB2 for i5/OS -> Windows

All the best,

Sally Power

Development Support for SAP on IBM i

[Former Member]

Thanks Sally,

will look into it and pass it on to more knowledgable people.

Dirk

[former_member204746]

your central instance is on AS/400.

the topic you refer to has got issues with SQL server because there are no Unix client for SQL server. This is not your case here because SQL server does not work on AS/400.

So, as long as your DB has a client supported by SAP to be run on Windows, you're OK.

[Former Member]

Hello Eric,

Thanks for quick response but:

In first instance I researched the problem for exactly the same issue as in the mentioned thread. Trying to use Native SQL to approach an external MS-SQL server.

If that would be the only reason to try to install a Windows AS I wouldn't bother and use different technique.

The fact that we have currently only the central instance and no AS's however seems not very good to me. Same machine with the DB has also to create web-pages, hold all users GUI's aso.

So in my opnion we should install at least 1 AS. That combined with the other problem makes me wonder whether that AS can be on Windows or has to be on the same OS as the central instance.

I know sounds aq bit exotic such a hybrid environment but on the other hand it might also have it's advantages.

Dirk