This site exploits technical cookies for improving navigation. No cookies are used for profiling you for commercial purpouses. Clicking the OK button you accept their usage to the end of this site navigation.  Read More
Our Products
Easy administration and fast integration
Jolie Enterprise is the italianasoftware's suite which increases
deployment rapidity and easy management of microservice architectures.
JSAP is the italianaSoftware collection of microservices
which enables SAP Netweaver integration in a microservice environment
Improve your microservice experience!
Jolie Enterprise
Fast microservices administration
It is the suite which allows you for an easy and rapid service deployment. You can see all the APIs provided by the deployed services and you can compose them for creating new services. All the deployed services are continuously monitored and checked. You can log all the activities of your services and check the statistics of their usage.
Jolie Enterprise concepts
Jolie Enterprise is a microservice architecture based framework which allows for the deployment and the management of microservices developed in Jolie. Jolie Enterprise offers the possibility to control all the deployed microservices in an intuitive and very simple way.
1. Microservices
Jolie Enterprise is mainly formed by an architecture of five microservices described below:
Jolie Enterprise Cloud Node (JECN) - it is the microservice container which allows for a controlled deployment of microservices. It provides external functionalities for starting and stopping microservices. Several JECNs can be handled in the same architecture.
Jolie Enterprise Control Panel (JECP) - it is the microservice in in charge of connecting to all the running JECNs and runnning commands over them. It collects all the necessary information about all the microservices (interfaces, deployed ports, basic information). It is equipped with a Web GUI where it is possible to see all the deployed microservices and control them through graphical commands.
ServiceAdmin (JLOG) - it is the microservice able to collect the activity log messages from the running microservices. It is equipped of a web GUI on which it is possible to navigate through the logs and the usage statistics.
AccountManager (JAM) - it is the microservice which manages credential authentication for enabling authenticated accesses to the available Web GUIs.
FileManager (JFM) - it is the microservice which is in charge of storing/retrieving file to/from a database as it is an ordinary file system.
2. Lower architectures
The lower architecture is represented by the connections among the installed JECNs, the JECP and all the deployed services. The lower architecture always underlies the Upper Architecture described at Section 3. It can be formed by several JECNs, where each of them can be deployed in different machines. Here follows some examples of Lower Architectures:
This is a very basic Lower Architecture where both a JECN microservice and the JECP microservice are launched in the same Linux based machine. Five microservices are deployed inside the JECN.
This Lower Architecture is an extension of the previous one where another JECN microservice has been added with four microservices deployed in. It is worth noting that the second JECN has been launched in windows based machine.
This Lower Architecture is more general. Here the JECP is running alone in a dedicated machine and two of the three JECNs are deployed in the Linux base machine whereas the last one is launched in a Windows based machine. In total eighteen microservices are deployed.
These are just some examples, Lower Architectures can be designed and customized depending on the specific needs of the customer.
2. Upper architectures
The upper architecture is represented by the connections among all the microservices installed in each JECNs. It is the actual architecture which carries out the ICT functions and processes. It is completely independent from the Lower Architecture. For the sake of brevity, in the following we report a very basic Upper Architecture. Other examples can be found in the JSAP tehcnical Section reported below.
In this Upper Architecture the AccountManager and the FileManager microservices of Jolie Enterprise are used. Two microservices, uS1 and uS2 has been developed for storing some documents that comes from uS2. uS2 is also equipped with a Web GUI which exploits the AccountManager microservice for authentication and authorization. All the microservices log their activities into the JLOG microservice.
Integration made easy
JSAP is the suite of services which enable you to integrate SAP Netweaver with third party applications. JSAP services can be run in Jolie Enterprise or in stand alone mode for achieving specific tasks. JSAP allows for integrating SAP through IDOC document exchange, RFC calls and Archive Link module.
JSAP concepts
JSAP is a suite of microservices which allows for developing integrated solutions with SAP Netweaver. Each microservices focuses on a specific integration modality in order to provide different ways for achieving system integration with SAP.
1. Microservices
In the following we list the collection of microservices which enables integration solutions towards SAP Netweaver. It is worth noting that all the JSAP microservices can be run in stand alone mode or deployed into Jolie Enterprise. In Section 2 Upper Architectures that exploits JSAP microservices are presented.
RfcClient (JRFC) - it is a microservice which allows for the publication of RFCs defined into the target SAP as operation of the microservice that can be concurrently invoked by another application
RfcServer (JRFS) - it is a programmable microservice able to play the role of a sibling SAP which public RFC to be invoked by the target SAP.
IdocClient (JIDC) - it is a microservice able to send IDOC documents to the target SAP by exploiting a RFC connection. Each IDOC is published as a different operation of the microservice which can be concurrently invoked by another application
IdocServer (JIDS) - it is a programmable microservice able to receive IDOC documents from the target SAP by exploiting a RFC connection.
ArchiveLink Content Server (JARL) - it is a microservice able to receive documents from the target SAP through the ArchiveLink module.
2. Examples
In the following we report some Upper Architectures examples which deal with JSAP microservices.
Document archiving - active flow
In this example we show a simple architecture for storing active documents generated by SAP. Documents are stored in the FileManager microservice. JRFC is used for retrieving meta information related to the documents before archiving them. SAP user can retrieve the documents by exploting a standard ArchiveLink call in the SAP GUI. All the microservices are here connected to the ServiceAdmin for logging the activities. ServiceAdmin and FileManager are microservices released with Jolie Eneterprise.
Document archiving - active and passive flows
In this example both active documents and passive documents are store into a third party archive. Active flow follows the same rule of the example above, the passive flow starts introducing documents with a barcode label into the scanner for digital transformation which are stored within the document archive. In SAP the user registers the meta data of the document and triggers a BTE (Business Transaction Event) which is sent to the JRFS. Then a workflow is triggered in order to retrieve the metadata of the document by using the JRFC and then registering them on the document archive. For the sake of clarity JLOG microservice is not reported into the picture but all the involved microservices are connected to it in order to log all their activities. A commericial solution is available for Arxivar document archive.
Integration with a supply chain collaboration solution
In this example SAP is integrated with a supply chain collaboration solutions by using IDOC documents exchange both from SAP to the third party application and from it to SAP. A custom microservice performs all the necessary workflows for correctly address techinical specifications of the supply chain collaboration solution. For the sake of clarity JLOG microservice is not reported into the picture but all the involved microservices are connected to it in order to log all their activities. A commercial solution is available for Iungo supply chain collaboration solution.