The SNS, SNS Administration webpage and SUS is packaged as a single JEE application. The SNS is based on JAX-WS, the METRO web services stack, and JPA for persistency. The SNS Administration webpage and the SUS is based on JSP, Servlets and Javascript. The SNS, SNS Admin webpage and SUS is delivered as a war file to be installed in your JEE application server. 4 war files are delivered: War file Description sns. ...
Figure 44 Reference items - Translation tables Translate blocks are used to convert message values in to SICS values - and require mapping tables to hold both sides of the mapping. These mapping tables are maintained using the translation table function in Reference items. There are two parts to the transformation table - the table definition, and the table contents. First, we consider the definition of the table. Define new table # Figure 45 Translation tables - Define new table ...
Verify SICS API Server startup using the SICS API Server Management console # SICS API Server comes with a rudimentary management console which can be found at: http://<Tomcat-installation:port>/SicsServer/SicsServerManagementConsole and looks like this: When SICS API Server is ready to process SOAP messages the status will be “Running and ready since date/time and the flag will be green: Figure 9 - SICS API Server Management Console Green Status Verify SICS API Server startup by inspecting the log files # SICS API Server writes important startup messages to the SicsServer. ...
Command Line Parameters # SICS Command Line Parameters # NOTE: This information does not apply to SICS API Server. Please see separate installation documentation for SICS API Server. This appendix describes the command line parameters that can be specified in the shortcut that starts the SICS system. SICS command lines follow this template with 6 elements: <Path to JRE><JRE arguments><Main class><Target type><Product><SICS application command line arguments> Element Description <Path to JRE> Path to the Java runtime. ...
Registration # Upon startup (after login), the SICS Workstation will find an available TCP/IP port and start listening for incoming Web Service calls on this port. Then, it will register itself with SNS, providing the user’s login name (first level user in case of two-level login), database name, database schema and the user’s OS name. SNS will assign and reply a token, which SICS will remember. Note: If the user is logged in as the table owner (empty schema), then the registration will be done using an empty string for database schema, not Java null / database NULL. ...
SICS Batch Server is a web application running Java and is designed to be run in any Servlet/JSP-Container compatible with Servlet specification 2.5 or higher and JSP Specification 2.0 or higher. See http://en.wikipedia.org/wiki/List_of_Servlet_containers for a list of Java Servlet Containers. The following description shows how to install Tomcat 10.x which is a free and commonly used Java Servlet Container from Apache using Java 21 or higher. This does not imply that we promote Tomcat 10. ...
SICS API Server can process multiple messages concurrently. The SICS API Server management console is extended to show information of the SICS System pool: Figure 22 - SICS API Server Management Console Figure 23 - SICS API Server Management Console Status
The two data values "" (empty string) and null (data missing / not present) are considered different, not equal. The source and target systems should be of the same SICS product type. Comparison of a pure P&C system with a Life or combined system may cause the Configuration Manager to report differences that, although the CM will allow it, should NOT be copied from one system to the other. Generating SQL for category 4 means creating DELETE statements. ...