SOAP Requests
SOAP requests are defined by the SOAP client, which sends the request to the web server, which then passes the request on to the SOAP RPC servlet. The SOAP RPC servlet can be found in the following location:
http://<host>/Windchill/servlet/RPC
where Windchill is the web application defined for the SOAP RPC servlet.
When sending a SOAP request, an Info*Engine SOAP client must specify a method to be executed and the class that supports the method. This information can be conveyed to the SOAP service in multiple ways:
• In the SOAPAction HTTP header in a URI (Uniform Resource Identifier) of the form:
uri:ie-soap-rpc:class!method
where method is the method to be executed and class is the class that supports the method.
• On the CLASS and METHOD query arguments.
If CLASS is specified as a query argument and METHOD is not, then the SOAP service attempts to resolve the method name by looking to the SOAPAction HTTP header and then the SOAP message body. If METHOD is specified as a query argument and CLASS is not, then the SOAP service attempts to resolve the class name by looking to the SOAPAction HTTP header.
|
|
GET requests to the SOAP service must contain a CLASS parameter, and return the WSDL document for the specified class. POST requests to the SOAP service are handled as SOAP requests.
|
The association between the method name sent by the SOAP client and the Info*Engine task that gets executed is maintained in an LDAP repository as a task delegate entry. The class sent by the SOAP client corresponds to a type identifier entry maintained in an LDAP repository. Type identifiers represent object types (or classes) and contain task delegates (or methods). The Info*Engine server that processes the task invocation is represented by a repository, which declares its repository type.
Repository types represent types of information systems and maintain what object types they can act upon. Repository types contain type identifiers. The repository is stored in the Windchill Directory Server that is used by Info*Engine. For more information on repositories, repository types, type identifiers and task delegates, see
About the Delegate Administration Utility.
