Chapter 6 Building an Executable BPM: Working with Service Description Objects
The General tab contains the following properties:
| Property | Description |
|---|---|
| Name | The name of the item which should be clear and meaningful, and should convey the item's purpose to non-technical users |
| Code | The technical name of the item used for generating code or scripts, which may be abbreviated, and should not generally include spaces |
| Comment | Descriptive comment for the object |
| Stereotype | Extends the semantics of an object derived from existing objects but specific to your needs. You can type stereotypes directly in the Stereotype box of the object property sheet or select a value from the list if you have previously defined stereotypes in an embedded or imported extended model definition (.XEM) or in the process language |
| Filename | Path of the file that contains the whole service definition. It is set during the import and used during a file generation. You can click the Select a File tool beside the Location box to select a .WSDL file then click the Open a File tool to open the WSDL file |
| Endpoint URL | Address at which the service can be reached |
| Target namespace | URL linked to a method that uniquely identifies the Web service and avoids conflicts with other Web services of the same name. By default, it is: urn:<Service Provider Code> |
| Prefix | Allows you to type a namespace prefix for the target namespace. It is useful to find an element of the WSDL defined on the web. The default value is: "tns" that stands for "This NameSpace", for example: <tns:invoice>, where "tns" is the prefix associated with the XSD document that describes the "invoice" markup |
| Implementation | OOM component implementing the service provider. You can add or remove an implementation object, you can also see its properties. For more information, see the Implementing a service provider using an OOM component section |
| Copyright (C) 2007. Sybase Inc. All rights reserved. |
| |