Skip to Content

h4. Introduction

In this blog, you can see the procedures to configure the E-Recruitment component in such a way that the external applicants can access the e-recruitment web applications over internet, so that the entire recruiting procedure would be accelerated and your company and external applicants both profit. Using these Web applications, companies can publish job advertisements on the Internet, process online applications and applicants can monitor the processing status of their applications via Internet.

* *

Activities in SAP E-Recruiting – External Candidates

The external candidate is a non-employee or ex-employee of the company. The external candidates perform the following activities.

For performing the above mentioned activities by external candidates, the corresponding web applications should be exposed and the external users should have the *P_RCF_APPL authorization object. For searching for vacancies, the TREX engine with FUZZY search needs to be installed and the documents should be indexed.<br />

*

System Landscape

The ERP system has been separated from the internet users with a firewall and DM zone, so that the external candidates can access the e-recruitment web applications residing on the ERP system only through ISA reverse proxy server. In this way, the direct access to the ERP system can be avoided and can make the system more secure while accessing web applications via internet.

!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_2.gif|height=387|alt=|width=531|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_2.gif|border=0!<br />

Prerequisites

1)  On the ECC system, you should have checked your systems technical settings to ensure that the system would run properly.

2)  System Parameters in E-Recruiting should be maintained properly.

3)  Communication Interface (SMTP mail server and port details) should be configured properly.

4)  User Administration (Creation of User Profiles, Creation of User Groups, and Creation of Special Users – service user with role SAP_RCF_CONTENT_SERVER to enable documents of the document area to be accessed and another service user with user role SAP_RCF_UNREGISTERED_CANDIDATE to enable unregistered user to use the necessary services) should be done properly.

5)  External candidates should have the authorization objects, P_RCF_APPL, P_RCF_STAT, and P_RCF_ACT for performing the above mentioned activities.

6)  Different communication destinations required for E-Recruiting should be  maintained via SPRO.

7)  TREX engine with FUZZY search should be installed and all the post installation steps should be performed (Activating Python Extensions).

8)  ISA Server 2006 should be installed and has to moved to DM zone for reverse proxy configurations.

Steps to be performed

The different steps to be performed are,

1) Connecting TREX with an ABAP Application (RFC Connection)

2) Set up of Search Engine for E-Recruiting

3) Generate URLs for E-Recruiting Web Applications for External Candidates.

4) Configure Reverse Proxy for the Web enablement of E-Recruiting Web Applications

*

1) Connecting TREX with an ABAP Application (RFC Connection)

To configure the search functionality for E-Recruitment, we need to create RFC destinations on the ECC system using TREX Admin Tool. As a rule, ABAP Applications communicate with the TREX Servers by means of the TREX ABAP Client using RFC/SNC protocol. Communication takes place using an instance of the SAP gateway and an RFC Server.

  
1.1 Run TREX Admin Tool <br />

Based on the TREX installation platform, we need to execute either TREXAdmin.bat or TREXAdmin.sh to open the TREX Admin Tool. In our case, installation platform is AIX and the script for TREX Admin can be executed as depicted below. We can see the TREXAdmin.sh file in the following path -:/usr/sap/<System ID>/TRX01/<br />adm user, for eg: If system ID is TP1, then the user id is tp1adm)

 ./TREXAdmin.sh 

 

 

1.2 Create New SAP System Connection

 

 

First step is to create new SAP system connection using TREX Admin Tool. For this, in the TREX Admin Tool, Click on link RFC -> then choose “Create Connection”.

 

You need to mention the ECC system and client details here.  Under logon data, you can see the mentioned user, which is “TREX_ADMIN”. The prerequisite is that, this user should have “*SAP_BC_TREX_ADMIN” *role attached on ECC system. (The user has the necessary authorization for secure use of the TREX Admin Tool in the SAP System).

 

 

1.3 Set SAP System Logon Data

 * *

If you have not mentioned the logon data while creating the SAP System connection, you can edit the details later. For this, Click on RFC-> Edit: Logon Data.<br />

 

!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_6.jpg|height=324|alt=|width=360|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_6.jpg|border=0!<br />h5.

1.4 Create New RFC Destination in SAP System

This step is basically for creating TREXDEFAULT_REG and TREXDEFAULT_START RFC destinations on the SAP System. These two destinations are mandatory for configuring the Search Server Relation (SSR) on the SAP R/3 system. Click RFC-> Create: RFC Destination (sm59).

