Administration Guide
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This chapter describes how to publish Liquid Data stored queries as Web Services. It contains the following sections:
Using the Administration Console, you can publish Liquid Data stored queries as Web Services. Web-based applications can then invoke Liquid Data queries as Web Service clients.
Generate Web Service Demo... If you are looking at this documentation online, you can click the "Demo" button to see a viewlet demo showing how to use the Liquid Data Administration Console to generate a Web Service from a stored query. The viewlet also demonstrates how to test the generated Web Service in BEA WebLogic Workshop. The demo assumes that you have already stored the query you want to use in the Liquid Data Repository.
Web Services are a type of service that can be shared by, and used as components of, distributed Web-based applications. Web Services communicate with clients (both end-user applications or other Web Services) through XML messages that are transmitted by standard Internet protocols, such as HTTP. Web Services endorse standards-based distributed computing. Currently, popular Web Service standards are SOAP (Simple Object Access Protocol), WSDL (Web Services Description Language) and UDDI (Universal Description, Discovery, and Integration).
This section describes how to generate a Web Service from a stored query in the server repository. For each stored query, you can have up to one generated Web Service.
Notes: The names of stored queries to be generated as Web Services must begin with an alphabetic character, followed by other alphabetic characters or numbers. The file name must also have an .xq
suffix. For more information, see Naming Conventions for Stored Queries in Building Queries and Data Views.
To create a new Web Service from a stored query:
Note: If the Generate Web Service link is not available, then a Web Service has already been generated for this stored query. Also, if the query does not have a schema already associated with it, you must configure one before the Generate Web Service link appears.
Figure 23-1 Web Service Generation Success Screen
If the associated stored query is modified or deleted, then this generated Web Service is deleted automatically. If the stored query has been modified, you need to explicitly create it again using the instructions in this section.
You cannot directly modify a generated Web Service. If the associated stored query is modified or deleted, the generated Web Service is deleted automatically.
You can delete a generated Web Service that you no longer need or that you want to regenerate.
Note: A Web Service is automatically deleted if its associated stored query is subsequently changed or deleted.
To directly delete a Web Service:
You can use WebLogic Workshop to test a Web Service that you have generated with the Administration Console.
.jcx
) file..jcx
) file, right-click, and select Generate Test JWS File. Workshop generates a Java Web Service (.jws
) file.
When you create a Web Service, the Administration Console automatically deploys the generated EAR
file to all nodes in the currently active domain. If you subsequently need to manage this EAR
file, such as undeploying or redeploying it:
For detailed information about WebLogic Web Services, see Programming WebLogic Web Services in the WebLogic Server documentation.
If you want to find the target schema for a generated web service, the target schema is stored in the generated EAR
file. To view the contents of the EAR
file, open the file with a utility such as WinZip. The EAR
file is located in the following directory:
<ld_repository>/web_services_gen
The filename of the EAR
file is generated based on the filename of the stored query from which the web service was generated. For example, if a stored query is named order.xq
, the generated web service name is order.ear
.
You invoke Liquid Data Web Services that were generated in the Administration Console using the same approach that you would use for invoking any WebLogic Web Service. For more information, see Invoking Queries in Web Service Clients in the Application Developer's Guide.
![]() |
![]() |
![]() |