cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

EREC E-recruting DMZ landscape

tombo_larsen
Active Participant
0 Likes
215

Hi

We are designing an E-recruiting system, which should be used for external candidates.

We are planning to use the webdynpro interface technology and has decided to split the 'frontend' and 'backend' into two systems - running the 'frontend' WebAS ABAP system in the DMZ.

When having a look of SAP's online documentation

http://help.sap.com/saphelp_rc10/helpdata/en/2c/95c241979ac417e10000000a155106/content.htm

...and will probably go for the technical system landscape at the bottom of this link (above).

Our question: Is the any reason for having a separate reverse proxy/application gateway (like SAP web dispatcher) in front of the 'frontend' system in the DMZ (as indicated in the link) ?

BR

Tom Bo

Accepted Solutions (1)

Accepted Solutions (1)

romanweise
Active Contributor
0 Likes

Hi Tom,

for security reasons and to replace / hide the internal system names from the external view additional security infrastructure is recommended in front of the sap e-recruiting frontend server.

Another good advice. Do not use the last scenario described. Always go for standalone e-recruiting 1 eRec frontend server, 1 eRec backend server and 1 HR core server.

Rgds.

Roman

tombo_larsen
Active Participant
0 Likes

Hi Roman

Thanks for the advices.

Do you have any specific reasons for not recommending the last ("Front-End and Backend on Different Systems (SAP E-Recruiting Integrated with ERP)") solution with the EREC backend in the HR system?

Reasons: Security, flexibility, performance, availability, manageable?

This alternative is attractive from a cost perspective, as one less system (SAP, RDBMS, OS etc) is needed as if the backend should also have its own WebAS ABAP system.

Another alternative with only one extra system for EREC would be the frontend and backend in the same system hidden by an application gateway in the DMZ. This has some advantages

- Only one extra system for the EREC project (per environment of cause)

- Frontend and backend customising/development in same system (in same net as no frontend in the DMZ)

- EREC can be patched/maintained independent of the HR system

- but... Any security issues having the EREC system (frontend+backend) on the same net (not in DMZ) as the HR system?

BR

Tom Bo

BR

Tom Bo

Answers (0)