This blog post is part 2 of a series of blogs on how to develop full-stack To-Do application in SAP Web IDE Full-Stack.

Prerequisites

Before reading this blog please make sure that you have read, understood and implemented part 0 and part 1 of this series.

 

Let’s Get Started!

Create your Java Module

The Java module is responsible for:

  1. OData provisioning of the database module
  2. Custom business logic

In our app we will use it for the OData provisioning.

To create the Java module, follow these steps:

  • In SAP Web IDE, select the todo project folder
  • Right-click it and select New -> Java Module
  • Select OData V4 Service Using SAP Cloud Platform SDK template and then click on Next.
  • Enter service as the module name and click Next.
  • Enter Group ID, artifact ID and package or just use the default values.
    Make sure that Enable SAP HANA Database support checkbox is checked! It’s needed to allow connectivity from the Java service to the HANA database module. Finally, click Finish.
  • SAP Web IDE creates a new service folder under your todo project folder. In addition, the mta.yaml file is updated and now contains the service java module in addition to the db module.
    Specifically notice the ‘provides’ and ‘requires’ sections in the mta.yaml file. The db and java modules both require HANA and provides a service_api which will be used by the UI module (that we will create in part 3 of this series).
  • Next, select the service folder which is located under service > src > main > java >
    {your_package_path} > service
  • Right-click it and select New > Java Class to create a new Java class
  • Enter ToDoService in the Name field, click Next and Finish
  • SAP Web IDE creates the ToDoService.java file in the service folder
  • Open the ToDoService.java file in the code editor
  • Copy the code below and paste it under the first line in the file (under the package {your_package_name} )
    import java.sql.Connection; import java.util.List; import javax.naming.Context; import javax.naming.InitialContext; import javax.sql.DataSource; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import com.sap.cloud.sdk.hana.connectivity.cds.CDSQuery; import com.sap.cloud.sdk.hana.connectivity.cds.CDSSelectQueryBuilder; import com.sap.cloud.sdk.hana.connectivity.cds.CDSSelectQueryResult; import com.sap.cloud.sdk.hana.connectivity.handler.CDSDataSourceHandler; import com.sap.cloud.sdk.hana.connectivity.handler.DataSourceHandlerFactory; import com.sap.cloud.sdk.service.prov.api.EntityData; import com.sap.cloud.sdk.service.prov.api.operations.Query; import com.sap.cloud.sdk.service.prov.api.operations.Read; import com.sap.cloud.sdk.service.prov.api.request.QueryRequest; import com.sap.cloud.sdk.service.prov.api.request.ReadRequest; import com.sap.cloud.sdk.service.prov.api.response.QueryResponse; import com.sap.cloud.sdk.service.prov.api.response.ReadResponse; /** * * @author I059508 */ public class ToDoService { private static Logger logger = LoggerFactory.getLogger(ToDoService.class); @Query(entity = "Task", serviceName = "todo") public QueryResponse findTasks(QueryRequest request) { try { QueryResponse res = QueryResponse.setSuccess().setEntityData(getEntitySet(request)).response(); return res; } catch (Exception e) { return null; } } @Read(entity = "Task", serviceName = "todo") public ReadResponse getProposedBooks(ReadRequest readRequest){ try { ReadResponse readResponse = ReadResponse.setSuccess().setData(readEntity(readRequest)).response(); return readResponse; } catch (Exception e) { return null; } } private List<EntityData> getEntitySet(QueryRequest queryRequest) { String fullQualifiedName = queryRequest.getEntityMetadata().getNamespace() + "." + queryRequest.getEntityMetadata().getName(); CDSDataSourceHandler dsHandler = DataSourceHandlerFactory.getInstance().getCDSHandler(getConnection(), queryRequest.getEntityMetadata().getNamespace()); try { CDSQuery cdsQuery = new CDSSelectQueryBuilder(fullQualifiedName).build(); CDSSelectQueryResult cdsSelectQueryResult = dsHandler.executeQuery(cdsQuery); return cdsSelectQueryResult.getResult(); } catch (Exception e) { logger.error("==> Eexception while fetching query data from CDS: " + e.getMessage()); e.printStackTrace(); } return null; } private EntityData readEntity(ReadRequest readRequest) throws Exception { CDSDataSourceHandler dsHandler = DataSourceHandlerFactory.getInstance().getCDSHandler(getConnection(), readRequest.getEntityMetadata().getNamespace()); EntityData ed = dsHandler.executeRead(readRequest.getEntityMetadata().getName(), readRequest.getKeys(), readRequest.getEntityMetadata().getElementNames()); return ed; } private static Connection getConnection(){ Connection conn = null; Context ctx; try { ctx = new InitialContext(); conn = ((DataSource) ctx.lookup("java:comp/env/jdbc/java-hdi-container")).getConnection(); System.out.println("conn = " + conn); } catch (Exception e) { e.printStackTrace(); } return conn; } }​

     

  • The java code that you just added is doing the following:
    • Connects to the SAP HANA database – see the getConnection() method
    • Uses the @Read and @Query annotations to expose a task and a list of tasks in OData. This is done using the SAP Cloud Java SDK which is added automatically by SAP Web IDE as a Maven dependency in the module (to understand more, review the pom.xml).

      Notice: This java code handles only the Task entity’s ‘query’ and ‘read’ operations.
      Handling the SubTask entity or any other CUD (create, update, delete) operations can be done in the same way (using the same SDK with similar code).

 

  • Now let’s create the EDMX file for our OData V4 service metadata.
    Select the edmx folder (which is located under the resources folder), right-click it and select New > File
  • Enter todo_v4_default.xml as the File Name and click OK
  • Open the new file and paste the following content into it:
    <?xml version='1.0' encoding='UTF-8'?> <edmx:Edmx Version="4.0" xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx"> <edmx:DataServices> <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="todo"> <EntityType Name="Task"> <Key> <PropertyRef Name="id"/> </Key> <Property Name="id" Type="Edm.String" Nullable="false" MaxLength="10"/> <Property Name="title" Type="Edm.String" Nullable="false" MaxLength="100"/> <Property Name="note" Type="Edm.String" MaxLength="250"/> <Property Name="status" Type="Edm.Int16"/> </EntityType> <EntityType Name="SubTask"> <Key> <PropertyRef Name="id"/> </Key> <Property Name="id" Type="Edm.String" Nullable="false" MaxLength="10"/> <Property Name="taskId" Type="Edm.String" Nullable="false" MaxLength="10"/> <Property Name="content" Type="Edm.String" Nullable="false" MaxLength="250"/> <Property Name="status" Type="Edm.Int16"/> </EntityType> <EntityContainer Name="EntityContainer_16ED33654DD94D7FA71D8CBCD0F62216"> <EntitySet Name="Task" EntityType="todo.Task"></EntitySet> <EntitySet Name="SubTask" EntityType="todo.SubTask"></EntitySet> </EntityContainer> </Schema> </edmx:DataServices> </edmx:Edmx>​

    Notice – in the future this file will be automatically generated by SAP Web IDE and so this step will not be required anymore.
    Moreover, the EDMX file must be OData V4 complaint and must contain the same entities, properties and associations that we have in the HDBCDS file that was created in part 1 of this series. For the purpose of this blog it’s sufficient to just copy and paste it into your project.

Build and test your Java module

Now that we created all the relevant resources for our java module, its time to build it.
The build operation will execute a Maven build that will download all the dependencies and check that our java module is runnable.

 

  • Right-click the service folder (which is located under the todo folder) and click Build
  • Logs and info about the build status can be found in SAP Web IDE console (can be opened via the View menu bar).
  • The message Build of /todo/service completed successfully indicates that your project has been built successfully.
  • Now we can run the service!
    Right-click the service folder and select Run > Run Java Application
    (Notice this operation can take several minutes)
  • Finally, SAP Web IDE presents the service URL of your OData service in the Run Console
  • In order to view the content of the OData service, open your browser and enter the URL together with /odata/v4/todo appended to it.
    This should present the OData service document.
  • In order to access to the service metadata add /odata/v4/todo/$metadata
  • In order to access to the list of tasks add /odata/v4/todo/Task

 

That’s it 🙂

In part 3, we will show how to create the UI module that will consume this OData service.
Our app will consume the service and show the lists of tasks in a Master section, and the task details in a Details section.

 

 

 

 

New NetWeaver Information at SAP.com

Very Helpfull

User Rating: Be the first one !