SICS Automated Document Handling
Installation Overview # The installation of the SICS software is in three stages: Installation of the DBMS. Installation of the SICS System Administration Utility. Installation of each SICS client. This chapter describes only the installation of the software prior to setting up all of the database components. For subsequent configuration details see the relevant “Database Preparation” chapter for your database. In this document it is assumed that the SICS software is installed to the folder: ...
End-User PC # The requirements described here, are valid for an end-user who performs normal online (UI) related tasks and who has SICS installed on his own PC. For centralized operation, please see the section on Remote Desktop Operation. For heavy processing, please see the section on SICS Batch Server. For interfacing via the SOAP/XML-based API, please see the section on SICS API Server. Operating System # These Windows versions are supported (64-bit only): ...
Starting the DSB # The DSB is part of the SICS System Administration Utility. The DSB is located in the ‘Database Setup’ Folder. Initially, the DSB GUI looks like this: There are two ‘alias’ entries in the ‘Data sources’ listbox. The first one represents the database one is logged in to. The second one represents the SICS application / runtime image. Select either data source to populate the ‘Tables’ and ‘Views’ listbox. ...
The following is a list of Web Services which use “List Framework”. This list is not exhaustive and should be considered only as examples. P&C Claims # S.No Name of the Web Service 1 Create New Claim 2 Update Claim 3 Create and Update Claim FGU 4 Create Headline Loss 5 Update Headline Loss 6 Headline Loss: Retrieve Claim List 7 Move Claim from one Claim Program to Another 8 Create Claim program 9 Update Claim Program 10 Create Claim Group 11 Update Claim Group 12 Delete Claim-to-SOC relation Insurable Object # S. ...
If SICS API Server is started in secure mode, all normal Web Services calls must include an authentication token. The caller must obtain this token by sending an initial “login” message to SICS API Server. The Login service # Sample SOAP Request and Response # The SOAP request (input message) for the login service must follow one of these formats (see discussion on OS AUTHENTICATION and <sicsUserId> further down): <SOAP-ENV:Envelope . ...
Communication Using Web Services # The following diagram shows how communication takes place between the external application, SNS and SICS Workstation. On startup, SICS Workstation starts listening for incoming Web Service calls and also registers itself with SNS. The end-user performs an action in an external web application. Assuming this is an action which is meant to open a screen in SICS, the external application will continue with step 3. ...
SICS API Server is delivered as a web application. Web applications are packaged as files with extension .war. The war file is in fact a zipped archive file. The contents may be viewed with a zip application such as WinZip. Any configuration setting done prior to deploying SICS API Server, must therefore be done in the war file. For instance, WinZip allows the user to edit text files from the archive with Notepad or another external editor. ...
This section describes the necessary database preparation that must be completed before any of the SICS software can be executed. Your DBA will be responsible for correctly configuring and creating the SICS database. Database setup # Before any of the SICS tables can be created, you will need to create the files necessary for the storage of the database using the DBMS tools. This will generally involve creating the instance, specifying where the tablespace files will be stored, creating and configuring the database for your specific requirements. ...