In this 2nd part, we will explore the detail involving the development preparation required in NWDS before actual coding can begin.
Then, in Directory API Development - Part 3 of 3, we will dive into the actual coding using the Directory API.
To use as an example for this blog, I will use the Directory API to create SOAP receiver communication channels. The steps of creating other types of communication channels are similar. Primarily, the parameter names and the adapter type will need to be changed.
This blog, part 2, covers the 1st 3 steps, and Directory API Development - Part 3 of 3 covers step 4.
For convenience, I included the above libraries in a user-library in NWDS.
After project creation, my project, DirAPI_Blog, looks like the following:
This is an easier way of importing the WSDL, since the binding and endpoint are already in the WSDL URL. However, for some reason, specific to the Communication Channel webservice, we will receive an error when generating proxy using this import. Consequently, for this blog, this method should only be used as a reference to be used with other Directory API webservices. Please use step (B) for the exercise in this blog.
Communication channel webservice:
Copy-n-paste the URL into the following in NWDS.
When we double-click on the root WSDL, we will see that the bindings have already been included:
We should see the following in our project:
So, now, we have to create the binding and endpoint.
and, select "SOAP" for the protocol:
Save the wsdl file.
If you used step (A) to import the WSDL, you will encounter a proxy-generation error: IWAB0399E Error in generating Java from WSDL: java.lang.NullPointerException
This error seems to occur only with the Communication Channel webservice. As a result, I will generate the proxy using the WSDL from step (B) above. If you have already done step (A), you can delete the 4 WSDLs created from the import and redo the import using step (B).
Note: If step (A) was used during the import, then you will need to do this for all of the 4 WSDLs created from the import.
Note: Do not forget to generate the java proxies for all the WSDLs created after importing the WSDL URL.
Because we imported the WSDL URL instead of using the external definition, there is no need to go thru the steps in the configuration of the binding and endpoint. We can just generate the java proxies after importing the WSDL URL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
39 | |
25 | |
17 | |
13 | |
7 | |
7 | |
7 | |
7 | |
6 | |
6 |