Welcome to the SAP HANA Academy. My name is Bob and in this video series from the SAP HANA Academy
and Digital Partner Engineering we'll be looking at SAP Fieldglass integration .
in this video we'll be looking at both customizing and enabling our connectors .
In the previous video we looked at using the connector setup wizard navigation
in order to answer a series of questions to help us to decide which connector we're going to use.
In this video we're going to be looking at enabling those connectors so once you've answered
a series of questions you'll be given a series of steps to complete to enable that connector .
We'll see at the top that we've set up zero out of the eight required steps
and basically presented all the steps on the left hand side. As it says, even though there's
a wizard you can always go back and change the options that you've selected using this wizard .
Frstly what we need to do is give this connector a name. It will give us
a default name which is active worker single line download. You can also add a description as well .
Additionally you'll notice that next to each of the options you'll have what looks like a light
bulb which means you can get further information on that specific option. If we scroll down then we
can see the version. This is our first version and if i scroll down, in terms of integration, you can
see here are all the options. As you can imagine when you're setting up your connector it depends
on the system that you're connecting to. So i'm going to select here homegrown system as we'll
be connecting with postman. If i then click on the next step all the parameters that are listed
on this part of the wizard will be checked. A simple error here is that you can see that this
connector name is already in use, so we'll have to give it another name. I'll just put an
"SHA" at the beginning beginning of the connector name like so so then we can go to our next step
here we can customize our delimiters and also create notifications for success or
failure during execution. By selecting the light bulb you'll get further information
on each of those parameters. We'll leave the default option. We don't really need to change
whether it's asynchronous or not in terms of the download data format. i'll specify that it's json
or depending on your setup you can specify it as a default and lastly you can choose
when to email your recipients whether the post was successful or on a failure .
if i go to security, you've got some options to do with encryption. We can specify
whether it's sensitive-- i'm saying that it isn't sensitive -- and we can see a note indicating that
the user with the view integration audit trail permission can retrieve this file
from your integration audit trail. We'll look at that later on. We can also choose if we want
to archive the data -- so whether or not the file will be kept on the SAP Fieldglass system -- but
this option applies to upload connectors only. Lastly we can enable the connector to be used
through a user interface. We don't need to change anything here, so we can just click on next step.
This step is where we can configure our fields so we can choose to add custom
fields and as it shows we've set up four out of our eight required items.
These are the fields that will be made available to us. You can see all the fields
here of course, as you can imagine you can combine and you can remove these fields with these options
here now based on the connector type. Some of the things you can do are modify the
properties of the fields, of course you can combine multiple custom fields and pull data into one
combined field. To do this you'll need to select the fields that you want to combine.
For example, if i select first and last name i can combine these custom fields if I want.
You can add and remove native or custom fields and lastly you can change the order of your columns.
The next step is to do with advanced custom features for specific download connectors.
So depending on the destination of where you're downloading your data to,
you might have some specific custom feature. For that specific type of connection this is where
you'll deal with those connection details. The next step describes how to create an endpoint
and subscription( if you're using for example sftp) and how to set up web services transfer methods .
We're going to use SAP Fieldglass SOAP web services as our method and this works fine for us
as we're going to be using postman to upload some data. The next step
is to set up your web service so this is where we configure credentials for web service connectivity.
Here we are presented with a list of licenses and also usernames. You can use most of these
users, but we're going to be using the API user when we set up the post within postman. You can
also choose to create new users here within this list. For now we can exit the wizard and we're
going to look at creating application keys or API application keys. If i go back to the home page
within my integration tools, you'll see that we've got links for create API application key
and view APIi application key. If I click on view API application key here, you can see a
list of those keys. Now when you create these keys, basically you create an application key, a client
id and a client secret. You've also got below a list of your web service license keys and the
users that have been assigned those licenses. i've already got one of those API application keys
which i'm using for this video series but to show you how to build one, if i go back to the home page
and then select create API application key... First, we have to give that application key a name.
i'm going to call mine "job posting demo". There's a mandatory field for the description
and then when we click create, what will happen is we'll get those three pieces of information
which is the application key the client id and the client secret. You'll be using this
application key when you commit a post in postman. Now on this screen you'll also see that there's
an edit button but the only thing you can really do is edit the name, the description,
and the status of this application key. You can disable of course or you can enable it
this is important because you should note that you can't really delete
your API application keys after you've created them. Lastly you'll notice that we don't attach
any of those keys to a specific connector so all the keys can access all the connectors.
Now that we've looked at the steps to create ourselves one of these connectors as well as an application key,
what we're going to be doing in the next video is looking at editing an existing connector.