Creating a WSDL Document: Add Operation
In this section, create a WSDL Document using the Add operation. For this example, create AddWSDL.wsdl in the BPEL project. Use the Partner view of the WSDL editor to configure the components of the WSDL Document.
To Create a WSDL Document: Add Operation
- Expand the BPEL Module project node in the Projects tab.
- Right-click the project node or Process Files node.
- Select New —> WSDL Document...
The New WSDL Document wizard appears.
- Type the File Name in the File Name field.
- Select Concrete WSDL Document.
- Choose the Binding — LDAP from the drop-down list.
- Choose one of the following Types from the drop-down list.
- From LDAP Server
- From LDIF File
- From LDAP Server
- Click Next.
- Enter the Root DN and LDAP Server URL.
Note _ DN is the base object entry search relative to. In the following image the Root DN is dc=sun,dc=com and the format of the LDAP Server URL is ldap://hostname:port.
- Click Advanced.
The Advanced Login dialog box appears.
- Enter values for the fields describe in the following table:
| Field | Description | Required Value |
| Principal | Allows you to specify the principal needed when using an authentication mechanism other than the anonymous log-in (authentication = none). | The fully qualified Distinguished Name (DN) of the user. For example: cn=Administrator,cn=Users,dc=stc,dc=com |
| Credentials | Allows you to enter the credentials needed when using an authentication mechanism other than anonymous log-in (authentication = none). | The appropriate credentials, such as valid password. |
| SSL Connection Type | Allows you to specify SSL connection type. | Select None, Enable SSL, or TLS On Demand. Enter the desired value as follows: * None: No SSL, simple plain connection. * Enable SSL: SSL is enabled. All communication to the LDAP server uses a secure communication channel. Note - If you are using the Enable SSL option, the ProviderURL property must point to a secure LDAP port. |
| Authentication | Allows you to select the method authentication (none or simple). Select the desired authentication as follows: * None: No authentication, that is, an anonymous log-on. If you use this setting, ensure that the LDAP server supports anonymous log-ons if you are using this setting. * Simple: Authentication is based on a user name and password. Provide the user name and password in the appropriate fields (Use the Principal and Credentials). | Select None or Simple. The default is None. |
| TrustStore | Specifies the default TrustStore. The TrustStore is used for CA certificate management when establishing SSL connections. Click Browse to select the trust store file. | A valid TrustStore file. There is no default value. |
| TrustStore Type | Allows you to specify the TrustStore type of the TrustStore used for CA certificate management while establishing an SSL connection. If the TrustStore type is not specified, the application uses JKS as the default TrustStore Type. | A valid TrustStore type. |
| TrustStore Password | Allows you to specify the default TrustStore password. The password is meant to access the TrustStore used for CA certificate management while establishing SSL connections. | A valid TrustStore password. There is no default value. |
| KeyStore | Specifies the default KeyStore file. The keystore is used for key/certificate management while establishing SSL connections. Click Browse to select the key store file. | A valid package location. There is no default value. |
| KeyStore Type | Allows you to specify the default KeyStore type. The keystore type is used for key/certificate management when establishing SSL connections. If the KeyStore type is not specified, the default KeyStore type is used. | A valid KeyStore type. |
| KeyStore Username | The user name for accessing the keystore used for key/certificate management when establishing SSL connections. | A valid KeyStore user name. |
| KeyStore Password | Specifies the default KeyStore password. The password is used to access the KeyStore used for key/certificate management when establishing SSL connections; there is no default. | A valid KeyStore password. There is no default value. |
| TLS Security | Specifies whether TLS security is enabled. | The default value is NO |
12 Click OK to close the Advanced Login Dialog.
13 Click Next.
The New WSDL Document — Operation Setting dialog box opens.
- Search
- Add
- Update
- Delete
14 Click the Add tab.
 |
Select the following Object Class:
* person
* inetOrgPerson
Click the down arrow to move them from the top-left pane to the bottom-left pane.
Each schema is made up of a set of attributes.
For example,
* person — person.sn and person.cn
* inetOrgPerson — inetOrgPerson.uid and inetOrgPerson.mail
They are represented as follows:
schemaname.Attributename
a sn — Surname
b cn — Common Name
c uid — Unique id
d mail — Email
 |
15 Set any one of the Attributes to Relative Distinguished Name (RDN).
A Relative Distinguished Name (RDN) is a component of the distinguished name.
For example, cn=John Doe, ou=People is a RDN relative to the root RDN dc=sun.com.
 |
For example, Set inetOrgPerson.uid = RDN
16 Click Finish.
The illustration is as shown.
 |
A tree structure is formed as follows:
a AddWSDL.wsdl — Target WSDL
b AddWSDLAdd.xsd
c LdapBase.xsd
Previous
- Tutorial Overview
- Tutorial Requirement
- Tutorial Plan
- LDAP Binding Component Project in a Nutshell
- Functional Architecture of LDAP Binding Component
- Downloading GlassFish ESB Installer
- Downloading and Installing the JAR Files and the NBM Files
- Starting the GlassFish V2 Application Server
- Creating a BPEL Module Project For the Add Feature
Next
Create a WSDL Document For Type : SOAP
See Also
|
JSPWiki v2.4.100
|
Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. 
![[RSS]](http://wiki.open-esb.java.net/images/xml.png "Aggregate the RSS feed")
|