To the cloud using JANE-Converter
JANE-Converter and the cloud – a dream couple
More and more applications and application areas are being ported to the cloud. The main reasons are, on the one hand, the simple and fast availability of complex services without having to build up additional infrastructure and know-how. On the other hand, ressources can easily be easily turned on or off when usage intensity changes, which adjusts the costs to the demand situation.
But what to do when cloud data has to be made available to other services?
The JANE-Converter uses logic analogous to that used to access ServiceNow to pull data from various cloud providers and make it available in JANE.
This data is used for invoice-control, but also for accounting within the companies.
However, the data provided by cloud providers cannot be accessed directly, because it is not made available in the company itself, but in the cloud.
To do this, it is necessary to access this data from the protected company network over the Internet.
This is done with a range of access methods and security constraints.

JANE-Converter and the Cloud
Metrics in JANE
For this purpose, various metrics have been implemented in JANE-Converter, e.g. over multiple calls of various cloud logics, in order to
- receive one-time passwords
- get invoice information with it
- finally use this invoice information to port the provided invoices from various storage systems (e.g. S3) to JANE.
The results of a converter step get passed on to the next converter step and so on.
The input handler in JANE-Converter
Different JANE-Converter input-handlers enable parsing of the invoices and putting the data into the relational JANE-DWH tables in one work process.
These tables can be evaluated using reports (with deposited role concept, only for selected JANE-users) or they can be read via DB-connection from JANE by other systems.
Among others, the JANE-Converter input-handlers include ‚csv‘, ‚json‘, …..
Conclusion
The access data (credentials) are stored in their own, separately protected table in JANE, the actual accesses only use an access-ID.
If the access information changes, it only needs to be changed in one place.
Actually quite simple, challenge us.