Dear experts,

Is a pleasure to share more experiences after years working in “War Rooms & Real Projects” in hand to hand with other experts (SAP & no-SAP teams) to achieve a decision-making supporting the best ways to implement each business and technical strategies via Cloud or On-premise architectures with solutions involving SAP XI/PI/PO/HCI, TIBCO, BO, Business Connectors, MII, Web Methods, Bonita Soft, MuleSoft, Boomi, Data Stage and others… So after days working with this topic,i share you a main success ideas and a complement with the technical vision that require more hardwork from yourself to achieve each solution proposed (each one, was tested and here is shared)…

Business Vision:

With a little opinion based on real experience aligning the technology with the strategy vision, i can say that:

  • Is not just to decide about the costs of the talent and resources in each company, sometimes there are other untangible factors like the “know how” gained, the high-performance of your workforce, the quality of your solutions, the business strategy aligned to each “integration” paradigm to make the best decision about which technology will add value for each case and not just to save costs, “because” each one of above listed, for example: attack different cases, considering nearest to real-time expectatives, jobs, high volumen vs lower, opportunity areas, standards, etc.,
    It is not just to talk about communication, you have to “integrate your business”, to translate your processes and to obtain the best information for your Business Intelligence paradigm, in order to decide fast, act accuracy & engage opportunities; “before” than your competence…

Process Vision:

I can share some tech and flows needs, that you can apply for your company:

  • Processes: At this level the most important concepts are the interoperability, simplicity and the quality of each architecture; even more than to call each process for its name…
  • Capabilities: SAP HANA Cloud Platform, SAP Fiori launchpad, SAP Web IDE, SAP HANA Cloud Platform…
  • Communication: SAP HANA JDBC, REST Odata (JSON, ATOM), SOAP…
  • FAQ for common interoperability decision-making (these examples are just ideas, will depend of more deeper factors for each company, etc.):
    • Do you still thinking that the problem is located in your technical / functional / final user team (common war)?… but, what about the management, the leadership, the human vision, etc…
    • What is the paradigm that you need?… Point2Point Middlewares (PI), High-volumen (BO DS / TIBCO), BPM (TIBCO / PO), Workflows (TIBCO / BO / PI),
    • Suggesting with SAP PI: if you implement in “artesanal way & with expert tricks avoiding issues”, you will troubleshoot common issues before to implement interfaces, issues that a lot of companies has in its integrations… The tangible results of this comentary will be supported by “real life” including high availability (this vision was proved many times, before to share the idea here) and this try to motivate the importance of design your architecture before to implement in the classical mode (fast, low-cost & test-error)…

Technical vision:

In this new adventure considering that even you can implement it by yourself (without complex scenarios), we are going to use the main concepts like TIBCO Cloud Json Service & SAP HCP – API Management; as a secondary concepts i will share you ideas to implement integrations with SAP HANA DB & SAP Fiori via Web IDE…

About implementation (step by step):

  1. TIBCO Cloud Integration & How to model a first REST API: LINK & via Swagger: LINK
  2. SAP HCP – API Management Service: LINK

Results:

Implementation via API Managemet Service:

1.- TIBCO Project: you can use sample projects, implement the video tutorial or adapt the pet store solution to your new flow (GET /store/Inventory)…

@In this case it is not neccesary to add a route function….

You can test your flow and use the Endpoint to be used in your clients…

2.- HCP – API Management: you can implement without the flow, just configuring the real parameters and following the “deep” proposal of the API Management (be aware to not confuse the API as a hub proposal, for example)…

3.- Execution: From the first invoke of SAP HCP API Management Endpoint was executed the json TIBCO Service (the first call was stable)…

Here is important to mention, that if your SSL Configuration has problems, you can execute it via Swagger.io (just if you implement pet store tibco solution, to follow the same idea): http://petstore.swagger.io/v2/store/inventory


4.- Monitoring: now you can create the application that will be used in SAP WEB IDE…

Interoperability Vision (Other Solutions):

1.- SAP Fiori – WEB IDE: EDMX / JSON: now the big challenge is to get connectivity to JSON services that are implemented in this case with TIBCO in difference with ATOM, so for this reason was just simulated with another “logic trick” to motivate the implementation of this solution with custom edmx file: LINK & then building Fiori custom apps: LINK & And modify Odata: LINK


a) Edit Mock Data: In this case considering Sales Orders Structure more than Business Partner Structure, with this action, will be updated JSON File:

b) SAP Fiori offline execution (you can compare fiori app results with odata online result):

2.- SAP TIBCO SOAP: no you can follow SOAP solution with tibco, with another challenge and is some configuration that is required to be functional on the cloud and not just with localhost configuration:

a) TIBCO Business Studio (you can download it from cloud web site)

b) After your project was deployed successfully in your cloud side:


3.- SAP TIBCO to SAP HANA: it seems there are standard connectors to integrate with SAP HANA, but even the other challenge is to install de sap jdbc driver in this jdbc solutions: LINK

 

Next Steps:

  1. As was mentioned, one of the challenges is to build a json solution that can consume TIBCO and other Services from SAP HCP, that were not implemented for probable ssl limitations (some blogs talk about trial version limitations, but, complicated to confirm in a certain way…
  2. You can implement more logics for example trying to integrate SAP HANA, SAP Fiori Online mode via Destinations, via APIs (was succesfully executed once and after that, the next executions become with 400 bad request error, that require more time to analyse)…

References:

1.- TIBCO Documentation: Link

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply