HCI First Steps Series

HCI First Steps Part 1- Initialising the iFlow Over this series of posts we will use the HANA Cloud Integration (HCI) will show how it is possible to build a very simple process flow to get data from R!" service# process it into an email and send it to your to your gmail account every morning so you can $now what the weather is going to be li$e that day% In order to build the i&low you will need the following' 1. 2. 3. 4.

a tas$ to get the data from a remote server# a tas$ to process the response# a tas$ to deliver the parsed output to a receiver% a receiver is also reuired% In this case the result will be sent as an email message to a mail account# the sub*ect# body and attachment will all be generated by HCI in the i&low%

For the weather data the weather will be obtained openweathermap.org API. This seri!e that ta"es a town or !it# name and ret$rns latest weather %or that town or !it#. !it#. &ore abo$t the API !an be %o$nd on their website http'((openweathermap.org(api % "he A+I seems very inconsistent when reuesting current weather without an A+I $ey% If the service is disabled then a ,-, error will be received% In this case or even without it# you should be able to reuest a free A+I $ey from http'((openweathermap.org(appid)get where the id can can be appended to the city city name in the /A++I012A+I345.% 5.% 4our 4our uery parameters will loo$ l oo$ li$e the following ./A++I012A+I34 following 1walldorf#de/A++I016 1walldorf#de/A++I01667788,,99% 67788,,99%