After saving these entries, you would be able to see the above mentioned destinations in the menu tree for RFC Destinations under TCP/IP Connection on ECC system.

2)  Set Up Search Engine for E-Recruiting

<p> </p>Search Engine for E-Recruiting should be configured properly if you want to use the search functions for candidate data, job posting and so on. For external candidates, they should be able to search for available vacancies and for Recruiter; he/she has to search for candidates from the Talent Pool.

2.1 Set up access to documents

You set up access to the contentserver service of the SAP E-Recruiting system. This enables users to access documents of the document area HR_KW (Document Storage for HR Objects). Attachments, search profiles, and so on, are stored in this document repository.  The communication user RCF_CONTENT with role “SAP_RCF_CONTENT_SERVER” should be created.  

When we execute, it would be redirected to the “Maintain Services” page. There we need to mention the Service Name – CONTENTSERVER and press execute.

We need to mention the name of the created communication user in the details screen of this service. For this double click on the service.

2.2 Create Search Server Relation 

Execute the transaction *SRMO -> Choose “Create SSR” from the Application Menu on the E-Recruitment System. Mention the SSR ID as “SSR_TREX”.</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”><br />!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_13.jpg|height=128|alt=|width=480|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_13.jpg|border=0!</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”>In the following screen, enter the Search Engine as “DRFUZZY” and RFC destination (TCP/IP) as “TREXDEFAULT_REG”. Maintain meaningful description for the same and save the entry.</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”><br />!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_14.jpg|height=271|alt=|width=479|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_14.jpg|border=0!</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”><br />After this, we can see two entries for the created SSR under “RFC Destinations” tab. One for action “I” – indexing and other for action “S” – Searching.</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”><br />!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_15.jpg|height=224|alt=|width=553|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_15.jpg|border=0!</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”><br />Select the entry with action = ‘I*’ and choose Change Destination. Here we have to enter the RFC Destination with activation type ‘start’ into the field ‘New RFC Destination’. Maintain TREXDEFAULT_START as new value, so that the SSR entries created for different actions (I and S) would be using different RFC destinations.

 

2.3 Activate Indexing

 * * You activate the document area HR_KW (Document Storage for HR Objects) to index and classify the documents stored there. Indexing is required to enable the search engine to search the search profiles.

!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_17.jpg|height=329|alt=|width=408|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_17.jpg|border=0!   

Click on “Activate Indexing

 

Mention the created Search Server Relation ID against the document areas “HR_DOC” and “HR_KW”. Check boxes for “Index Release” and “Classify” should be selected to index and classify the documents stored under these document areas.  

2.4 Create Index Category

 

At least one document should be uploaded in the system. For creating Index Category, execute the transaction SKPR07. Here select the document class “HR_DOC” and click on “Clean up Table Entries”.

 

From the results list, return to the transaction. Deselect the limited to selected language indicator and “Choose Re-Index”. Select the created Index category. In the “Defining Indexing Area” group box, set the document area indicator and “Choose Trigger Process”.

 

 

After this, all available data would be transferred to TREX for indexing. Based on the Queue Server settings, the real indexing would be happened.

 

 

3) Generate URLs for E-Recruiting Web Applications for External Candidates

 * *

The links for “Candidate Register”, “Candidate Login”, “Candidate job Search”, “Change password”, and “Password Forgotten” have to be generated for external candidates. This can be done by executing the standard report “RCF_GENERATE_URLS” on the E-Recruitment system. For this, execute transaction SA38 and mention the report name.

 

 

Click on Execute or Press F8.

You can see the generated URLs for different BSP applications in the result page.

 

4) Configure Reverse Proxy for the Web enablement of E-Recruiting Web Applications

For external candidates to register and search for vacancies available in the company, the web applications (BSP Applications) residing on the E-Recruitment system (ECC System) should be made available via internet. For providing additional security to the Intranet ERP system, the ERP system has to be separated from the external users using reverse proxy server configured in the DM zone (neutral zone in between Intranet and External network, which is protected by firewall) of the company, So that, external candidates/users would not have direct access to the E-Recruitment system. Instead of exposing the IP address of E-Recruitment system, we would expose the IP address of reverse proxy server for public access. Then the reverse proxy server would be configured in such a way that all the requests for E-Recruitment applications would come to the standard HTTP port 80 of the reverse proxy server and the reverse proxy would take care of forwarding the requests and (transparently) sending them back as if it was the content server itself. We used, ISA Server 2006 as the reverse proxy server for this purpose. Compared to other reverse proxy servers, ISA Server 2006 has so many additional features and because of these reasons, most of the customers prefer to implement their reverse proxy scenarios on ISA Server series.

