ISM Admin UI
Last updated
Last updated
All the operational tasks and implementation of flows are performed through Admin UI except custom java class or script implementations. You may not need to implement custom scripts or functions. Most of the business flow implementations can be done inside Admin UI.
· URL : http://ISM_HOST:18080/web
· ID : ism
· Password : fiss
Admin UI has these functions.
· Dashboard
o Provides runtime status of entire services.
o Provides runtime status of entire instances.
· Flow design
o Provides business flow implementation tool.
· Job
o Provides schedule management.
· Transaction result
o Provides the transaction results and the details.
o Provides the summary of transactions ??? daily/hourly.
o Provides the input/output messages of the transactions.
· Interface
o Manages system information.
o Manages data structures.
· Web service
o Provides web service/client generation tool.
o Provides REST API Key management.
· Utility
o Provides some useful functions during operation.
· Admin
o Manages users/access control/housekeeping.
o Provides deployment tool from test/staging to production environment.
These are the menus of Admin UI.
Category | Menu | Description |
Dashboard |
| Shows summary information of service and processes |
Design | Flow | Design and control flows |
Job | Schedule | Manages schedules |
| Sftp | Manages sftp related jobs |
Result | Transaction | Shows the result and the details of the transactions |
| Report | Shows the summary data of the transactions |
| Schedule | Shows the schedule execution results |
| Web Inout | Shows raw input/output message of Web service/REST |
Interface | System | Manages source/target systems |
| Data Structure | Manages data structure |
| Field Group | Manages a single unit of fields |
| Field | Manages fields |
Web Service | Service | Generates web services |
| Client | Generates web service clients |
| API Key (REST) | Generates API Keys for REST call |
Utility | SQL Executor | Query executor for the registered databases |
| File Parser | File parser downloaded from (s)FTP server |
Admin | User | Manages users of Admin UI |
| sFTP User | Manages sFTP users |
| Role | Manages roles of Admin UI |
| Application Group | Manages business groups |
| ACL | Manages Access Control List |
| Runtime Node | Manages runtime instances |
| Import | Deployment tool from test/staging to production |
| Housekeeping | Shows the status of the ISM tables and housekeeping of log tables |
| Parameters | Global parameters for the entire flows |
| Configuration | Global configuration |
| Activities | Shows the list of activities of users |
| Settings | General settings for UI |
These are the menus to visit and the sequence to create a business flow.
· System
o If source or target systems are among database, (s)FTP, SMTP servers, system information should be registered before designing the flow.
· Data structure
o If mapping or predefined request/response is required, data structure should be registered before designing the flow.
· Flow design
o Implement the business logic in the flow.
· Web service
o If the flow will be served as a web service (SOAP), a new web service should be generated and deployed.
o If the flow will be served as a REST service, it is automatically registered with this endpoint.
§ /api/flow_id/flow_version
· Schedule
o If the flow will be executed by scheduler, a new schedule should be registered.
And once the flow is complete and executed, these pages will be visited.
· Transaction result
· Summary
