E-Rec: Candidate Scenarios

[Former Member]

Hello Experts,

We are on EhP5, SP8. SAP ECC and E-Rec 6.0 are on different boxes. We are on third constellation "Front-end and backend are separated and run on different servers. External candidates access the application via the front-end system and internal candidates access the application via the backend system. SAP E-Recruiting uses Web Dynpro ABAP as the interface technology.".

My concern is for "Web Dynpro ABAP as Interface Technology for Internal and External Candidate Scenarios", what all are the requirements for Basis and Security team, we can request to provide? When we say Front end and backend on different system, do we need to request them two different systems? and then RFC connections? Please guide.

Thanks and regards,

SAP E-Rec Guy

[Former Member · Accepted solution]

Hi,

Have you read SAP note 1017866 already?

Kr,

Julien

[Former Member · Accepted solution]

Hello Julien,

Yes, I have referred the note you mentioned. I still have doubts being new to E-Rec. Can you please help?

Regards,

E-Rec Guy

[romanweise · Accepted solution]

Hi,

the frontend-backend-separation is a landscape archtecture for additional system security in which the frontend system acts as a sort of proxy to establish an additional security layer by channeling external system access. The frontend and backend servers are connected via RFC connections. If there is still the issue with the cross system lock (which has to be set up) these RFC connections have to be named lke the logical system name of the servers / clients. The backend system is a trusted system for the frontend system. That way the external candidate only need a password on the frontend system. The access from backend to frontend is only necessary for services resetting external candidate passwords. Here the RFC connection gets the service user and password which is also used for unregistered services.

Frontend and backend installatons should be on separated physical instances for production and between them should be some firewall / network security stuff. Otherwise the landscape architecture would be quite sensless. I stronly recomment that also one system layer before production (whatever it is called test / quality / production preparation) is also set up with the full infratstructure to test all network settings and service permissions in a not production environment.

Kind Regards

Roman 

[Former Member · Accepted solution]

Thanks Roman. I will discuss these requirements with basis/security admin guys.

Regards,

SAP E-Rec Guy