E-Recruiting Standalone Front-end and back end system queries

[Former Member]

Dear All,

Couple of queries on E-Recruiting Standalone Front End and Back End system landscape & configuration :

1) We are on EHP 7 E-RECRUITING 617. Our EREC architecture is E-Rec Front End & Back End. (Front End in DMZ). ERP ECC is connected via ALE to Back end EREC.

Our major concern is due to hardware and time crunch, is it advisable that we want to put a Front End server for EREC with Webdynpro Abap interface with Backend EREC systems only on Quality and production landscape. That is there will not be an EREC DEV Front End server.

>>So is it mandatory to have EREC Devolpment Server Front End for implementing Standalone  Front & Back End model ?

>> Can we skip the Front End EREC development server from landscape ?

2) If EREC is on Front End & Back End model landscape, is Extranet portal ( External facing portal) still mandatory required for accessing EREC services for External candidates ?

Please shed more light on the relevance of Extranet or External facing portal ? Why it is required ? what are the benefits ?

3) What are the functional configurations / scope of functional configuration required as part of Front End & Back End model ?

I have attached the SPRO nodes screenshot..

>>Is there any other spro nodes other than these ones to be configured for Front End model..

>> Is there any specific activities which we have to do in each system independently in Dev, QA, PRD front end systems and back end systems other than items transported.

Urgently need your inputs.

Regards,

Paul.

[romanweise · Accepted solution]

Hi Paul,

in this case I have to disagree with Nicole. Of course a customer may have individual requirements on security but if you decide for erec standalone w/ frontend backend separated you have to have this on all levels of the landscape. You cannot simply skip this for development as this landscape defines certain requirements for implementing enhancement etc. So you would have no proper way to test your developments bevor getting them to QA which will result in a lot of problems. Whenever a customer insisted in this it ended in a lot of tears. As an additional hint. The best implementation approach from my various projects is to do all development and customizing in the backend server as it is quite difficult to differ what has to be done on backend and what on frontend e.g. when it comes to text changes and you have not done this 20 times. Then transport everything to the DEV frontend server for testing in the DEV landscape layer. From there transport to the other levels of the landscape Backend and Frontend. This way youi have much less double work and cordination trouble compared to working parallel in frontend and backend. Last point, please make sure the QA system has the same infrastructure and network setup like production (DMZ etc.). It is not a good idea to start the test of the security settings in production when everything might be exposed to the public because your Initial setting was not perfect .

For question 2 you do not need an external facing portal for e-rec. Actually this was never a requirement. E-Rec brings the full UI for the external candidate with job search, reference code search, application wizard and candidate startpage.

For question 3. There is a requirement for the cross system lock that the rfc Connections between frontend and backend have to be named the same like the Logical System names. As These names have to be unique in a landscape you have different rfc connections in DEV, QA and PRD. So you will have to set the RFC to frontend, the rfc to backend and the cross system lock settings per landscape level. SICF Service activation, creating external aliases and setting service users is done per System as well. And there are the usual activities which are system specific for the backend in general (TREX setup, Workflow setup, Job planning, Number ranges, maintain branches, etc.)

Kind regards

Roman

[Former Member]

Hi Paul

Its not mandatory to have e-rec front end system . in E-rec Front end system maximum there will be not data i.e infotype data will not be saved.  

Ext candi application like register page, Job search page , Search and apply WDA page are used in E-rec Front end  system but ultimately data should be saved in E-rec back end system .

For front end configuration are like assigning special users to service , roles , RFC and Activating services .

Thanks

Sanjay

[NicoleGeischnek]

Hi Paul,

Such infrastructure and security decisions have to be answered within the company. There is no good or bad here:

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

Regards,

Nicole