Lets begin :e begin by assuming you have an HCI tenant and locally installed clipse ;una and the HANA HCI tooling from https'((tool https'((tools.hana.ondema s.hana.ondemand.!om()h!i nd.!om()h!i% "his tooling allows you to connect to the HCI "enant "enant in order to deploy and manage operations and integration flows on that tenant% !tartup clipse# create a new wor$space and connect to your tenant% If not already done so# goto the +references# eR;# !CN username and an d password% "est "est the connections and clic$ O3% clipse and the HCI "ooling "ooling are now connected to the HCI server%

Ne
It is important to choose an Integration +ro*ect and not an Integration &low% "he pro*ect will be created with a default i&low that will then be customi?ed% Clic$ the @Ne
"he pro*ect will be called @:eatherReport= and it be @Integration &low= pro*ect with a node type of @I&;A+=% It is important to ensure the Node "ype is @I&;A+= rather than I&;% Clic$ @Ne
&or this pro*ect a +ointBtoB+oint i&low will be created and put into the integration flow folder in the pro*ect% Now is a good time to clic$ @&inish= and have the pro*ect generate artifacts into the wor$space

!ince the i&low that was created by b y default is not what we reuire# delete the components so that a blan$ +rocess Integration bo< is left% "his stage is to test that the empty :eather Report integration can be deployed successfully% "his will verify that pro*ect is correctly configured and the i&low can be deployed and e
!ave the i&low and then right right clic$ outside the Integration &low bo< and choose the @0eploy Integration= option from the conte
Clic$ @O3= and the empty i&low will be deployed%%%

As suggested# change to the @Integration Operations= perspective perspective and double clic$ on the node with the tenant name in the tree on the right% "his will open a new view with the operations status for the tenant%

!elect the .0eployed Artifacts. tab and verify that the i&low has indeed been deployed% If there are any errors then refresh the @"as$s @"as$s iew= view and e
HCI First Steps Part 2- Creating the iFlow In HCI First Steps Part 1- Initialising the iFlow the :eather Report pro*ect was was created in clipse with an empty i&low% i&low% Components will now be added to the the i&low to perform the processing processing and data manipulation%

"here are three ma*or components to the i&low% "he first is the tas$ to retrieve the current weather weather in D; from an e
Ne
"here are no options to configure in the service call since authentication is not being used% However a receiver component is reuired to be able to receive data into the message flow%

"he receiver is the abstract message source that wil l be a source for messages% "o configure how the messages will be received reuires a channel%

Clic$ on the Connectors pane and choose @essage &low=% Clic$ over the @ReuestBReply= component and then the @Receiver component to *oin the two together% "his creates a new channel# however the channel still needs to be configured%

Note the direction of the arrow attached to the receiver component% "his indicates the direction the reuest will be made%

nsuring the channel is selected by ma$ing sure orange chec$ bo
It is important to remember that this is the only way to confgure the channnel. Clicking on the "Channels" tab can have unpredictable results.

"his will display the the panel to configure the selected channel% !elect the adapter type of H""+ by clic$ing on the @Erowse= button% "his will enable the @Adapter !pecific= configuration panel with the correct options enabled and displayed% 0epending on the adapter type chosen# different options will be displayed%

Here the *+, o% the weather seri!e is entered that ishttp'((api.openweathermap.org(data(2.(weather is http'((api.openweathermap.org(data(2.(weather "he additional uery parameters allow the type of response# in this case it is D; and the location which is Chippenham in the >3% Of course you could *ust have eaily used walldorf#0 if you were wor$ing at !A+Fs headuarters% "he remaining options are straightforward% "his is an H""+ " call and does not reuire authentication or pro
HCI First Steps Part 3 - $ilding the iFlow !ontin$ed... In the previous installment# HCI First Steps Part 2- Creating the iFlow the i&low was setup so that the i&low could be started and the data retrieved from a remote service% In this e
After the content modifier modifier has processed the message# message# the message will need to be be delivered so at this stage an @nd essage= event will be added to the integration process pr ocess as well%


And of course the destination destination (sender) component and channel will also be reuired to ta$e the final message and deliver it somewhere# *oin them together using a message flow connector%

As before# to configure the channel reuires right clic$ing over the the channel and choosing @Configure Channel= in order to reliably configure the channel definition%

&or the outgoing messages the messages will be sent to the @ail= adapter# that will be using !"+ to deliver the message% As before# once the adapter has been selected# goto the @Adapter !pecific= tab and enter the relevant details%

Here the address of the destination server will wil l be the gmail servers' smtp%gmail%com'9 using !"AR"";! !"A R"";! protocol and both the from and to fields will be set to my personal gmail account% &or now the sub*ect and body fields will not be configured% All that is missing is the the credential name and this will reuire a little detourG% which will be covered covered in the ne
HCI First Steps Part 4 - Con/g$ring the Credentials In the previous installments' HCI First Steps Part 3 - $ilding the iFlow !ontin$ed... the i&low was created and partially configured% "he outbound message now needs to be delivered but this reuired a username and password to be supplied to mail in order that the email can be created on oogleFs servers%

In the previous posting the message destination reuired a user name and password% Normally this process reuires creating and deploying a credential artefact# however in the case of mail this may reuire additional steps that will be documented in the case the oogle account has two factor authentication enabled% "o enable a password to be used with the ail adapter will reuire creating and deploying a Credential Artifact to protect the credentials from being read by anyone e
"his will give a choice of artefacts to deploy% In this case the @>ser Credentials= artifact will be created and deployed to the "enant% "hese "hese will be the credentials will be used to authenticate with the oogle mail servers% Ey using an artifact li$e this the username and password can be protected on the server since they will not be made visible to developers and also the credentials may be independently updated%

Clic$ the @Ne
&or the credentials the oogle username and password are used% If however the oogle account has two factor authentication then an application specific password will need to be created% If "wo "wo &actor Authentication Authentication is not enabled on your oogle Account then your oogle password should be sufficient% If errors are being reported delivering email then follow the steps below to setup an applications specific password% Application specific passwords are important since they will restrict what the application is allowed to do with your account% In this case the password will be restricted to the email application only# so your other oogle properties are not affected% ;og into your oogle account and choose @y Account.

!elect the @!igning in to oogle= lin$ and in the @+assword and signBin method= panel# choose @App passwords.

&rom the list of app passwords# p asswords# choose the @!elect app= and @!elect device= selects at the bottom%

&or the @!elect App= choose @ail and in the @!elect 0evice= choose @Other= then use a descriptive name such as @HCI :eatherReport.

and clic$ the @enerate. button

"he will show a 6J character password in groups of four% "his is the password that will need to be used for the password in the password field% emori?e this password or at least leave it on the screen then swap bac$ to clipse and enter it in the password and password repeat fields% Once the password is entered in the fields of the +assword artifact# clic$ @&inish= and this will deploy the credentials to the tenant%

erify the credentials have been deployed by clic$ing on the .0eployed Artifacts. Artifacts. tab tab and verify the the @HCI :eatherReport Credentials= have been successfully deployed%

0o$ !an !lose 0o$ !lose the password password window window on #o$r oogle oogle a!!o$nt and and logo$t o% oogle oogle now. now. The new appli!ation appli!ation spe!i/! spe!i/! password password wo$ld wo$ld hae been saed. saed.

A tip tip to remember is to clic$ clic$ over the deployed artifact and choose choose the @Copy Artifact Artifact Name= command to copy the artifact to the clipboard% "his wil l ensure the correct name is preserved%

o bac$ to the channel configuration and enter or paste the name of the newly deployed credential name in the @Credential Name= field%

"his completes the configuration of the email channel% "he start# transformation and end of the integration have been defined# now *oin them together with the seuence connector# noting that the @Content odifier= transformation is showing an error since there is nothing yet configured for the transformation%

"he Integration process is now starting to loo$ lo o$ completed% In the ne
HCI First Steps Part  - Completing the iFlow In the previous installment HCI First Steps Part 4 - Con/g$ring the Credentials we are built an integration process and configured receiving the data a nd forwarding the data% "he actual step for performing the processing of the data now needs to be built%

The /rst thing that needs to to be done is is getting rid rid o% the error error on the !ontent !ontent modi/er "o do this the content modifier sin!e this is preenting deplo#ment and testing o% the iFlow. needs to be configured to e
&or this the @weather. element in the @current= root element needs to be e
!ave the i&low and first use the @se the @0eploy Integration Content= command to deploy the i&low to the HCI "enant% "enant%

Eecause i&low i mar$ed as run once# on deployment the i&low will e
ote the header tet the bod# tet and o% !o$rse as epe!ted there is also an atta!hment in the message. "he final configuration step in the i&low is to have this i&low integration process e
Sele!t the 5Start 6ent 25 !omponent and then %rom the properties tab $n!he!" the 5r$n on!e5 !he!"bo and sele!t the 5dail#5 radio b$tton and then sele!t the 5time5 radio b$tton setting the time to 578'775.

Sae the iFlow ee!$te the 5Che!"s5 !ommand to ens$re that the iFlow is !onsistant and then deplo# the iFlow to the HCI tenant. Pat #o$rsel% on the ba!" %or designing !reating and deplo#ing #o$r /rst iFlow hae a sleep and wa"e $p with the weather being deliered to #o$r gmail inbo eer#da#. In the final installment the tracing options will be discussed%

HCI First Steps Part 9 - Identi%#ing iss$es In the previous installment HCI First Steps Part  - Completing the iFlow the integration flow was built# deployed and set to run daily% In the final installment of the series we will be loo$ing at what happens when things go wrong how to find and resolve errors with your i&low%

:e hae now !ompleted the iFlow and deplo#ed it. 6a!h time the iFlow is r$n proiding tra!ing is enabled there will be a log o% ea!h step o% the pro!ess. This tra!e data !an then be integrated into the iFlow so that ea!h step !an be eamined to eri%# the inp$t data and the o$tp$t data to ma"e s$re the data is as epe!ted. "o enable tracing the first step is to reuest tracing be enabled on your tenant% Ey default this is disabled% oto the !A+ Incident Report portal ( https'((s$pport.sap.!om("bre uest using the component .;O0BHCI.% a$ing sure in!idents(in!ident.html) and create a new reuest to have your tenant id to hand and the !B>ser as well% Once the tic$et has been actioned# tracing will

now be enabled for your tenant% "ypically "ypically tracing is disabled as it has an overhead that could impact the data to day performance in high hi gh volume situations% "he first step is to enable the tracing and logging messages in the i&low% Clic$ outside the i&low# on the chec$erboard pattern and the properties tab will now show the configuration settings for the i&low

Clic$ on the Runtime Configuration tab since we want to enable debugging and in the @essage +rocessing ;og= option# select @All vents=% Also chec$ the @nable 0ebug "race= chec$bo<%

Ne
"his is all that is needed to enable the i&low to generate trace and debug information% Redeploy the i&low and switch to the @essage @essage onitoring= tab in the .Integration .Integration Operations @ perspective% perspective% "his view will help assist in seeing how your integration process e
"his highlighted areas show the most important features on this view% "he @Refresh= button on the top right is used to refresh the list of messages from integration flow e
Note how now each seuence flow is annotated with a yellow envelope% e nvelope% "his is the output of the previous step so that ma$es it possible to view each step of the process and the outputs of the process% Clic$ on the envelope and the properties tab will show the message headers and also the message payload% In the e
Of course this shows a deployment that was successful# unfortunately despite our best intentions# sometimes something goes wrong% "o illustrate this# lets create a new step in i n our integration flow that will translate !ON to D;% :hilst the output of the reuest reply is an D; string# the intention is to generate an e
"his will insert the default converter which converts from C! to D;% Right clic$ over the el ement and change the type to !ON to D;%

"he integration flow will now have a new element to transform the response from !ON to D;

0eploy the integration flow as normal and the e
Clic$ on the &ailed line l ine and the @iew "race= button will enable as before% Clic$ this button and the integration flow will now show an error where an e
Clic$ on the error envelope and the properties will now show the e
However in a number of cases a eR; is supplied% "hese are error conditions the i&low should handle%

;ast but not least# sometimes for one reason or another the i&low will deploy deplo y but no run% "o simulate simulate this scenario# deploy the i&low but choose to deploy it to an I&; node rather than an I&;A+ node% Ignore the warning message and continue%

!ince I&; nodes are not supported on trial tenants this will deploy but will not run% >nfortunalty n o messages will be displa#ed in the &essage &onitoring either. To /nd o$t what happened between ;eplo#ment and 6e!$tion open the iew and s!roll thro$gh the tas"s list $ntil the tas" in red is shown.

The big red red ? stands o$t and this is is the deplo#ment deplo#ment that %ailed. %ailed. In the tas" tra!e window s!roll $nder the tas" list thro$gh the tas" deplo#ment tra!e tet to see the error. In this !ase I hae hilighted the error' There is no node o% t#pe IF, to deplo# the integration @ow to. Change the t#pe ba!" to IF,&AP and deplo# the integration @ow. "his concludes the final instalment of the HCI &irst !teps series%

HCI First Steps Part  - Handling errors I% #o$ %ollowed the preio$s t$torial steps the !all to get the weather wo$ld sometimes %ail. The tra!e log wo$ld not show an#thing b$t b# loo"ing at the message monitoring log the %ail$re !an be seen. This is something that needs to be /ed both in the s!enario and in other real world integrations. integrations.

As aboe the error !ode is 471. I% the same reB$est is r$n thro$gh a +6ST !lient then a little bit more in%ormation is reealed. This will sa# that the appli!ation id "e# is missing. :hilst it is triial to / this b# appl#ing %or a %ree "e# at http'((openweathermap.org(appid)get a m$!h better sol$tion is to handle the error in the integration. This is what the topi! o% this post is abo$t. $r eisting integration loo"s li"e the %ollowing'

At a spe!i/ed time the seri!e !alls the open weather API and then etra!ts properties %rom the ?&, $sing ?Path to send and email to a spe!i/ed email address ia &ail. For the remainder o% this post the 6!eption s$bpro!ess will need to be added. The s$b pro!ess will handle an# e!eptions generated b# this iFlow. This is $se%$l sin!e it will be ino"ed when the +eB$est+epl# tas" %ails. Cli!" on the !ommand palette on the right and !hoose the <6!eption S$bPro!ess> S$bPro!ess> element $nder the <thers> se!tion. This s$b pro!ess pro!ess ma# onl# onl# be added to an integration integration so now go ahead and and add the e!eption s$b pro!ess to the integration pro!ess as below.

0o$ will probabl# 0o$ probabl# need to adD$st the la#o$ts as as I hae done to ma"e ma"e the @ow loo" loo" de!ent. It is important to note that the e!eption s$b pro!ess a!t$all# ends with a message end eent. This is the eent that will be etended to send an email to the same message seri!e that the weather report is being sent to. Howeer be%ore the e!eption !an be handled there is some additional pro!essing that needs to be done. To a!!omplish this a pro!ess !all needs to be added to the e!eption s$bpro!ess. This will ta"e the message in the s$b pro!ess and do %$rther pro!essing on it. In this !ase the e!eption will be etra!ted together with the HTTP stat$s and error message.

et !reate a new lo!al integration. This integrationEs role will be to etra!t the HTTP stat$s and error %rom the e!eption and p$t them in a header that !an be $sed b# the !aller.

The new lo!al integratio integration n pro!ess pro!ess is also renamed renamed to <6tra!t6rr <6tra!t6rrorPro orPro!ess> !ess> to des!riptiel# des!ripti el# name the %$n!tion o% this lo!al integration pro!ess. pro!ess. In this pro!ess a new s!ript step will be added to pro!ess the e!eption and etra!t the /elds needed %rom the e!eption. Firstl# a %older !alled 5s!ript5 needs to be !reated $nder the :eather+eport.sr!.main.reso$r!es %older. *sing the FileGew..Gther !ommand epand the <eneral> node and !hoose
Cli!" the b$tton and !hoose the %older 6pand the nodes $nder weather report b# sele!ting then
then and then entering the name %or the %older name in the edit !ontrol

Cli!" and the %older will be !reated

:itho$t the s!ript %older a new s!ript will not be able to be added $sing the s!ript element.

oing ba!" the integration sele!t the element %rom the <&essage Trans%ormers> panel and add it to the 56tra!t6rrorPro!ess5 integration.

+ight !li!" oer the element and !hoose <ew S!ript5

I% #o$ did not !reate the %older in the preio$s step #o$ will be $nable to !reate the s!ript /le and an error will be displa#ed at the top o% the dialog.

Howeer we did !reate the %older so a s!ript !an be now !reated. The s!ript will be named . Cli!" and the
;elete the !ontents o% and repla!e it with the s!ript below. This de%a$lt s!ript had a single method whi!h ta"es a message. This message obDe!t !an be altered a!!ording to the !omments at the top o% the s!ript /le. import !om.sap.gatewa#.ip.!ore.!$stomde.$til.&essage import Daa.$til.Hash&ap de% &essage de% &essage pro!ess;ataJ&essage pro!ess;ataJ&essage messageK L de% map de% map M message.getPr message.getPropertiesJK opertiesJK de% e de% e M map.getJ5Camel6 map.getJ5Camel6!eptionCa$ght5K !eptionCa$ght5K

i% JeNMn$llK L de% bod# de% bod# M message.geto message.getod#JK d#JK message.setod#Je.get+ message.setod #Je.get+esponseod#JK esponseod#JKK K ((Headers message.setHeaderJ5STAT*SC;65 e.getStat$sCodeJKK message.setHeaderJ5STAT*ST6?T5 e.getStat$sTetJKK O ret$rn message O

This s!ript etra!ts the the $ght> element %rom the message message and then etra!ts the stat$s !ode and stat$s tet %rom the e!eption message.

To the message To message the %ollowing %ollowing headers are added added STA STAT*SC;6 and STA STAT*ST6?T both o% whi!h are $se%$l when !reating o$r error message email when an error is thrown. A $se%$l tip is that i% the groo# pl$gins are installed in #o$r e!lipse enironment enironment then right !li!"ing oer the /le in the ProDe!t 6plorer and sele!ting <ther> %rom the <pen :ith> !ommand will displa# a list o% editors o% whi!h one will be the groo# editor.

Cli!" <> and the
Sae the /le and !lose the editor window. Sele!t the node in the <6tra!t6rrorPro!ess> and eri%# that indeed the s!ript asso!iated with this step is the /le.

This !ompletes !ompletes the set$p set$p %or parsing the stat$s !ode !ode and the error message message %rom %rom the e!eption. The message will now !ontain two new header /elds %or the HTTP Stat$s Code and the HTTP Stat$s message. Finall# we are going to send these to the email !hannel in the s$bpro!ess e!eption handler. oto the 6!eption s$bpro!ess !reated earlier and add a new sender !omponent and a !hannel %rom the <6nd 6ent> o% the e!eption S$b-pro!ess to the sender end point.

+ight !li!" oer the Channel and !hoose
Sele!t the email adapter and optionall# add a name and a des!ription %or the general !hannel settings.

Cli!" on the tab and /ll in the al$es identi!all# to the step preio$sl# where the !hannel was !on/g$red to delier the report. Address' smtp.gmail.!om'8 A$thenti!ation' Plain *sername(Password Credential ame' HCI :eather+eport Credentials From' Q#o$r gmail addressR To' T o' Q#o$r gmail gmail addressR addressR S$bDe!t' :eather 6rror' Lheader.ST Lheader.STAT*SC;6O AT*SC;6O Lheader.ST Lh eader.STAT*ST6?TO AT*ST6?TO od#' Jin.tetO

Change ba!" to the <&odel Con/g$ration> and rename the sender !omponent to so the name does not !lash with the eisting sender. Also the 5Pro!ess Call5 needs to be lin"ed to the lo!al integration. Cli!" on the node in the <6!eption S$bpro!ess> blo!" and in the properties !li!" the <rowse> b$tton and !hoose an integration in this !ase it is <6tra!t6rrorPro!ess5

Cli!" <> and sae the !hanges %or the integration Cli!" on the lined drawing board right !li!" and sele!t <6e!$te Che!"s> to ens$re the integration @ow is !orre!tl#. Again right !li!"ing on the drawing drawing board and sele!ting sele!ting <;eplo <;eplo# # Integration Content> will deplo# and ee!$te the integration @ow. I% #o$ hae b$ilt the pa!"age !orre!tl# then a message will be deliered to #o$r inbo showing the error !ode and the error message in the s$bDe!t as was !on/g$red in the email !hannel. The bod# will displa# the tet o% the error re!eied %rom the openweathermap web site.

This !on!l$des !on!l$des how to enable enable error error handling in an an integration integration so errors errors !an be dealt dealt with appropriatel# and integrated into the @ow o% the message pro!essing.

HCI - Pa#load ,ogging $sing roo# S!ripts - Part 1 Eac$ground ;ogging during a message processing is always handy be it for runBtime debugging during development or during during support when you want to understand what happened during the life cycle of a message%

HCI provides default logging options as described in this blog ' HCI First Steps Part 9 - Identi%#ing iss$es % "he tracing options described in this blog are temporary options as the trace is persisted only 6- for inutes% "ry to iew "race post 6- minutes of processing your message and you will get the below error message

"his is obviously not ideal% Are there better options that ensure that the logs are available for consumption post the 6minutes durationP "hose from a +I bac$ground would $now the advantage of using "race statements in their user define functions% "he trace statements enabled you to understand what happened during the processing of your message% Is there something similar in HCIP

4ou can insert logging statements in your roovy !cript and ava !cripts% "he documentation to this is described here##;e/ning S!ripts here "his blog covers a sample using roovy !cripts but it would wor$ similarly in the conte
roovy !cript 
1.

i mp or tc om. s ap. g at e wa y . i p. c or e. c us t omde v . ut i l . Mes s age;

2.

i mp or t j a va. ut i l . Has hMap;

3.

defMessagepr ocessDat a( Messagem me essage){

4.

defbody=mes s age. ge t Body ( j a v a. l ang. St r i ng )asSt r i n g;

.

defmessageLog=messageLogFact or y . get MessageLog( message) ;

9.

i f ( messageLog! =nul l ) {

. 8.

me s s ag eL og . s e t St r i n gPr o pe r t y ( " L og gi n g# 1" ," Pr i n t i n gPa y l o adAsAt t a ch me me nt " )

me s s a ge L og . a d dAt t a c h me me nt As St r i n g( " Re s p on s e Pa y l o ad : " ,body , " t ex t / pl ai n" ) ;

.

}

17.

r et ur n me message;

11. }

"he above script has 8 critical components#

Code de% message,og M message,ogFa!tor#.get&essage,ogJmessageK message,og.setStringPropert#J5,ogging)15 5Printing Pa#load As Atta!hment5K

Usage

et a!!ess to the &essage Pro!essing ,og :rite a String Propert# to the &essage Pro!essing ,og In the message pro!essing ,og the propert# ,ogging)1 is written with the !ontent 5Printing Pa#load Pa#loa d as Atta!hment5 In this !ase we hae hard!oded the 5Printing Pa#load as Atta!hment5 String. 0o$ !an also set this to the &essage Header Propert# and Pa#load as #o$ reB$ire. U*pdate' V$l 2 2719 - Added statement as per re!ommendation %rom Ste%an oller in the !omments se!tionW This se!tionW This method setStringPro setStringPropert# pert# sho$ld be $sed onl# %or short Strings Jone or a %ew

Code

Usage wordsK. For longer str$!t$red do!$ments li"e pa#loads method addAtta!hmentAsString addAtta!hmentAsString sho$ld be $sed. See net row %or this method. :rite :ri te an atta!hment to the &essage Pro!essing ,og

message,og.addAtta!hmentAsStringJ5+esponseP a#load'5 bod# 5tet(plain5K

The inp$t message message pa#load is inserted inserted as an atta!hment into the &essage Pro!essing Pro!essing ,og.

sage in a Integration &low

"his is a simple !OA+ to !OA+ !cenario with the !cript to log the response of the !OA+ call to the essage +rocessing ;og as an attachment% "he !cript listed above is used in a Integration &low a&ter the

'e(uest)'eply step%"he e
"esting of the Integration &low with the roovy !cript Eclipse "rigger your Integration flow# and then proceed to the message processing log in *clipse. Eelow will be seen%

"he ;oggingQ6 contains the "e
"he Attachments contains a Hyper ;in$ with the name of the Attachment as mentioned in our source code% Clic$ing on this hyperlin$# will lead to the actual payload%

WebUI ;i$ewise# when monitoring your flow over the :eb>I# the same info is visible% In fact the :eb>I provides the essage +rocessing ;og and Attachments separately ma$ing it easier to navigate and view the specifics as reuired#

!euence of +rinting of ;ogs

6ng Swee 0eoh had pointed to a very important concept in terms of how the ;ogs are printed% "he documentation lin$ pointed previously has the below info#

ote that the propert properties ies proided b# the s!ript step are displa#ed in alphabeti!al order in the res$lting message pro!essing pro!essing log J&P,K. That means that the seB$en!e o% properties in the &P, does not ne!essaril# re@e!t re@e!t the seB$en!e applied in the s!ript.

:hat this basically means is if your roovy !cript has multiple print settring+roperty! these are not printed in the logs in the same order as they get e
&or e
1.

me s s ag eL og . s e t St r i n gPr o pe r t y ( " DEF" ," Pr i n t i n gPa y l o adAsAt t a ch me me nt 1 " )

2.

me s s ag eL og . s e t St r i n gPr o pe r t y ( " ABC" ," Pr i n t i n gPa y l o adAsAt t a ch me me nt 2 " )

"he message processing ;og will print the output in Alphabetical order instead of the seuence in which it is e
:hen implementing your roovy !cript to use print in the essage +rocessing ;og# it is recommended that you ensure that the !tring +roperties have the 3eyFs as ;ogQ6# ;ogQ7 and so on to that the +rinting happens in the same order as e
&inal Note

;i$e everywhere else# there are performance tradeoffFs between ;ogging multiple payloads and not logging the same and hence this should be used with reuired design considerations% It is recommended that the ,roovy Logging

described in this blog is used in combination with *-ternalied +arameters to enable K disable logging of +ayloads for an Integration &low% 4our 4our e
"he steps to e
roo# S!ripts - Part 2 - *se 6ternaliXed Parameters

HCI - Pa#load ,ogging $sing roo# S!ripts - Part 2 - *se 6ternaliXed Parameters Eac$ground As discussed in my previous blog# HCI - Pa#load ,ogging $sing roo# S!ripts logging of payloads should be used prudently% "ypically "ypically you would li$e the logging to be disabled and have options to enable this only on a need basis%

If you are from a +I bac$ground# you would be well aware of parameters li$e "RAC;;# ;OIN!4NC and Integrated Configuration ;ogging Options that enable you to turn on K off logging / staging when reuired% !o how can this be done in HCI using the roovy scripts we described in the previous blogsP

R;s# &"+ !erver Host#etc which will typically vary in each environment% "here is already content on 
"o be able to define ;ogging 0ynamically we will be using a custom 
Integration &low Changes :e will continue to use the sample Integration &low described in my previous blog with an additional Content

%odifer tep and some changes in the ,roovy script as described below%

tep

/escription

Conten The ew t Content &odi/er %odife step is $sed to

/elta Changes ame M logger J J &essage Propert# to be $sed in the roo# S!ript K T#pe T #pe M 6ternal 6ternal Parameter Parameter ;ata T#pe M Daa.lang.String

tep

/escription

/elta Changes =al$e M externalParamLogger J ame o% the 6ternal Parameter whose al$e wil eternall# K

r

read the 6ternal Parameter into a lo!al propert# propert#..

+ead &essage Properties +ead the al$e o% propert# logger as set in the preio$s !ontent modi/er step I% ,ogger is set to 1 then log the pa#load ,roovy else do not cript per%orm an# Change logging.

1.

i mp or tc om. s ap. g at e wa y . i p. c or e. c us t omde v . ut i l . Mes s age;

2.

i mp or t j av a. ut i l . Has hMap;

3.

defMessagepr ocessDat a( Messagem me essage){

4.

defbody=mes s age. ge t Bod y( j a va . l a ng. St r i ng)asSt r i ng;

.

defmessageLog=messageLogFact or y . get MessageLog( message) ;

9.

d efp r o per t y Ma Ma p=me ss ag e. g et Pr o pe r t i e s( )

.

/ / Readl oggerf r om t heMes s agePr oper t i es

8.

St r i ngl ogg er=pr op er t y Map. Ma g et ( " l ogger " ) ;

.

i f ( l ogger . equal s ( " 1" ) ) {

17.

i f ( messageLog! =nul l ) {

11.

me s s ag eL og . s e t St r i n gPr o pe r t y ( " L og gi n g# 1" ," Pr i n t i n gPa y l o adAsAt t a ch me me nt " )

12.

me s s a ge Lo g. a dd At t a c h me me nt As St r i n g( " Re s p on s e Pa y l o a d: " ,body , " t ex t / pl ai n" ) ;

13. 14.

} }

1. r et ur n me message; 19. }

!etting of 
"est your flow with 
"est your flow with  Confgurations

In the Confgurations +ane that opens# navigate to your pro*ect and double clic$ on the same% In my case the name of my pro*ect is B +r01+ayload$s$ttachment

o to *-ternalied +arameters tab and update the value of e-ternal+aramLogger as 2 and click on ave +arameters

Right Clic$ on your pro*ect in Confgurations 334 /eploy Integration Content. 5our Integration

#low is now updated to have the Logging *nabled6

ReBtrigger the Interface and you should see the logs with the attachment as the ;ogger is now set to alue 6%

&inal Note As seen in this blog# 
Starting with Hana Clo$d IntegrationY eep eep this in mindN Posted b# . =an +ooiD in Pro!ess Integration JPIK Z SA &iddleware on &a# 29 271 11'12'3 A& inShare34

A !o$ple o% months ago I started to wor" with Hana Clo$d Integration. I %ollowed the SAP e-learning HAC17 JHana Clo$d IntegrationK attended a HCI deelopers da# and iewed some webinars. :hen tr#ing to learn all the possibilities possibilities o% HCI I en!o$ntered some [problemsE. :ith this /rst blog I hope I !an help #o$ get get a %resh %resh start with HCI. •

•

•

Che!" o$t the SAP [Starting [Starting with HCIE HCIE page. It !ontains a lot o% $se%$l in%ormation abo$t the te!hniB$e blogs webinars and other eents. 0o$ 0o$ !an enter a trial program program to see what HCI !an do. do. Che!" the details here hereNN ;ownload 6!lipse 6!lipse.. This program will help #o$ to deelop adapters and integration Flows. To aoid weird errors ma"e s$re #o$ download the 7epler ersion. 7epler ersion. This is the ersion SAP s$pports. 6!lipse is $sed %or more than HCI onl# there%or #o$ need to download some additional pl$g-ins. See this this page page %or more in%ormation abo$t installing pl$g-ins in 6!lipse.

•

So #o$ got #o$r JtrialK HCI a!!o$nt and #o$ got the 6!lipse with all the pl$g-ins whatEs netY 0o$ 0o$ need to set $p #o$r #o$r 6!lipse with #o$r #o$r HCI tenant.

Enter your credentials in Eclipse. You should either received an email containing the URL, or use the trial environment. •

•

0o$r 0o$r 6!lipse is is now lin"ed lin"ed to #o$r HCI JtrialK JtrialK a!!o$nt. 0o$ 0o$ !reated a simple simple iFlow and tr# to deplo# this' errorN e%ore #o$ !an start $sing #o$r HCI tenant #o$ need to !reate a "e#store. JIn the trial ersion this is alread# per%ormed b# SAPK In the P;F \Create a "e#store.pd%\ whi!h #o$ !an download here here the !reating o% a new "e#store is eplained.

ow that #o$r iFlow !an be deplo#ed on #o$r HCI tenant #o$ want !reate an iFlow. iFlow. In m# net blog I will show how to !all a web seri!e trans%orm some data and send it ia email. I% #o$ want to !all a web seri!e or S$!!essFa!tors %or eample #o$ need to add !erti/!ates to #o$r "e#store In the [Creating a VA=A VA=A e#store.pd%E thereEs this !hapter !alled [Importing Signed certifcation into keystore’. $t how do #o$ get #o$r S$!!essFa!tors !erti/!ateY

Use ire!o" or #hrome and $ro%se to your Successactors login page. #lick on the lock, and go to the &#onnection’ &#onnection’ ta$. #hoose &#ertifcate in!ormation’.

#hoose 'etails and go !or &#opy to fle’.

(ake the )ase*+encoded -./0 12.#ER3 and save it.

And there #o$ got #o$r S$!!essFa!tors !erti/!ate whi!h #o$ !an import in #o$r "e#store. This wor"s the same %or other !erti/!ates.

•

So now #o$ are able to !reate #o$r iFlow rea!h to di]erent appli!ations and deplo# it to #o$r tenant. $t the iFlow is not wor"ing and #o$ want to tra!e the header and the bod# o% #o$r message. For this #o$ hae to ma"e a reB$est to SAP and as" %or tra!ing rights. 0o$ 0o$ !reate a ti!"et ti!"et here here and p$t #o$r reB$est in !ategor# ,;-HCI. &a"e s$re #o$ proide all the needed in%ormation Jli"e tenant name and S-$serK. A%ter #o$ hae been granted the rights #o$ need to enable tra!ing in #o$r iFlow.

In the properties o! your ilo%, go to (race #onfgurations and choose the trace level you %ant.

In the message monitoring 1dou$le click on your tenant, in the node e"plorer, to get here3 select the ilo% you deployed a!ter setting the trace settings and choose !or &4ie% (race’. Your ilo% %ill no% $e decorated %ith the selected trace level.

I hope that a%ter reading this blog #o$ are able to set $p #o$r HCI tenant with #o$r 6!lipse. I% #o$ hae an# B$estions please do not hesitate to !onta!t me or leae a !omment below. below.

Starting with Hana Clo$d IntegrationY Create a simple integration @ow JiFlowKN Posted b# . =an +ooiD in Pro!ess Integration JPIK Z SA &iddleware on V$n 22 271 8'2'12 A& inShare13

In m# preio$s blog blog I I wrote abo$t the [problemsE I en!o$ntered when starting with HCI. I hope that #o$ !o$ld b#pass those problems and otherwise %o$nd the sol$tion %or itN In this blog I wo$ld li"e to show how to !reate a simple integration @ow iFlow. In this eample I will show #o$ how to get in%ormation o$t o% a S$!!essFa!tors S$!!essFa!tors instan!e how to send this to a p$bli!web p$bli!web seri!e seri!e and how to pro!ess the res$lts. I will show #o$ the !$rrent weather %or a !it# whi!h ÎP !ode we will !olle!t o$t o% S$!!essFa!tors and sent that ia emailN The %ollowing prereB$isite prereB$isite are needed needed and will not not be %$rther dis!$ssed dis!$ssed in this post' post' •

a HCI tenant

•

a "e#store with S$!!essFa!tors !erti/!ate

•

an arti%a!t with S$!!essFa!tors !redentials

•

a "e#store with an email !erti/!ate

•

an arti%a!t with email !redentials

Confguring the sender

(his is %hat %e are going to create. First we !reate a new integration proDe!t in 6!lipse and !on/g$re the sender. I named the sender S$!!essFa!tors and !hoose %or [asi! A$thenti!ationE in properties. The sender !hannel will be !on/g$red li"e this'

(hese are the connection settings !or the Successactors channel. channel. #redential 5ame 2 is the name o! the credentials you deployed earlier to your tenant. ow we are going to set the operation details. Cli!" on &odel perations and /ll o$t #o$r SF !redentials. !redentials. e!a$se we want the ÎP !ode o% a person we sele!t the entit# [*serE and go %or XipCode.

In the demo enironment we are $sing there are a lot o% $sers with a lot o% Xip !odes. :e want to $se onl# one so we are going to set a /lter. I "now the I; o% the $ser I want the Xip !ode %rom is *S+-4 so we !reate a /lter li"e'

That is almost it %or %or !on/g$ring the sender !hannel. :e :e onl# need to /ll in in the S!hed$ler tab. tab. For testing p$rposes I alwa#s !hoose [+$n n!eE.

Create the 8/L fle So now we hae set $p the sender %rom whi!h we will get o$r inp$t. et step is to !reate a :S;, /le %rom the web seri!e. There are seeral wa#s to do that here is what I did. Sear!h the :S;, page %or the seri!e #o$ want to $se Jin this eample'http'((ws%.!d#ne.!om(:eather:S(:eather.asmYwsdl eample' http'((ws%.!d#ne.!om(:eather:S(:eather.asmYwsdl K and sae the page. It will sae the page as 6eather .asm.ml. .asm.ml. 0o$ !an sele!t this /le and drag it to #o$r 6!lipse. &a"e s$re #o$ drop the /le in the map. ow rename the /le to :eather.wsdl and do$ble !li!" the /le to see the o$t!ome. :e are going to $se this /le in the mapping and in the SAP !all later on.

Confgure the mapping ow it is time to add some mapping to o$r iFlow. Create a new message mapping and add it to #o$r @ow. :hen we !on/g$red the sender !hannel the model operation was saed as a /le Jprobabl# something li"e *ser6ntit#B$er#S#n!7.sdK whi!h is also in #o$r reso$r!es.wsdl map. Choose this /le as the so$r!e element. As %or the o$tp$t element #o$ !an sele!t the wsdl /le we !reated earlier and sele!t the global element o% #o$r !hoosing. In this eample we go with etCit#:eather#îp.

A%ter A%ter setting the so$r!e and target go to the ;e/nition tab and map the XipCode we got %rom S$!!essFa!tors to the ÎP the web seri!e reB$ires.

Calling the web service A%ter we managed to get the Xip !ode %orm S$!!essFa!tors and map it to the inp$t the web seri!e demands we !an !all the web seri!e. For that #o$ need to add a seri!e !all to #o$r @ow. @ow.

The +eB$est-+ep +eB$est-+epl# l# bo is is added to #o$r #o$r @ow and %rom %rom here o$t #o$ !an !an add a message @ow @ow to a +e!eier.

To To !on/g$re the !hannel !hannel do$ble !li!" !li!" the message @ow and !hoose SAP SAP as Adapter Adapter T#pe. T#pe.

n the tab [Adapter Spe!i/!E #o$ !an enter the details o% the SAP seri!e #o$ want to !all. The address is the same address %rom earlier in this blog where we downloaded the :S;,. The *+, to :S;, !an be %o$nd b# !li!"ing on [rowseE and sele!ting the :S;, in the reso$r!es.wsdl map.

In this eample we go with etCit#:eather#îp.

Create the converter To To show #o$ how to $se the the !onerter we will will $se a ?&, to CS= CS= !onerter in o$r iFlow. iFlow. Sele!t the !onerter %rom #o$r pallet and drag it to #o$r @ow. +ight mo$se !li!" on the bo and go %or [Swit!h to ?&, to CS= !onerterE.

ow we need to point the !onerter to the in!oming @ow and tell it how to pro!ess the data. o to the properties properties tab o% the !onerter and de/ne the parameters.

end the outcome by mail I% eer#thing is set$p in the !orre!t wa# whi!h we will see in a moment the o$t!ome will be the weather in%ormation o% a !it#. :e want to send this in%ormation ia email. For that we need to !reate a new re!eier and go %or the &ail adapter.

*nder [eneralE #o$ !an !on/g$re #o$r mail settings. In the address /eld #o$ !an /ll in #o$r smtpserer and the Credential ame is the name o% the arti%a!t #o$ deplo#ed earlier. I% #o$ want to hae the data showed in the message bod# #o$ !an enter <Lin.bod#O> in the mail bod#.

I% #o$ want an atta!hment with the data #o$ !an set it $p b# adding the parameters %or an atta!hment.

'un it And now #o$r iFlow sho$ld loo" something li"e this'

;eplo# #o$r Integration Content and wat!h the &essage &onitoring o% #o$r tenant to see i% it deplo#ed !orre!t.

I% instead o% C&P,6T6; #o$ see FAI,6; there is something wrong J#o$ might had /g$red that o$t alread#K. This is a great moment to $se the Tra!e %eat$re Ji% #o$ donEt "now how to a!tiate #o$r tra!ing !he!" m# preio$s bloghere blog hereK. K.

0o$r 0o$r iFlow will will be de!orated de!orated with enelopes. enelopes. These enelopes enelopes !an be sele!ted and and the !ontent !an be seen in the [PropertiesE tab. This is a great wa# to see what !ontent is moed %rom one [boE to another and to see where it goes wrong.

ThatEs allN 0o$ 0o$ now !reated !reated a simple integration integration @ow $sing seeral adapters adapters mappings mappings and !onerters. I hope this blog answered more B$estions than raised. raised. I% not please do not hesitate to !onta!t me or leae a !omment below. ob an +ooiD

log log log log log

1' Starting with Hana Clo$d IntegrationY eep this in mindN 2' Starting with Hana Clo$d IntegrationY Create a simple integration @ow JiFlowKN 3' ;eep die in Hana Clo$d Integration. 4' Hana Clo$d Integration and S$!!essF S$!!essFa!tors a!tors Integration Center ' Hana Clo$d Integration in !omparison to ;ellEs oomi.

;eep die in Hana Clo$d Integration Posted b# . =an +ooiD in Pro!ess Integration JPIK Z SA &iddleware on V$l 21 271 11'13'29 A& inShare24

;eep die in Hana Clo$d Integration. ;onEt be s!ared b# the title o% the blog donEt go awa#' ItEs not #o$ itEs meN It is me who Doined the SAP Hana Clo$d Integration ;eep ;ie training in :alldor% and I want to share some o% the great things I learned there. ] !o$rse D$st li"e m# preio$s blogs J1 J 1 2K I will "eep it B$ite simple. I% #o$ want the %$ll deep diing deal D$st !he!" o$t Pi#$sh a"harEs pro/le pro/le and and "eep an e#e on his training sessions. This time we will !oer en!r#ption and data stores. :hen all goes well #o$r two iFlows will loo" li"e this'

iFlow 1' 6n!r#ption and writing to a data store.

iFlow 2' ;e!r#ption and getting %rom data store.

Preparing Preparing %or en!r#ption e%ore we start with b$ilding o$r iFlow we need to add an +SA "e# pair to o$r "e#store. I% #o$ do not "now how to !reate Jor adD$stK #o$r "e#store please read m# /rst /rst blog blog Jdire!t Jdire!t lin" lin" to the do!$ment [How to !reate a "e#store.pd%EK.

For !reating the +SA "e# pair I also $sed e#Store 6plorer JD$st li"e we $sed %or !reating the "e#storeK. yourkeystore.D"s in e#Store 6plorer JS6K #o$ !an right !li!" on an empt# spa!e and :hen #o$ open yourkeystore !hoose %or [enerate e# PairE.

In the net s!reen #o$ !an !hoose the e# SiXe. For this eample we leae eer#thing as it is.

n the net pop-$p s!reen we !hange nothing and go dire!tl# to the prett# address boo" net to ame.

There we /ll /ll o$t all the in%ormation in%ormation is needed.

Then we get prompted prompted %or an Alias Alias %or o$r "e# "e# pair'

Please name #o$ +SA "e# pair . This name is needed %or a good HCI handling.

ow sae #o$r "e#store and deplo# it to #o$r tenant.

Creating the /rst iFlow ow eer#thing is set $p %or the en!r#ption part we are going to b$ild o$r /rst iFlow. In this iFlow I !hoose S$!!essFa!tors as a Sender. ] !o$rse #o$ !an $se an# "ind o% data %rom an# "ind o% adapter %or this eer!ise. eer!ise. I will not dis!$ss setting $p the sender Jand the re!eierK. re!eierK. I% #o$ do not "now how to set $p a sender or re!eier please read m# preio$s blogs.

I begin with pla!ing a &$lti!ast on the integration proDe!t. 0o$ 0o$ !an /nd this $nder &essage +o$ting in #o$r pallet. e!a$se I want to show #o$ the di]erent o$t!omes with and witho$t en!r#ption en!r#ption I m$lti!ast m# in!oming message J%rom S$!!essFa!torsK two wa#s.

n one o% the bran!hes I add a Content 6n!r#ptor J$nder se!$rit# elementsK. The other bran!h sta#s empt#.

The properties properties o% the PCS6n!r#p PCS6n!r#ptor tor are displa#ed displa#ed below below.. 0o$ 0o$ !an !hange it to #o$r #o$r li"es b$t b$t %or the eer!ise I will onl# assign m# p$bli! "e# alias. *nder 6n!r#ption !hoose add and set in as the P$bli! e# Alias.

ow we added the en!r#ption to o$r SFSF data in one bran!h and nothing in the other bran!h. e!a$se I want to $se the en!r#pted /le %or later b$t also show #o$ the di]erent o$t!omes I will add another m$lti!ast right a%ter the PCS6n!r#ptor blo!".

ow we hae a bran!h we will $se to mail the en!r#pted /le and a bran!h whi!h we !an store in o$r data store. n the end o% the data store bran!h p$t a ;ata Store peration blo!" blo!" whi!h !an be %o$nd $nder &essage Persisten!e. Persisten!e.

In the properties o% the :rite blo!" #o$ !an !hoose a name %or #o$r data store. Also #o$ !an !hange the isibilit#. Please !hange the isibilit# %rom Integration @ow to lobal be!a$se we are going to need in in iFlow2. The option [6n!r#pt Stored &essageE !an be !he!"ed on b$t this is not the en!r#ption we !on/g$red earlier. So i% #o$ !hoose to !he!" this o% #o$r stored message will still be en!r#pted with #o$ own en!r#ption. In this eer!ise I will leae it on.

I !onne!ted both bran!hes to an end eent and !onne!t those to the re!eier. re!eier. For both I !hose the &ail adapter. For the bran!h witho$t en!r#ption I set $p the s$bDe!t with something li"e' SSfle57(E5#RY8(E' and the s$bDe!t on the other bran!h will then be' SSfleE5#RY8(E' .

So now #o$r !omplete iFlow1 sho$ld loo" something li"e this'

:hen we sae and deplo# the iFlow #o$ sho$ld get three di]erent things. ne is an email with the en!r#pted /le the se!ond one is a mail with an $nen!r#pted /le and the third is an entr# in a data store. 0o$ !an !he!" the data store in #o$r tenant $nder ;ata Store =iewer.

The emails sho$ld li"e something something li"e li"e this b$t will be be di]erent based based on #o$r !hosen inp$t. inp$t.

5ot encrypted

Encrypted

Creating the se!ond iFlow

In the se!ond @ow we are not going to $se a Sender shape #o$ !an delete this. Instead o% a sender shape we start this @ow with a Timer Start J$nder eentsK. From the timer start we pla!e a ;ata Store perations and sele!t [Swit!h to et perationE.

:hen #o$ sele!t the et peration #o$ need to enter the ;ata Store ame and the 6ntr# I;. oth !an be %o$nd in the ;ata Store =iewer on #o$r tenant.

A%ter #o$ point the et operation to the right data store and the right entr# in that data store we !reate a m$lti!ast. This is to proe we reall# did de!r#pt the data and where no de!r#ption too" pla!e the /le is still en!r#pted.

n the [to be de!r#ptedE bran!h we add s$rprisingl# a !ontent de!r#ptor. This !an be %o$nd $nder Se!$rit# 6lements.

e!a$se we did not !hange the settings while we were en!r#pting we do not need to !hange an#thing now.

V$st li"e li"e in iFlow1 we will will !onne!t the two bran!hes bran!hes to an endpoint endpoint and !onne!t those ia a mail adapter to the re!eier. re!eier. :hen #o$ sae and deplo# this iFlow2 the res$lt sho$ld be something eB$al to what we saw in the /rst iFlow that means a de!r#pted message J%rom the ot de!r#pted bran!hK and an en!r#pted message J%rom the de!r#pted bran!hK.

I hope #o$ learned something %rom this blog i% not please let me "now. I% #o$ want more detailed in%ormation in%ormation please %eel %ree to !onta!t me and donEt %orget to !he!" o$t Pi#$sh a"harEs pro/le pro/le to to see when the net HCI ;eep ;ie training is near #o$N

log 1' Starting with Hana Clo$d IntegrationY eep this in mindN log 2' Starting with Hana Clo$d IntegrationY Create a simple integration @ow JiFlowKN log 3' ;eep die in Hana Clo$d Integration. log 4' Hana Clo$d Integration and S$!!essF S$!!essFa!tors a!tors Integration Center log ' Hana Clo$d Integration in !omparison to ;ellEs oomi.

Hana Clo$d Integration and S$!!essF S$!!essFa!tors a!tors Integration Center Hana Clo$d Integration and S$!!essFa!tors S$!!essFa!tors Integration Center e!a$se etmoes etmoes the !ompan# I wor" %or is !$rrentl# inoled inoled in a !o$ple o% S$!!essFa!tors S$!!essFa!tors implementation proDe!ts m# e#e w as !a$ght b# the latest release notes %or S$!!essFa!tors. S$!!essFa!tors. In release 178 there will be an Integration Center within S$!!essFa!tors. S$!!essFa!tors. I tho$ght it wo$ld be a good idea to see what "ind o% integration options are aailable in the S$!!essFa!tors S$!!essFa!tors Integration Center and o] !o$rse I want to share m# eperien!e with #o$. The des!ription in the release release notes is as %ollows' %ollows' Integration #enter ena$les 5onI( users to easily $uild, deploy and manage out$ound fle $ased integrations themselves using a !un and intuitive user inter!ace %ithin Successactors 9dmin UI.

I am er# !$rio$s what that %$n inter%a!e means letEs seeN

Setting $p SF IC First o% all #o$ need to a!tiate the S$!!essFa!tors S$!!essFa!tors Integration Center JSF ICK in #o$r proisioning proisioning whi!h is something #o$r S$!!essFa!tors S$!!essFa!tors admin !an do %or #o$ Ja lin" to the o_!ial SAP do!$mentation is at the end o% this blogK. There is no etra li!ense %ee %or the IC it !omes with the S$!!essFa!tors Fo$ndation mod$le. A%ter A%ter the Integration Center is a!tiated in proisioning #o$ !an sele!t it in #o$r admin tools'

The /rst thing #o$ see on the wel!ome wel!ome s!reen are are the tiles with the di]erent di]erent options.

` rowse Integration Catalog ` Create a ew Integration ` 6dit m# integrations ` Import an Integration From a File ` &onitor Integrations I am going to %o!$s on the [Create a ew IntegrationE tile b$t I will !oer the other tiles brie@#.

rowse Integration Catalog This tile brings #o$ to the oerall oerall Clo$d Integration !atalog !atalog.. In here #o$ will /nd prepa!"aged integrations %or S$!!essFa!tors S$!!essFa!tors b$t also %or other appli!ations. :hen I wrote this blog there were seen SF IC @ows aailable b$t IE m g$essing this n$mber will grow oer time.

Create a new Integration The /rst thing when !reating !reating a new integration is to !hoose %rom %rom whi!h entit# #o$ want to etra!t data. :hen sele!ting an entit# it will show a preiew o% the /elds in the entit#. entit#. IEm going %or the entit# \*serE and !hoose sele!t.

A%ter A%ter sele!ting the right entit# we !an see we hae to go thro$gh si steps to !omplete o$r integration. The s$bDe!ts o% the steps and the /elds in the /rst step seem reall# sel%eplanator#.

:hen #o$Ee /lled in the reB$ired /elds and !hoose net it ma# ta"e some time %or the s#stem to gather the in%ormation. :hen the !al!$lation is done the s!reen will gie #o$ a preiew o% the data. Here #o$ !an edit /elds re-arrange them remoe them and add a lot o% /lters and sorting options. 7n a side note: you can save the integration %hile confguring confguring it and I suggest you do. It seems that the standard Successactors Successactors logo;%henidle time can interrupt your creation $e!ore you fnished it.

&a#be this loo"s %amiliar to #o$ as we dis!$ssed this in m# se!ond blog' Starting with Hana Clo$d IntegrationY Create a simple integration @ow JiFlowKN V$st pla# aro$nd with these settings settings and when #o$Ere read# !hoose !hoose net to see a preiew preiew o% what #o$ !reated. I% #o$ li"e what what #o$ see in the preiew preiew !hoose net so we !an !an enter the SFTP settings.

The /elds in this step step are also !lear. !lear. 6nter #o$r SFTP address address enter #o$r !redentials !redentials and !hoose a /le name and pla!e. This is almost ea!tl# the same as the sFTP adapter option in HCI. The net step is to to s!hed$le. 0o$ 0o$ !an !hoose not to S!hed$le the integration integration so #o$ !an r$n it on!e.

The reiew and r$n step is is the /nal step o% the pro!ess. pro!ess. Here #o$ !an !he!" !he!" the !reated integration and r$n it.

*nder the Sae b$tton Jwhi!h I mentioned earlierK there are some more options. 0o$ 0o$ !an eport the Integration de/nition as well as the spe!i/!ations spe!i/!ations #o$ !an download the preiew. preiew. ne other thing that is worth mentioning is the A$dit Histor# ,og. Here #o$ !an iew #o$r preio$sl# saed saed ersions o% #o$r integration. I% #o$ mess $p and "now that ersion 4 o% the integration was wor"ing /ne D$st go on with that oneN

*dit my integrations

Here #o$ !an /nd preio$sl# !reated !reated integrations and edit them.

Import an Integration #rom a #ile

,etEs tr# to import an integration %rom a /le. First we need to go to the !atalog !atalog and and download a integration %or SF IC. I /ltered on s$pported plat%orm JSF ICK and went with the Telephone Telephone and ,o!ation template.

Sele!t the tile and go to the do!$ments tab'

Sele!t the do!$ment !hoose ;ownload and sae it on #o$r dis".

:hen #o$ saed the integration go to the Import an Integration From From a File tile and sele!t #o$r downloaded integration. Choose $pload and #o$ will be in the same s!reen as when we !reated o$r own integration. $t when #o$ sele!t #o$ see that the download integration sele!ted a !o$ple o% /elds whi!h also !ontain the lo!ation and phone n$mbers. 0o$ 0o$ !an easil# add and modi%# /elds /elds or $pload another integration i% that s$ites s$ites #o$r needs.

%onitor Integrations :hen going into the monitor integrations we see a ni!e HCI-:6*I HCI-:6*I loo"ing monitoring. 0o$ !an see the Dobs that hae been triggered %rom the Integration Center Dobs that #o$ s!hed$led and Dobs that hae been triggered %rom ;ell oomi.

:hen #o$ !li!" on a pro!ess name %or eample the one that !as$ed an error #o$ will get detailed in%ormation o% the Dob. I% #o$ entered an in!orre!t sFTP adress #o$ will see the error in there.

For s!hed$led Dobs it is possible to add an email address to re!eie stat$s $pdates a%ter the Dob has /nished. In the S!hed$le S!hed$le tab when #o$ !hoose an o!!$rren!e o!!$rren!e other than [noneE [noneE #o$ get the option to enter an email address. This is onl# an in%ormation in%ormation mail the a!t$al data will be stored stored on #o$r sFTP serer. serer. The title o% the mail will be something li"e' li"e'

And that was all. I hope this blog helped #o$ along with the SF IC i% #o$Ee got an# more B$estions do not hesitate to !onta!t me' bobnetmoes.nl www.netmoes.nl

5ou 5ou can fnd the o9cial o9cial $+ User ,uide &or Integration Integration Center here here..

log 1' Starting with Hana Clo$d IntegrationY eep this in mindN log 2' Starting with Hana Clo$d IntegrationY Create a simple integration @ow JiFlowKN log 3' ;eep die in Hana Clo$d Integration. log 4' Hana Clo$d Integration and S$!!essF S$!!essFa!tors a!tors Integration Center log ' Hana Clo$d Integration in !omparison to ;ellEs oomi.

Hana Cloud Integration in comparison to 0ellUs Eoomi%

In my previous four (1#2#3#4) blogs I tal$ed about i&lows in Hana Cloud Integration% As we all $now HCI is not the only middleware solution that is out there and if you are wor$ing in the integration scene# names as itterEit# ule!oft# Ei?"al$ Ei?"al$ and Eoomi are probably not unfamiliar to you% "hat last one# Eoomi# is specifically for all the !uccess&actors mployee Central users and integration partners% >ntil a month ago# when purchasing an !A+ !&!& enterprise pac$age# the middleware software that came with that pac$age was Eoomi% Now it is also possible to go for a !A+ !&!& enterprise pac$age withG%%HANA C;O>0 IN"RA"ION% IN"RA"ION%

Eecause this option is relatively new# there are still a lot of !&!& customers who are wor$ing with 0ell Eoomi% "herefore I want to compare some options in 0ell Eoomi to Hana Cloud Integration% IUm going to ma$e a simple integration flow in HCI and Eoomi and show you my results% "he i&low will contain an inbound connector (!uccess&actors)# a simple mapping# an D; to C! converter and an outbound connection (email)% Eecause the HCI web >I is not fully developed yet (e%g% there is no possibility to start a new i&low from scratch) IUll be using clipse for the HCI part% &or Eoomi I will be using the web environment (https'((plat%orm.boomi.!om )

Inbound connector

<#I connector and connection

'etails !or the in$ound connector

'etails !or the connection

In HCI# you create an inbound connector and a connection to the start shape% On the connector itself you can ad*ust the authentication details% On the connection you see two sections VConnection detailsU and V+rocessing detailsU% "hese are uite selfBe
)oomi connector and operation

)oomi connector

)oomi operation

As you can see in the pictures# in Eoomi thereUs one place where you enter the aut hentication# the connection details# and the operation details (called process details in HCI)% A big difference between HCI and Eoomi is the way these connectors are saved% In HCI# you create a pro*ect# in which your i&low is stored% In the i&low youUll find the different connectors that have been used% In Eoomi# thereUs one big pro*ect where all your i&lows and connectors are saved% "hat means# for e
apping

"he mapping in Eoomi and HCI are uite similar% ItUs possible to drag a value from your import directly to your desired output# or you can change the data by using different $ind of functions% &or e
(he mapping icon in <#I

7vervie% o! a simple mapping in <#I

Some o! the !unctions that can $e used $et%een your input and output

8arameters !or a (rans!orm'ate !unction in <#I

In Eoomi the mapping loo$s li$e this'

(he mapping icon in )oomi

7vervie% o! a simple mapping in )oomi

9 !unction to modi!y the date date !ormat

8arameters !or 'ate(rans in )oomi

Combine andKor convert

Now we come to the part where Eoomi and HCI show some difference% :hen loo$ing at HCI# we see that the reuested data rows from !uccess&actors are treated as one document% :ithin HCI all records (data rows) will automatically be combined into one document% "his is not the case with Eoomi% very single row (record) is treated as one document# which can c an be sent out individually% Normally# Normally# youUd want to have one file (%csv) containing all the rows (records) so itUs necessary to combine the documents (each containing one data row) to one document% On the other hand# in HCI the data is processed as
(he converter icon in <#I

8arameters !or the -=L to #S4 converter

And in Eoomi# we do not convert but we must combine'

(he data process icon, !rom %here %e can com$ine

8arameters to com$ine documents

Another difference is naming the resulting document% In HCI the document is named in the connector which is being used (e%g% the mail adapter# which we will discuss in the ne
(he icon to set the properties

(he parameters to name the fle.

Outbound connector

"he outbound connector is set up in the same way as the inbound connector% In HCI you need to create a connector and a connection# and in Eoomi you need to create a connector and an operation%

(he mail connector icon and connection >o% in <#I

8arameters !or the #onnection 'etails and the =ail 9ttri$utes in <#I

(he )oomi out$ound connector icon

(he connections details !or email in )oomi

(he operation details in )oomi

:rapBup

:hen you deploy and run these simple i&lows in both systems you get the following result'

Result in <#I

Result in )oomi

As shown# Eoomi ta$es up to more than a minute t o run this flow% It has read JJ documents (read' rows of data) out of !uccess&actors# and has sent one %csv file out% HCI doesnUt display the amount of documents in or out# and only ta$es 6J seconds to complete% Off course this is *ust one simple test# but I thin$ the speed difference is remar$able% "here are two things that I would love to see in HCI in the near future% In Eoomi you have the possibility to @test= the i&low before actually deploying it to your atom% If your i&low reuest to much data it will only ta$e the first 6documents and run the i&low as if it is was deployed% In HCI you have to deploy the whole i&low to your tenant and

run it to see if the changes you have made were successful% "he second thing is the way Eoomi handles multiple accounts% I now have one email address to login and from there I can service all my customers% "his saves me a lot of time and IUm very curious in wat way HCI is going to develop in this matter% "he thing I li$e a lot in HCI is the trace functionality% 4our 4our i&low becomes decorated with envelopes where you can see the data that is going through% In Eoomi the trace function is much more standard and you cannot see directly what data is going through the different steps%

(race !unctionality in <#I

(race !unctionality in )oomi

As e
IUm very curious if you are wor$ing with HCI or Eoomi and what your e
log 1' Starting with Hana Clo$d IntegrationY eep this in mindN log 2' Starting with Hana Clo$d IntegrationY Create a simple integration @ow JiFlowKN log 3' ;eep die in Hana Clo$d Integration log 4' Hana Clo$d Integration and S$!!essFa!tors S$!!essFa!tors Integration Center log ' Hana Clo$d Integration in !omparison to ;ellEs oomi.

HCI First Steps Series

Recommend Documents