In part 2, we explored the details involving the development preparation required in NWDS before actual coding can begin.
In this blog, part 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 adapter type and the parameter names will need to be changed. To get the parameter names to use with the Directory API, it is recommended that a listing of an existing communication channel be done first using the "/wsnavigator".
Since a Communication Channel will have to be created in a Business Component or Business System, for this blog, I created two business components in the Integration Directory: BusComponent1 and BusComponent2
The userid must be authorized with the right roles to use the Directory API.
createChangeList: This method creates a new change list and returns its changelist id.
activate: This method activates the changelist, using the changelist id.
setURL: This method sets the URL on where the webservice is to be executed. By default, the webservice will executed on the server as set in the binding and endpoint of the WSDL configuration in part 2. We can change this configuration by using this method. Consequently, this code can be used to execute the webservice on any server.
It containts the following code:
createSoapChannelActivate: This method is the main method to create and actiate the SOAP communication channel configurations.
createChangeList: This method creates a changelist containing the SOAP communication channel configurations.
createSoapChan: This method creates all the SOAP communication channel configurations. build1SoapChan: This method creates one SOAP communication channel configuration.
setURL: This method sets the URL on where the webservice is to be executed. It serves the same purpose as in the ChangeList class.
setActivate: This method sets the flag on whether the configuration is to be activated. I included this option on whether to activate the changelist. If this is set to "false", then we can see the changelist list in the "Change List" tab of the Integration Directory. At that point, we can manually activate it or reject it. If set to "true", then the configuration will be activated by the program.
The class containts the following code:
We will see in the Integration Directory the changelist: (make sure you log on using the same userid as the one used in the Directory API program...you may also need to refresh the screen)
and
If we used "setActivate(true)", then there will be no changelist shown and the configuration would have been activated automatically.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
34 | |
25 | |
13 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |