Yes, ignio™ AI.ERPOps has an architecture documentation which can be found here: Eagle | AI.ERPOps 5.0 | Understanding Architecture
In case you do not have access to the attached link, please connect with your Digitate Alliance representative.
Yes, ignio™ AI.ERPOps has an architecture documentation which can be found here: Eagle | AI.ERPOps 5.0 | Understanding Architecture
In case you do not have access to the attached link, please connect with your Digitate Alliance representative.
No, ignio™ AI.ERPOps needs custom SAP add-on to be deployed in customer SAP systems.
Key architecture features used for performance and scalability are:
For each ticket, ignio™ logs some details in the log files. The maximum size of these files is 10MB. After the 10 MB size is reached, the log file is compressed, and a new file is created. (This is a standard product feature and is applicable for all other appliances. In case of any issues in logging, connect with the support team).
Prerequisites expected from the customer are mentioned in the following Confluence links. https://digitate.atlassian.net/wiki/spaces/ID/pages/3776645174/Eagle+AI.ERPOps+5.0+Prerequisites
The following skills are needed to write custom SAP use cases.
Here is the link of ignio AI.ERPOps customization document: Eagle | AI.ERPOps 5.0 | Customization Guides
No additional SAP License is required to integrate ignio with SAP except the named user (system type) license which connects to SAP systems.
SAP has provided a JCO connector free of charge to customers who have an SAP license. Customers need to download and install the JCO connector inside the ignio proxy. This JCO library is used by ignio to connect to SAP systems.
System user (Non-dialog user)
Currently, ignio™ AI.ERPOps delivers .SAR file SAP system wise such as ECC and S/4HANA.
It is the standard recommended minimum sizing for ignio™ AI.ERPOps product. It varies based on the features and workload. Sizing is scalable for increased volume.
Yes, VM Logging must be enabled on ignio™ servers to monitor the application services.
ignio proxy is like a mid server that sits in a datacenter, pulls work from central ignio™, connects to various target systems, and performs actions.
Yes. All the AI.ERPOps APIs are exposed. You can see the data that AI.ERPOps stores.
All AI.ERPOps use cases work on SAP which is hosted on any public or private cloud.
No. Once its stored in ignio’s DB, then only it can be pushed to Shukra. But this development should be done by CS/PS/Customer, not by ERPOps product team.
Yes, multiple SAP users can be used for individual ERPOps capability. Each of these capabilities can have restricted domain specific access.
Yes, ignio is deployed on Digitate’s azure cloud, and its publicly available so that proxy can reach ignio.
This is by design of proxy, which uses these ports to communicate with ignio and do data transfer of various kinds of data like raw data and commands to/from ignio to connect to ITSM and targets within customer DC.