React to events and connect 3rd Party systems using Serverless services & Open Connectors (Part 4)

Before using the Backend service, we would need to add the required roles. Under Security > Role Collections, create a new role collection.

Select the newly created role collection and click on “Add Role” to add the roles specific to the backend service. I have added both Admin and AllAccess roles.

Once the Role Collection has been updated, navigate to Security >Trust Configuration. This will have SAP ID service as default. Select the SAP ID service and in the email address provide your email address (used to login to SAP CP trial account) and click on “Assign Role Collection” to assign the newly created role collection to your account.

Now that you have provided all the required authorizations, you can navigate to Subscription menu and launch the Backend service. The homepage of the dashboard will provide the statistics of the API usage.

Click on the APIs menu to create your service. Click on the button “Create API”.

For this scenario, I have already created a CDS file with employee model.

context employeeModel {
        entity employees {
		key EmployeeID: String(10);
		EmployeeName: String(255);
		Address: String(255);
		Department: String(10);
	}	
};

service manageEmployees {
	entity employees as projection on employeeModel.employees;
};

In the “Create API” dialog, provide the service name, version and model type. The Model type could be CDS, openAPI and EDMX. For CDS document, I have provided the CDS file mentioned above.

When the service is created, the status would be “Pending” and in few seconds would change to “Active”.

You can always click on the “Deployment Log” icon in the right hand corner to view the status.

Click on the service to view the API details. This system has created a V4 OData service displaying an. Endpoint with operations against the entity.

I can create new employees and also view them using the APIs provided here.

You can also configure the service to generate events for Create/Update/Delete operations. You can configure a callback URL, to which the auto generated events will send data in a JSON format (containing details of the entity/operation)

This concludes the blog series. I hope you found this useful. Please note that Functions & Banckend services are still in beta phase. If you encounter any issues using them, please post them as questions in the forum.