Isolate app server from external RFC's, idocs

[dan_pfingsten2]

There is a server in our SAP R3 landscape that needs to be isolated both from user logon, external communiction like idocs and also load balancing of batch jobs to this server.

The user logon is no issue, config via SMLG by not including the server in the logon groups.

The external idoc coming in is still an issue to be addressed.

So is the batch job issue. This server requires background processes. But we don't want general batch jobs load balanaced to this server.

If idocs were balanced to that server, potentially they would wait (because of heavy procesing occuring on this server) and could processes to backup.

Can these be eliminated via usage of RZ12? By default a server in the environment will be in that group.

Could the server effectively be isolated by creating some bogus server logon group and assigning the server to it?

So 2 issues:

1. isolate server from idocs

2. isolate server from having batch jobs load balanced to it.

Any thoughts appreciated on this matter of isolating a server from the rest of the landscape so that it can be dedicated to a specific process.

[Former Member · Accepted solution]

You can configure your background jobs groups using SM61 and activate / deactivate as per your requirement. And assign the same background job server name for each background job.

[Former Member · Accepted solution]

Also Disable ICM in Tcode SMICM on that server so not to allow requests from internet.

[dan_pfingsten2]

Batch jobs resolved - sm61 with server group 'SAP_DEFAULT_BTC' , thanks. Note 786412 for this one.

Idocs - RFC of type 3 does not have a logon group set. So SMLG does not appear to come into play here. SMLG is more for the user login.

I'm still wondering if rz12 could be utilized here.

If I understand the question, you're wondering about the need for this scenario?

It's in a case where some dataloads are being done that is very CPU intensive on the SAP application server side (creating sales orders via batch VA01).

So we provided appropriate hardware and dedicated that server specifically to this process. The idea was to segregate any other processing from getting onto this server. If it did, it potentially may experience slowdowns or slowdown the insert process. Either way it would be detrimental.

[Former Member]

Hi Dan,

You can use RZ12 to dynamically change the RFC connections from one App server to another App server, here you will notice by default all the App servers and CI are assigned "parallel_generators" logon group, just remove the App server which you want to isolate from that logon group and save.

Also make sure in SMLG double click on App server and in Attributes tab uncheck EXt.RFC-enabled if is is checked. and save it.

Hope this helps you,

Sanjay

[pr_srinivas]

We understand the issues of you as below.

1. isolate server from idocs (The external idoc coming in is still an issue to be addressed)

- As u already eliminated the target server from SMLG, User login are managed but why external IDOC's are coming.

-

---

View-1) if the IDOC's are coming from other ABAP System, Check the RFC Connections of Source ABAP System to This Target ABAP System, Are they using by any chance LOGON group "SPACE". if yes...pl assign it to a Custom LOGON GROUP of Source which does not include the application server you desire.

View-2) if the IDOC's are coming directly from an external NON-ABAP System, Analyze where the external RFC server is registered..Secondly.....How the Inbound IDOCS are processed by Function Module....Select " TRIGGER BY BACK GROUND PROGRAM" instead "TRIGGER IMMEDIATELY" to build a control thru which BATCH Server the INBOUND IDOCS are processed.

2. isolate server from having batch jobs load balanced to it.

-

---

This you can acheive it as Mr.Sunil Bujade said thru SM61 in this thread.

3. HTTP Logins to thru that application server

-

---

If your ECC System connected to a Portal , and you are experience some WEB logins (IC) login on this application server ,

Do not activate the parameters on the application server where you do not desire HTTP Connections, which will stop HTTP Logins.

icm/server_port_0

icm/host_name_full

login/accept_sso2_ticket

login/create_sso2_ticket

(or)

You should Disable / Deactivate ICM of application server said by Mr.Khaiser in this thread ( I think after every restart ).

If time allows have a look of these Notes.

-

---

SAP Note 0001385751 Deactivating background processing

SAP Note 0000786412 Determining execution server of jobs w/o target server

SAP Note 0001359508 Background server groups: Blank server name in server group

SAP Note 0000519059 FAQ: Background processing system

A Final Question,

-

---

In which scenario, A server is not for GUI LOGINS, not for Specific BATCH Jobs, not for HTTP Logins, is required.. May we request a Technical Scenario was required such application server which may be useful to connect to the requirement when similar demand in our landscape.

Rgds