/sicsdocs/technical/server/api_server/technical_paper/ Recent content in Technical paper on Hugo -- gohugo.io /sicsdocs/technical/server/api_server/technical_paper/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/introduction/ SICS API Server is a non-mandatory component in the SICS software package. SICS API Server is a “headless” component that implements Web Services to common SICS functions, allowing other applications, components or front-ends to call SICS business processes directly or via a Services-oriented Architecture (SOA) implementation. This document describes the design of SICS API Server. It explains the basic architecture and important properties. For a full description of the supported Web Services, including WSDL/XSD files and sample SOAP messages, please refer to the documentation that is available after installing SICS API Server. /sicsdocs/technical/server/api_server/technical_paper/concepts/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/concepts/ Overall description # SICS API Server provides access to SICS functionality through Web Services. Web Services is an industry accepted standard for application interoperability. SICS API Server enables the use of SICS as server component in a number of scenarios: Calling SICS functions from other applications, e.g. to request information from the SICS database (for example retrieving information for a business); perform an operation using SICS logic (for example exchanging a monetary amount using SICS’s exchange rates and rules, create a business or renew a business). /sicsdocs/technical/server/api_server/technical_paper/features/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/features/ 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. /sicsdocs/technical/server/api_server/technical_paper/deployment/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/technical/server/api_server/technical_paper/deployment/ This section briefly explains the hardware and software required for installing and running the SICS API Server component. It is assumed that there already exists a SICS database that the SICS API Server will work against. Hardware Requirements # The SICS API Server component runs inside a Java servlet container. Such containers are available for many operating systems. One instance of SICS API Server requires at least 1 GB of memory running on a 64-bit operating system.