SICS API Server - Life - Business - Retrieve Reinstatement Condition

Please select example from the menu on the left side.

SICS API Server - Life - Business Partner

SICS API Server - P&C - Business - Retrieve Reinstatement Condition

Please select example from the menu on the left side.

SICS API Server - P&C - Business Partner

SICS API Server - P&C - Business Partner - Create Or Update Collateral Details - Update

Create Or Update Collateral Details # Description # Updating Collateral Details using createOrUpdateCollateralDetails API. Request message # <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Header /> <SOAP-ENV:Body> <swbpep:createOrUpdateCollateralDetails xmlns:swbpep="urn:SicsWsBusinessPartnerEntryPoint"> <genericInput /> <createOrUpdateCollateralDetailsInput> <businessPartnerReference> <identifier>S165S1A</identifier> </businessPartnerReference> <collateralLatestDetailUpdate> <loCCategory> <code>LETT_OF_CRED</code> <subclassNumber>1236</subclassNumber> </loCCategory> <loCAmountType> <code>INCREASE</code> <subclassNumber>1238</subclassNumber> </loCAmountType> <bankDate>2023-03-15</bankDate> <amount>54</amount> </collateralLatestDetailUpdate> </createOrUpdateCollateralDetailsInput> </swbpep:createOrUpdateCollateralDetails> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Response message # <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <swbpep:createOrUpdateCollateralDetailsResponse xmlns:swbpep="urn:SicsWsBusinessPartnerEntryPoint" xsi:type="swbpep:CreateOrUpdateCollateralDetailsOutput" /> </soapenv:Body> </soapenv:Envelope>

SICS Configuration Manager

SICS eMessaging Server

SICS Naming Service

Brief Description # The SICS Naming Service (SNS) is responsible for mapping users to SICS Workstations. The SNS is a JEE web application based on JAX-WS and the METRO web services stack.It must be run within a JEE application server. The list of registered users / workstations is persisted (stored) in a SICS database. The SNS connects to the database via a JNDI datasource. SNS is stateless. That is, each web service request will read data from the database. ...

Standard Settings

The use of SICS functions obviously varies from user to user and from one SICS session to another. Likewise, the amount of data being processed varies from user to user and from one SICS session to another. Therefore, it is not possible to pre-set the heap memory size in such a way that, the JVM never runs out of memory, and there is no gross over-allocation of memory. The best one can do, is to pre-set the memory limits such that ...

Starting the Configuration Manager

Start the SICS System Administration Utility. Log in with a source user and select the source environment. The source user (or the associated 2nd level user if using two level login) must have SELECT, UPDATE, DELETE, INSERT rights on all SICS tables in the source schema. In the case of Oracle, the source user must also have SELECT rights on various RDBMS system tables / views containing meta data (SYS.ALL_TAB_COLUMNS and SYS. ...