Import WSDL

Import WSDL Screen

The Oracle Communications Convergent Charging Controller Data Access Pack DAP Import WSDL screen allows you to import and configure predefined web services from ASPs.

It contains these functions:

What is WSDL?

Web Services Description Language (WSDL) is a XML based language that provides a model for describing web services.

The reason for using WSDL is to import predefined web services from ASPs, thereby speeding up configuration of DAP messages.

For restrictions on what parts of the specification are supported, see Convergent Charging Controller Data Access Pack PICS Guide.

Accessing the Import WSDL screen

Follow these steps to open the DAP Import WSDL screen.

Select the Services menu from the SMS main screen.
Select DAP.
Select Import WSDL.

Result: You see the Import WSDL screen.

Importing a WSDL file

Follow these steps to import a WSDL file.

On the Import WSDL screen, perform one of the following actions to select a file:
- Enter the location and name of the .wsdl file in the File/URL field. The file location can be an URL. For information about specifing URLs, see About Specifying URLs.
- Click Browse to find the file
The file has the suffix of .wsdl (for example DAP.wsdl)

Result: The Import button becomes available.
Click Import.

Result: The WSDL file is imported, then:
- The Operation/Description panel is populated from the imported file
- The No operation has been added message is displayed in the Notice/Error box.
To add:
- All operations, select the Add check box
- Selected operations, select the check box for each of the required operations
Result:
- Any configuration requirements are displayed in the Notice/Error box.
- The configuration fields under the ASP, Request, and Response tabs are populated with data from the WSDL and become available for editing.
- The Operation Set field becomes available.
  
  Warning: If you select multiple operations, you must configure all of them before the Save button is available. If there are any kind of fatal system problems, you will need to re-do any unsaved configuration.
Select the Operation Set to use from the drop down list.

Note: See Operation Sets for details on configuring this list.
Click on the operation to configure.
Configure the ASP as required. See ASP for more information.
Configure the request as required. See Operation Request Configuration for more information.
Configure the response as required. See Operation Response Configuration for more information.
Repeat steps 4 to 8 for each operation that you want to configure.
When there are no errors listed in the Error/Notice area, the Save button becomes available.

Click Save.

The ASP and the configured operations are created. You can view and edit them on the DAP Resources Screen.

Operation Request Configuration

You use the Request tab on the Import WSDL screen to configure the request parameters that are within the imported operation script. The imported operations are used by the DAP Request feature node.

Configuring requests

Follow these steps to configure operation request parameters.

In the Request tab, expand the parameter tree to see all the elements that can be configured (click + signs).

Note: Each element is preceded by a C, a P, an O, or an E:
- C – For a complex parameter that has more than one sub parameters.
- P – For the last element down a branch. This is the parameter that can be configured.
- O – For an optional parameter that may require configuration.
- E – For an empty sub-parameter within a complex parameter. This is not configurable.
Select the parameters to configure by selecting the check box preceding the parameter.

All the selected parameter names are colored red to indicate that the parameters require configuration, and the error reasons appear in the Error/Notice area. Sometimes all parameters under a selected complex parameter are automatically selected because they are all required.

Tip: Hover over a parameter to get a tip if a box cannot be selected or deselected.
Click a parameter name to configure.

The parameter name appears in the Name field, the editable parameter fields are made available, and the Iterator For table is populated with all the request elements.
If this parameter is to be used as a unique id, select the Correlation ID check box and then start configuring a new parameter.
Type a description for the parameter in the Description field.
Select the feature node behavior for the parameter from the Node Disposition list.

Note: The option you select determines whether or not you are required to configure a run-time parameter in a DAP feature node that sends XML requests.

Select one of the following options:
- Hidden – If the parameter will not be visible in the feature node configuration window and the parameter must be configured in this screen.
- Text – If the parameter will be completed in the feature node configuration window as a text field.
- Profile Block – If the parameter will be completed in the feature node configuration as a profile block location.
- Either – If the parameter will be completed in the feature node configuration either as a text field or as a profile block location.
- Transient – If you do not want to provide a run-time parameter and you also want to send the text defined in the XML template without any further processing.
Note: The Transient option enables the DAP to process XML requests containing attributes where the parameters are not recognized.
If you selected the Hidden disposition, perform one, or both, of the following steps:
1. Type the default value for the parameter in the Default Value field.
2. Select the location of the parameter from the Profile Field Type, Profile Block, and Profile Field lists.
Tip: The Xsd Type field indicates what type of data is expected in the DAP message for this parameter.

Note: If an expected profile field is missing, it can be added via the ACS Configuration screens. For information about configuring profile fields, see Advanced Control Services User's Guide.
If this parameter is being used as an iteration value for a request element, scroll to find the element in the Iterator For list and select the Add check box.

The parameter will be added to the request template element as an iteration.

Tip: A parameter can be an iterator for more than one element, however one element registers just one parameter as the iterator.
Repeat steps 3 to 8 for all the parameters that require configuration.

Operation Response Configuration

You need to configure any responses required by the imported script. You perform this on the Response tab.

Configuring responses

Follow these steps to configure all response parameters.

In the Response tab, expand the parameter tree to see all the elements that can be configured (click + signs).

Note: Each element is preceded by a C, a P, an O, or an E:
- C – For a complex parameter that has more than one sub parameters.
- P – For the last element down a branch. This is the parameter that can be configured.
- O – For an optional parameter that may require configuration.
- E – For an empty sub-parameter within a complex parameter. This is not configurable.
Select the parameters to configure by selecting the check box that precedes each parameter.

All the selected parameter names are colored red to indicate that the parameters require configuration.
Click a parameter name to configure.

The parameter name appears in the Name field, the editable parameter fields are made available
In the Description field, type what the response is expected to be.
If this parameter must be returned, select the Required check box.
If this parameter can be edited in feature nodes, select the Node Editable check box.
If the return of this parameter is an error condition, select the Indicates Error check box.

Note: The Required and Indicates Error check boxes are mutually exclusive.
Select the profile type and location for the parameter from the Profile Field Type, Profile Block and Profile Field lists.

Note: If an expected profile field is missing, it can be added via the ACS Configuration screens. For information about configuring profile fields, see Advanced Control Services User's Guide.

Result: The last error message for this parameter will disappear from the Error/Notices panel.
Repeat steps 3 to 8 to configure all the response parameters.