1. How to manually generate the Proxy Code
2. The difference/reason for using NotificationProducer as opposed to NotificationConsumer
3. The difference/reason for using User and Session services
4. The length of time the session is kept in CMF
1. How to manually generate the Proxy CodeJava - Apache CXF - wsdl2JavaTo manually generate the proxy code using Apache CXF Services Framework - WSDL to Java, please see the following tutorials: C# - Visual Studio – wsdl.exeFor Single ServiceTo use Visual Studio’s WSDL.exe please follow these steps: a) Make Sure you update your hosts file
b) Open up the Visual Studio Command Prompt
c) Type in the command · wsdl · Location of your service · /out: Location of Generated Proxy
d) The generated proxy code will be saved to the Microsoft Visual Studio directory
For Multiple ServicesFor multiple services, you need to generate the proxy code for all your required services into one single file and include the option /sharetypes. To use Visual Studio’s WSDL.exe for multiple services please follow these steps: a) Please see step A above b) Please see step B above c) Type in the command · wsdl · /sharetypes · Location of your service. Your services should be separated by a single space · /out: Location of Generated Proxy
d) The generated proxy code will be saved to your specified directory. Please note you can
|
2. The difference/reason for using NotificationProducer as opposed to NotificationConsumerNotification ProducerA Notification Producer is capable of producing a set of Notification messages. One uses the NotificationProducer to send out requests to the web services.
Notification ConsumerA Notification Consumer represents the endpoint to which the Notification Producer sends events. One uses the NotificationConsumer to receive responses from the web services.
Please see a detailed description of both the NotificationProducer and NotificationConsumer here:
|
3. The difference/reason for using User and Session servicesUser ServiceThe User Service models a user in the system. This service provides methods to read attributes such as address(s), Terminals(s) etc. For more list of features this service provides, please see here: · User Session ServiceThis is a summary service and represents a subset of all the other services exposed and as such can be used in place of them in many cases. The Session Service exposes a higher level API thus making it easier to use. For more list of features this service provides, please see here: · Session |
4. The length of time the session is kept in CMFIf there is no activity related to the SSO token for 2 hours (see configuration) the session will timeout and subsequent calls using this session will fail. If the user has registered for events then a SessionTermination imminent event will notify that the session is about to expire and must be refreshed. If the Open Interfaces service is interrupted (planned or unplanned) the session will be invalidated and an exception will be thrown the next time this session is used. |