e-recruiting job board integration using xi - nicx job board integration.pdf · e-recruiting job...

© SAP AG 1

©SAP AG 2005

E-Recruiting Job Board Integration using XI

© SAP AG 2

©SAP AG 2005

Overview of Integration ScenarioE-Recruiting System Configuration

Basic XI-side ConfigurationMessage Monitoring

Delivered XI Components

© SAP AG 3

© SAP AG 2006

High Level Process

The existing publication publishing framework that was available in E-Recruiting 3.0 is still available in 6.0. With E-Recruiting 6.0, a new XI scenario is available that publishes using HR-XML. The determination of whether external postings can be withdrawn or not is also new to 6.0.

© SAP AG 4

© SAP AG 2006

System Landscape

E-RecruitingHR-System

XI-Server

JobBoard

Hire Request

Hire Confirmation

Publication

This is an example system landscape. HR and E-Recruiting could be on the same instance if the ERP release is 2004 or higher, and the E-Recruiting version is the same as the ERP version. This simplified landscape doesn’t show firewalls, TREX, etc. Please see E-Recruiting architecture presentation for detailed examples.

© SAP AG 6

© SAP AG 2006

Customer number to be sent to the job board

Choose a Publication Channel to Publish

Each external job board or aggregator must be specified in the “Posting Channels IMG Step.

The Publisher Class refers to a class which has the methods needed to put the reference index information (such as publication ID) into a queue table. The entries in this table will later be picked up by a periodic service and published using XI (see next slides)

© SAP AG 7

© SAP AG 2006

ABAP Publisher Class Linked to Publication Channel

The publisher class listed above is the standard one delivered by SAP. Customers will often need to do their own classes. This can be done as long as the customer classes implement interfaces IF_HRRCF_CONSTANTS and IF_HRRCF_PUBLISHER.

© SAP AG 8

© SAP AG 2006

T77RCF_XI_PUB processed by periodic service

Class CL_HRRCF_PUBLISHER_XI

CL_HRRCF_PUBLISHER_XI or any customer class to publish data must implement these INTERFACES

PUBLISHAdds an entry to publication index table T77RCF_XI_PUB

WITHDRAWAdds an entry to publication index table T77RCF_XI_PUB if withdraw allowed

WITHDRAW_POSSIBLEChecks whether withdraw is possible for the selected channel

The WITHDRAW_POSSIBLE method will usually contain something like a simple case statement that sets the return value of the method to be true or false based on the ID of the posting channel. The return value determines whether the publication channel appears in the dropdown list or not.

© SAP AG 9

© SAP AG 2006

Periodic Service

Must implement Interfaces IF_HRRCF_PERIODICAL SERVICE and IF_HRRCF_CONSTANTS

Method: RUN does the work

Define and activate periodic service

© SAP AG 10

© SAP AG 2006

What Does the RUN Method do?

Get pointers of all posting instances (T77RCF_XI_PUB or customer table), where an XI-message must be sent

Instantiate XI PROXY object

Populate proxy object with publication and posting data

Send data to XI-Server asynchronously

Mark record in pointer-table as published or withdrawn

Reorganize the publication index table

The explicit COMMIT WORK is necessary to really send the message(s) to the XI-Server

P.S. DON’T FORGET THE COMMIT WORK!

Proxy class must reference Class Interface co_hrrcfjob_pos_publ_out (or customer version) –

Proxy class was generated from transaction SPROXY (ABAP proxy generation)

© SAP AG 12

© SAP AG 2006

Customizing XI

Requires Java Web Start, which is part of JS2E 1.4.2 (Status Jan

06)

© SAP AG 13

© SAP AG 2006

Software Component: ERECRUITSoftware Component Version: ERECRUIT 600

Inside-out integration:Maps directly to the E-Recruiting system via proxy object

Software Component: HR-XMLSoftware Component Version: HR-XML 1.0

Outside-in integration:Maps directly to the HR-XML standard

Structures mapped from E-Recruiting Proxy Object to HR-XML using the Mapping Objects within the HR-XML Software Component

Software Components Used

© SAP AG 14

© SAP AG 2006

Reference OutboundInterface

Reference InboundInterface

Reference InterfaceMapping

Integration Scenario

© SAP AG 15

© SAP AG 2006

JobPositionPublicationOut Action

© SAP AG 17

© SAP AG 2006

Basic Steps

Create technical system

Create business system

Create business system service with communication channel

Transfer Integration Scenarios from Integration Repository (Wizard)

Use alternative interface and mapping [optional]

This document will not cover creation of technical systems and business systems as this is a basic requirement of any XI integration.

The communication channel will typically use the HTTP adaptor to send XML to a job board or aggregator. In our example we save the XML as a file and put it in a directory of the XI server.

© SAP AG 18

© SAP AG 2006

Create Business System Service With CommunicationChannel

© SAP AG 19

© SAP AG 2006

Create Business System Service Wizard

© SAP AG 20

© SAP AG 2006

Assign Business System

© SAP AG 21

© SAP AG 2006

Create New Communication Channel

© SAP AG 22

© SAP AG 2006

Transfer Integration Scenarios from Integration Repository

© SAP AG 23

© SAP AG 2006

Transfer Integration Scenarios from Integration Repository (Cont.)

© SAP AG 32

© SAP AG 2006

SAP Exchange Infrastructure – Monitor Web Services

Transaction SXMB_MONI

In the monitoring area of the Exchange Infrastructure errors can be traced via checking the xml files that were defined by doing the configuration.

In the above shown case something is wrong when calling the integration server “X7R”.

Note: if there is no error then typically there is no monitoring in the productive system (unless otherwise configured).

© SAP AG 33

© SAP AG 2006

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Copyright 2006 SAP AG. All Rights Reserved

e-recruiting job board integration using xi - nicx job board integration.pdf · e-recruiting job...

Documents