Recommended Landscape

In general, ISA Server 2006 should be located in DMZ. The E-Recruitment servers are located in the Intranet. The figure depicts the recommended landscape and a DMZ scenario.

!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_23.jpg|height=291|alt=|width=554|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_23.jpg|border=0!  

<p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”><br /> </p>h5. 4.1 Create Web Publishing Rule

For this, in the ISA Server Management, Right click on “Firewall Policy” and choose “New->Web Site Publishing Rule”. Wizard for creating Web Publishing Rule will be popped up. Web Publishing Rule determines how the incoming requests to the server will be handled.

!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_24.jpg|height=328|alt=|width=560|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_24.jpg|border=0!  

You need to mention the “Rule Action Type”, “Publishing Type”, “Server Connection Security”, “Internal Publishing Details”, “Public Name Details”, “Web Listener Name”, “Client Connection Security”, “Web Listener IP Addresses”, “Authentication Type”, “Authentication Delegation” and “User Sets” within the road map of “Create Web Publishing Rule”, where all the steps are self-explanatory.

<br />Rule Action Type<br /><br />!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_25.gif|height=285|alt=|width=456|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_25.gif|border=0!  

<br />Select Publishing Type<br /><br />

* * 

*Select Connection Security Type

</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”>!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_27.gif|height=265|alt=|width=424|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_27.gif|border=0! ** *

 

Mention the details of Internal Server to be mapped

 

*
Public Name Details** 

**

<strong>!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_29.jpg|height=448|alt=|width=373|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_29.jpg|border=0!</strong> *

<br />Select Listener

 

*!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_30.gif|height=265|alt=|width=424|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_30.gif|border=0! ** ** *

4.2 Publishing all necessary paths

All the E-recruitment related external BSP applications are in the “sap” name space. We can see the service path “*/sap/bc/bsp/” and the name space “sap*” in the URL of all e-recruitment BSP applications. So we have to configure the reverse proxy server in such a way that the external candidates can access only the BSP applications over internet from the E-Recruitment system. In ISA Server, this can be controlled by publishing necessary paths. In order to do this, you have to activate the Paths Tab in the Web Publishing Rule’s properties dialog. Add the entry /sap/ path.</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”>!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_32.png|height=438|alt=|width=392|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_32.png|border=0!</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”> </p><h5 style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”>4.3 Changing the target Port</h5><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”>

 <br />By default, the web server publishing rule redirects the incoming requests to the standard port 80 on the specified target. Based on your requirement you need to change this target port. In our case, all are BSP applications and we need to mention the Web Application Server listening port. For this, in the properties dialog of the Web Publishing Rule, go to the tab “Bridging” and mention the appropriate value there. In our case, Web Application Server is listening on port 8010. </p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”>!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_31.gif|height=265|alt=|width=424|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_31.gif|border=0!</p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”> </p><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”> </p><h5 style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”>4.4 Activate Link Translation</h5><p style=”margin: 0in 0in 0pt; text-align: justify” class=”MsoNormal”>To make sure that no fully-qualified static links may reference internal host names, you need to activate the Link translation functionality. In the Web Publishing Rule’s properties dialog, go to the “Link Translation*” tab. Here you have to check the option “Apply link translation to this rule” and add a new dictionary entry.

 

