Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Stat 6.3 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Appendix: SOAP-Based Web Services API

Stat provides programmatic access to CSR information via a Web Service API.

The Stat Web Services are available when the Stat Central Agent is live.

API calls represent specific operations that your client applications can use to retrieve or update data, such as:

The following information is intended for developers and system administrators who want to use Stat Web Services to develop an interface to one or more of their in house applications, specifically for managing CSRs.

Stat Web Services are implemented using the JAX-WS 2.0 technology available in JBoss application servers. When developing the interface for Web Services, the Top-Down approach (also known as WSDL-first approach) is used. All WSDL files are created using the Document/Literal Wrapped strategy.

Users accessing Stat through Web Services must establish a valid connection. The Stat Central Agent maintains a list of valid connections, which are refreshed each time a user makes a call to any service. The user should close the connection after making all the desired service calls. If a connection is left open longer than a specified period of time, the Stat Central Agent automatically closes the connection and the user will have to establish a new connection for any future service calls. The default session timeout value is set for 30 seconds (30000) in the System Maintenance window. For more information, see Parameters Tab .

Services and Exposed Methods

This section documents the Login Service, CSR Service, and Approval Service and their exposed Methods.

Login Service

The URL for the wsdl file of this service is located at:

http://hostname:port/stat/WSLoginService?wsdl

long connect( String userId, String password ) throws WSLoginFault;

User has to establish a valid connection in order to interact with Stat through Web Services. Connections are validated the same way a normal login into the Web Client is validated. Upon successful connection, a valid Connect ID is returned to the user, which will be used in subsequent method calls to validate user's connection. Also proper rows are written into CONNECTION_MGMT and CONNECT_HIST tables. A list of valid connections is stored on the server and the connection is refreshed each time a valid Web Service Method is executed. This connection will have to be either closed by User or it will expire after a time-out period.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating