AIOps

I would need your support in clarifying the below scenario :

We installed TWS installation for SAP on Linux server ( where SAP central instance < application layer > and SAP database < HANA > ) is combined in single same Linux server. ( Current landscape for TWS V 9.2  )

On cloud – on premise model :

Going forth in cloud, we are planning to split the SAP architecture on Linux server splitted into two i.e SAP central instance < application layer > on linux server ( A ) and SAP database < HANA > in server ( B ). Therefore, our confusion is Do we need to procure TWS licensing for Both server A & B or it is sufficient to procure TWS license for server ( A ) alone, where the SAP central instance < application layer > alone running inorder to run the TWS SAP batch jobs.

Have attached our current R/3 batch SAP architecture in single server at present for reference :

The TWS for SAP license needs to cover the entire SAP estate so you will need licenses for both servers, but as licensing always seems to be changing I would recommend confirming that with your IBM account representative

Hi Pete,
 

Thanks for your prompt response!!

Since the SAP servers are splitting separately for SAP ( central instance ) on server A and SAP ( HANA database ) instance on server ( B ), Do we need to install the IWS for extended agent on server A ( for SAP batch jobs on central instance ) and Do we need to install separate IWS base install on server B for Hana Database  ? , Is that the correct way for the SAP batch jobs to run successfully for SAP ?

Regards,

KK

I believe it depends upon how SAP is configured, but in most cases batch scheduling is performed through the central instance and it will manage which application server actually executes the batch job internally in SAP. If that is your SAP configuration, then you only need an XA (or R3 access method dynamic job) to connect to the central instance

Hi Pete,
 Excellent!!

Now SAP is configured in single Linux server. IWS 9.2 base and IWS X-agent is installed on the same server. IWS X-agent connects the SAP - central instance and execute in the application layer & it is managed by its own internally inside SAP.

We have confusion like if SAP central instance and SAP database < HANA DB > is going to split into two servers. How can we achieve the IWS base and IWS x-agent install on these splitted servers. Do we need to install IWS base and IWS X-agent on Server  ( A ) connecting SAP central instance is sufficient or Do we need to install IWS base & x-agent install for server ( B ) which has SAP hana DB. ?

Regards,

KK

You should only need the XA connecting to the SAP central instance and it will then schedule and execute the jobs internally  in SAP

Hi Pete,

Prompt reply!!

We would consider IWS base 9.3/9.4 with X-agent plugin installed automatically during installation on Linux server which has SAP CI < central instance >. However, we need to purchase IWS base and IWS x-agent license for SAP CI <central instance > installed server alone to run the SAP batch jobs. We can ignore the server B which holds the SAP DB < Hana database >.

Please revert if  I understood correctly.

Regards,

KK

Licensing for the SAP XA is different to the license for IWS base (MDM, FTA, agent, etc.) as the license for the SAP XA is based upon the total size of  the entire SAP estate the XA connects to. Therefore you will need a license for all SAP systems e.g. CI, application server, etc. I don't know if the SAP HANA database is included as part of the entire SAP estate  so you should check with your IBM account representative to clarify if that is necessary

You don't need to install the IWS base (FTA) and XA locally on the SAP CI instance as it uses a remote connection to connect to SAP. So if you don't need the FTA locally on the SAP CI system, you can save yourself some license costs by installing the XA on an existing FTA on another system. You would need to consider availability issues in the event the FTA failed for some reason (e.g. move the XA to another available FTA) or alternatively use dynamic jobs in a POOL that execute the r3batch method and that way you do not have a single point of failure like the FTA/XA combination

Hi Pete,
 

Excellent!! thanks for your kind & prompt reply. It really helps.

We be in touch if there is anything to be discussed in future.

Regards,

KK