Before You Begin Using the WSDL Files

This topic lists the prerequisites that you must complete before you integrate your application with RA. It also describes how to use RA WSDL files and provides a quick recap of the steps that you must perform to set up your environment to use RA Web service. It contains the following sub-topics:
cara
This topic lists the prerequisites that you must complete before you integrate your application with RA. It also describes how to use RA WSDL files and provides a quick recap of the steps that you must perform to set up your environment to use RA Web service. It contains the following sub-topics:
Prerequisites
Before you integrate your application with RA, you must install and configure RA, ensuring that:
  • The systems on which you plan to install RA meet the system requirements.
  • You have completed the configuration and planning-related information:
    • You have installed and configured the required number of RA database instances.
    • You have installed the applicable version of JDK on the system where you plan to install RA components that use JDK.
    • You have also installed the required application server.
  • In the case of
    single-system deployment
    of RA, ensure that all the components are up and running.
  • In the case of
    distributed-system deployment
    of RA, ensure that the connection is established between all the components and that they successfully communicate with each other.
Using Risk Analytics WSDL Files
To generate client applications, you must use the WSDL documents that are shipped with RA. These documents define the request and response messages that are exchanged between your application and Transaction Server to perform an operation.
The following table lists the WSDL documents that RA provides. These WSDLs are available at the following location:
  • On Microsoft Windows:
    <install_location>
    \Arcot Systems\wsdls\
  • On UNIX-Based platforms:
    <
    install_location>
    /arcot/wsdls/
You can use any tool of your choice, such as Apache Axis or .NET SOAP Framework, to generate client stub classes by using the WSDL files listed in the following table. You can then use the generated stub classes to build your application and access the required Web services.
WSDL File
Description
riskfort/
ArcotRiskFortEvaluate
RiskService.wsdl
Used to perform risk evaluation and post evaluation.
riskfort/
ArcotRiskFortAdminWeb
Service.wsdl
Used to manage a few administrative operations.
uds/
ArcotOrganizationManagementSvc.wsdl
Used to create and manage organizations in your setup.
uds/
ArcotConfigManagementSvc.wsdl
Used to create and manage user account types.
uds/
ArcotUserManagementSvc.wsdl
Used to create and manage users and user accounts.
If you are using .NET SOAP Framework to generate the client stubs, then you must include the following line in your code
before
you invoke the RA operations (ArcotRiskFortAdminSvc and RiskFortEvaluateRiskSvc):
ServicePointManager.Expect100Continue = false; // which is available in System.Net;
If you do not include this line, you might see errors.
Quick Summary
The following steps provide a quick recap of the steps that you must perform to set up your environment to use RA Web service:
  1. Access the WSDL by navigating to the following location:
    On Microsoft Windows:
    <
    install_location
    >\Arcot Systems\wsdls\
    On UNIX-Based platforms:
    <
    install_location
    >/arcot/wsdls/
  2. Generate the client stub classes by using the WSDL files.
    You can use a SOAP Framework, such as Apache Axis or Microsoft.NET, to generate client stub classes from a WSDL file.
  3. Create the client application by using the stub classes generated in Step 2.
    Depending on the software that you choose, refer to the respective vendor documentation for more information about writing the client and the files required for the client to connect to the RA Web service.
  4. Connect the client to the RA Web service end point by using the default URLs listed in the following table.
    The following table lists the default URLs on which the Web services listen for client requests. If you change the service end point URL, then ensure that you connect your client to the new location that you have configured.
Web Service
URL
Organization Management Web Service
http://<Apphost>:<port_number>/arcotuds/services/
ArcotOrganizationManagementSvc
Apphost
: Host name or the IP address of the system where User Data Service (UDS) is deployed.
Port
: The port number at which the application server (on which UDS is deployed) is listening.
User Management Web Service
http://<Apphost>:<port_number>/arcotuds/services/
ArcotUserManagementSvc
Apphost
: Host name or the IP address of the system where UDS is deployed.
Port
: The port number at which the application server (on which UDS is deployed) is listening.
Configuration Management Web Service
http://<Apphost>:<port_number>/arcotuds/services/
ArcotConfigManagementSvc
Apphost
: Host name or the IP address of the system where User Data Service (UDS) is deployed.
Port
: The port number at which the application server (on which UDS is deployed) is listening.
Risk Evaluation Web Service
http://<Apphost>:<port_number>/services/RiskFortEvaluateRiskSvc
Apphost
: Host name or the IP address of the system where Transaction Server is installed.
Port
: The port number at which the Transaction Web Services protocol is listening. By default, this is
7778
.
Administration Web Service
http://<Apphost>:<port_number>/services/ArcotRiskFort
AdminSvc
Apphost
: Host name or the IP address of the system where Transaction Server is installed.
Port
: The port number at which the Administration Web Services protocol is listening. By default, this is
7777
.
To secure the connection using SSL, enable the Web Services protocols for SSL connection.
5. Send the requests to the RA Web service through the client.
The RA Web service processes the request and returns the message, response code, reason code, and transaction ID in the response.