This section describes strategies for creating Remedy applications. The strategy uses advanced web services, and WSDL files to access Remedy Java methods and the Remedy data source. You can create a master Remedy application, and link to insert, update, verification, and login applications, and you can create a web service application to access the Remedy data source.
You can create a JSP template to handle known capture problems, especially for older versions of Remedy. See “Adding JSP-related capabilities” and Chapter 6, “Building Templates” for information.
The following section shows the basic procedure for using the Mobile Web Studio interface to create a Remedy application. See the Mobile Application Development Tutorial for detailed information.
Creating Remedy applications using Web services and WSDL
files
From Mobile Web Studio, select Build | Applications, and then click the New button.
On Application Builder, click the down arrow to the right of the Add button, and select Web Service Element.
On the Web Service Element Definition window, identify the WSDL file to use:
Service Type – select WSDL.
UDDI Key/UDDI Registry – do not select this option.
WSDL URL – enter the WSDL file location; for example:
http://hostname/arsys/WSDL/public/ hostname/HelpDesk_Query_Service
Replace the hostname string with
the host name of the mid-tier server specific to your own installation.
Use Standardization XSLT – do not select this option when creating Remediy applications using a Web service.
Get Method – click Get Method. The system retrieves the WSDL XML and populates the Method drop-down list. The list of defined services is extracted from the WSDL file you specified in WSDL URL.
If you cannot access the WSDL URL you specified, WSDL files may be kept in a secure location and require a user name and password for access. If necessary, see the Remedy system administrator for access information. You can use the WSDL Authentication option to gain access.
Authentication – select the Authentication option. The User Name and Password fields appear.
User Name and Password – enter the user name and password provided by your Remedy system administrator.
Click Get Method. The system should retrieve the WSDL XML and populate the Method drop-down list.
On the Web Service Element Definition window, identify the method to use:
Method – select a method from the drop-down list.
Click Preview to see a list of the input parameters of the selected Web service method in the Preview pane
In the Web Service Element Definition window, make sure Enable Grid Rules is selected. This option is required to display the element output in grid format.
If you want the Web service application to be viewable
on a mobile device, you must check the Enable Grid Rules box.
Optionally on the Web Service Element Definition window, establish the login method for accessing the Remedy datasource:
Define Login Method – select this option if you selected a Web service method that requires a seperate invocation to a login method to get valid session information for future transactions.
When you select this option, three new fields appear:
Login Method
Login Params
Login Profiles
Login Method – if you selected a method where the Web Service requires session information in the SOAP header, select the login method from the drop-down list; for example, RemedyDISSoap:Login.
Login Profiles – select a login profile from the drop-down list. The Login Params option disappears.
Login Params – alternatively, enter the login parameters manually in the Login Params text area. You must specify the datasource (such as labxp), the user name (sa), and password for your environment.
Optionally on the Web Service Element Definition window, establish BASIC Authentication.
Enable BASIC Authentication – select the Enable BASIC Authentication option. The User Name and Password fields appear.
User Name and Password – enter the user name and password. The user name and password are used internally by the Web services element for basic authentication of HTTP requests of SOAP calls.
Optionally on the Web Service Element Definition window, specify a custom JSP file:
Advanced – select the Advanced option. The JSP Filename field displays to the right of the Method or Login Method fields.
JSP Filename – enter the name of a JSP file you previously created.
On the Web Service Element Definition window, search for or define an XSLT template. An XSLT template is used to transform XML format to the grid format required to build mobile applications.
Content XSLT – search for or create a content XSLT template.
UI XSLT – search for a user interface XSLT template.
To create the Web service element and to see the Web
service application on a mobile device, you must define Content
XSLT. The Content XSLT template transforms Remedy business object
XML to the XML format required by Unwired Accelerator to create
the grid format needed for mobile applications. See Chapter 6, “Building Templates” for information about
XSLT templates.
Click Create, located to the right of Content XSLT. The Web Services Output XSLT Template Customization window displays.
In UA Web services, UA uses cached information for the
templates. If you make changes to the cached Content XSLT template,
the changes do not take effect until the next Tomcat server restart.
On the Web Services Output XSLT Template Customization window, modify the Content XSLT for the business object:
Name – enter a name for the
template; for example, HelpDeskList.
Roles – select the roles for the runtime version of the mobile application. Use the buttons to move roles in and out of the Available and Selected columns. These are Unwired Accelerator roles and have no bearing on Remedy object security.
Select Output Parameters for Display – select the output parameters to include in the Web service element. Use the buttons to move output parameters in and out of the Available and Selected columns. Use the horizontal scroll bar to view the entire output parameter name.
Update Output Display Name – for Output
Parameters for Display, highlight an object in the Selected list,
such as FullName. The Update
Output Display Name field is populated with this value. You can
change the value to something more meaningful or readable for the
mobile application, such as Full Name.
If you do not have multiple records within the selected object, skip this step.
If you have multiple records within the object (for example, multiple card codes, employees, service codes, and so forth), select the node level of the repeating record.
Remedy business objects often contain multiple records at various nodes levels. Unwired Accelerator supports one node level per element, but enables you to specify the node level to use for a specific record. You select the node level to use from the Web Services Output XSLT Template Customization window. If you select more than one node level, the Web Service element will not work.
Select Node Level That Contains One or More Child Records – click Select to the right of this field. The Web Services Output Node Level window displays.
Highlight a node level, such as getListValues,
and click OK. The window closes and the value is populated in the
Select Node Level That Contains One or More Child Record field.
Click Save to save the template, and OK to confirm then return to the Web Service Element Definition window.
On the Web Service Element Definition window, click Input, and type input for Remedy objects and parameters as needed:
For objects, enter the object identifier; for
example, for _HEADER.Authenticationinfo.userName,
you could enter Demo.
For parameters, enter a default value; for example,
for QueryListBy_FullName_Full_Name,
you could enter a.
If you want the Web service application output to be
viewable on a mobile device, you must provide input parameters.
In most cases, you can provide them on the Preview window to see
the results more quickly, or you can provide them on the Configure
Parameters window later in the process.
However, if you are creating a Web service element using the AddObject, UpdateObject, or RemoveObject methods, Sybase recommends you not enter input parameters in the Preview window. Otherwise a new record is created for every window in the mobile application wizard (Define, Filter, and so forth) since no invocation can be done, and no action can be performed to the database. Consequently, you end up with many user records, one for each window, rather than the one record you want. Instead, enter input parameters in the Configuration Parameters window for these methods.
Click Next. The Define window displays. The business object should display in a grid format, indicating the XML transformation from Remedy format to Unwired Accelerator format occurred successfully.
Use the Define, and Filter windows to define the mobile application in the same way you would define any other mobile application.
In Configure Parameters, under Variables, select the boxes for the parameters you need, and configure the CGI Parameters.
If you need to modify these parameters, you can do so
after you save the application. Access Application Builder, select
Params, and modify the parameters.
Click Next.
On the Preview window, enter an element name, and click Finish.
On the Application Builder window, save the mobile application and click Finish. Optionally, you can click Preview to preview the application, then approve the application.
Finalizing the Remedy application
Once you have saved the mobile application, you can set up CGI parameters, including linked parameters, which enables you to set up chained relationships among field/parameter values. This makes it easier to create and update applications.
For example, on the Remedy Administration GUI, you have many drop-down fields to choose from, and the values of some drop-down fields you select can affect choices in other fields. Linking parameters provides a way to imitate the Remedy Administration GUI, by linking a field to its data source. Additionally, on the mobile device, the drop-down options are available to the user.
In Application Builder, select Params.
In Configure Parameters, click Next.
For the parameter, under Display Type, select Linked from the drop-down list. The Add and Clear buttons appear.
Click Add, then search for and select the application to which to link. This application is the data source. After you save and close the window, the linked application displays in the Component column.
You can select multiple parameters and select Add, to
link the application to multiple parameters.
Repeat the procedure for any parameters you need; for example, any of the Remedy parameters your application needs.
Make any additional configuration parameter settings you need.
To remove a linked parameter, click Clear.
In the Configure Parameters window, click Save.
