The format of the SICS database has been designed to be as flexible as possible. Its structure has only been enforced where necessary, allowing for multiple configuration possibilities. The configuration at your site should be determined in advance by your DBA, based on your requirements and the specification of your Database Management System (DBMS).
Note: Terminology in this chapter relates to Oracle. SQL Server does not have the concept of Instances, but the following text still applies.
...
The Java version being used can be determined as follows:
In Help->About SICS, go to System Info. Select the Java tab The properties java.version and java.runtime.version specifies the Java version. The property sun.arch.data.model specifies if the SICS is 64 or 32 bit. Note that this version of SICS requires 64-bit Java 21+.
Overview # The Enviroment API component is as Spring Boot-based REST API service. It provides endpoints to create, update, delete and list the Assure Re environments.
The Enviroment API component stores the environment data. The environment data contains name, description, runtime zip file URL, a unique HASH-value, and other details. Installation # As the Environment API is Spring Boot-based component, it can be run as a normal Java application using the scripts provided in delivery zip-file.
...
Stateless # SICS API Server is designed to operate in a stateless manner. In other words, each SOAP call must contain the data that is necessary for SICS API Server to fully process the SICS business function. Parts of the data may consist of references to data that already exist in the SICS operational database.
Commit / Rollback / Unit of Work # Each SOAP call to the SICS API Server will either succeed 100% or fail completely.
...
The SICS Configuration Manager module is protected by a module key. Start SICS System Administration Utility, open System Parameter Maintenance, switch to the Module Key tab and enter the unlock key for the Configuration Manager.
The SICS Configuration Manager module is also protected by a usecase. Make sure the source user (see Starting the Configuration Manager) is assigned a user role which contains the usecase ‘Configuration Manager’.
Because the SICS Java Launcher works by copying the DXC SICS runtime from a designated folder (call it F), care should be taken when installing a new runtime. The following procedure is recommended:
Install the new runtime in a new folder F2 Rename the ‘old’ runtime folder F to F3 Rename F2 to F Delete or archive F3.
Output patterns # Selecting Output patterns from the menu opens a find window where you can select a single pattern for further processing, create a pattern, or import a pattern from outside SICS.
Figure 8 Output pattern choice
Item Description Name The name given to the output pattern. Active Indicates if the output pattern is active or not. Output type eMessaging Message, External or Tabular. Chosen when the pattern is created.
...
The SBS provides a simple web GUI to administer the SBS instance.
The SBS admin console is available at URL:
http://<hostname>:<port>/<rootcontext>/admin
URL part Description <hostname> The domain name or IP address of the computer where SBS is running. <port> The SBS port, as configured in the JEE container (Tomcat, WebSphere, etc) where SBS is deployed. <rootcontext> The context root where the SicsBatchServer is published, for example, “sbs”. Note:
If admin pages are set up to be protected the user must log in before the management console is opened.
...