Limitations on version of WAS w/ a 4.6C backend?

[Former Member]

What are the limitations using a WAS 6.2 or a 6.4 when connecting to a 4.6C backend? (Other than the differences within the WAS servers themselves). Just trying to determine which route to take:

-> Use ITS standalone

-> Use ITS w/ WAS 6.2

-> Use WAS 6.4

[Former Member]

When developing on the WAS 6.4 system...connected to 4.6C backend...will we limited in development of web functions?

Can we develop BSP applications w/ 4.6C and WAS 6.4?

[Former Member]

Hi Kauhi,

Yes, of course you can. All you need to do is develop business logic on 46C as RFC/BAPI/Web Service and use them with BSP applications as per the requirement.

Regards,

Sanjeev

[Former Member]

Hi Kauhi,

Use WAS 6.40, this is the latest. Only limitation is the webgui service of ITS which you can use for connecting to your 4.6C, webgui service of WAS 6.40 can not be used for connecting to other systems. If it is important to web-enable existing transactions of 4.6C without development effort, ITS webgui is the only choice.

Regards,

Sanjeev

[Former Member]

Yes, you've said it the main limitation is that the 4.6C Basis layer does not support the HTTP protocol -- so the need for a standalone ITS.

Note, if you use the JCO Connector (on the WebAS side) to connect to the 4.6C ABAP stack you can still call BAPIs. In this scenario the WebAS is another tier in your presentation/application layer.