!https://weblogs.sdn.sap.com/weblogs/images/251857961/9_33.jpg|height=346|alt=|width=553|src=https://weblogs.sdn.sap.com/weblogs/images/251857961/9_33.jpg|border=0!</body>

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Hi,

    That was a very nice blog. It was very useful for me.

    Could you explain me the advantages and disadvantages in using BSP and Web DYnpro for E-Recruitment. We are in the initial stages of implementing E-Recruitment in our organisation. Your answer might help me in taking a goos decision.

    I would appreciate your help.

    Kind Regards,
    Gopal.

    (0) 
    1. Kishor Gopinathan Post author
      Hi Gopal,

      Thank you very much. 🙂

      In general, when we think from the UI perspective, WebDynpro application is the best option. The differences between these two UI technologies have been discussed in this Forum Query – Web Dynpro ABAP v/s BSP

      I believe, from EHP 4 onwards we have WebDynpro ABAP application for external candidates and it is released for limited customers.

      Most probably, SAP may not be supporting the BSP applications in future.. So, It is better to go ahead with WebDynpro ABAP applications !!!!!! 🙂

      Thanks & Regards,
      Kishor Gopinathan

      (0) 
  2. Zarine Ghaboos
    Hi there – your blog has been really interesting to read.

    I’m currently looking at implementing e-Recruiting with a portal front end.  Are you able to advise on how to integrate with the portal? We also require portal to integrate with other applications such as Supplier Self-Service.

    Any help is much appreciated.
    Thanks.

    (0) 
    1. Kishor Gopinathan Post author
      Hi Zarine,

      Thanks for your comment.

      We have mainly 4 e-recruiting roles, which can be integrated with Portal.

      a)Recruiter
      b)Administrator
      c)Approver  and
      d)Business Team

      In older versions, user interfaces for all these roles were using BSP. So we can directly integrate those BSP applications with portal. Based on your scenario, you can either prefer SSO using user id / password or SSO using logon tickets as authentication mechanism.

      With EHP4 for E-Recruiting 6.0, we have new user interface technology – WebDynpro for ABAP. We have completely new UI for the roles Recruiter and Administrator. For handling Recruiter’s work, we have Workcenter application. You only have to integrate these WebDynpro applications with Portal. You need NetWeaver 7.01 components and business packages for Recruiter (version 1.40) and Administrator(version 1.40) to implement EHP4.

      You will get enough informations on the same from SDN and Service Market Place.

      Thanks & Regards,
      Kishor Gopinathan

      (0) 
  3. Sanket Gulati
    This is very helpful indeed. We are about to implement this and I had some solution architecture questions. As per your diagram, only the ISA needs to sit outside the firewall, and the ECC and E-recruit system can be positioned inside. We prefer to keep both on the same system instead of separate. We should be able to keep the combined system behind our firewall without compromising security on the ECC system right? Thanks ..
    (0) 
  4. Hi,

    Great Blog, but in the Prerequisites you indicate the following:

    1)  On the ECC system, you should have checked your systems technical settings to ensure that the system would run properly.

    2)  System Parameters in E-Recruiting should have been maintained properly.

    Please could you give more details on this?

    Regards

    (0) 
  5. Esther Imeh-Ogaga
    Thanks for taking time to explain this step by step.
    We are trying to implement the e-recruiting module, however, we have a front end e-recruiting server in a DM zone and I am trying to configure a name [like a DNS name] so that the port number doesn’t show on the url. Our ISA server is in the intranet. How do you recommend I do this?
    Thank you.
    (0) 
    1. Kishor Gopinathan Post author
      Hi Esther,

      Thanks for your time.

      While setting up the ISA server, you can assign the default port – 80 as the HTTP port. So that it would not be displayed in the URL.

      Thanks & Regards,
      Kishor Gopinathan

      (0) 
  6. Sri M
    Hello Gopinathan,
    Why do we have to use ISA when we have SAP’s WebDispatcher which can act as reverse proxy and can better understand SAP’s back end system changes by pinging message server every 120s.

    We have implemented using SAP Web Dispatcher, SSL(Verisign), Trex, Virus Scanning (it is not in this blog). It works excellent.

    Thanks
    SM.

    (0) 
    1. Kishor Gopinathan Post author
      Hi Charan,

      Nowhere in this blog I have mentioned that you must use ISA only for this. Its upto the customer, if the customer is already using the ISA in their landscape as reverse proxy, its better to have it with this, so that maintenance will be easy.

      When SAP WebDispatcher was developed, it was using only for the load balancing purposes. Latest version of SAP WebDispatcher is providing so many features like-: (SAP WebDispatcher 7.2 onwards) -> Server Selection and Load Balancing (can point to more than one SAP system), Web Caching,SSL etc..

      My intention was to share it with the people in the community, since there were no blogs on ISA at that time.

      Thanks & Regards,
      Kishor Gopinathan

      (0) 

Leave a Reply