Parent Topic: Building a LabVIEW Application to Deploy Remotely
A deployed LabVIEW application can include Web method VIs, Web method VI dependencies, auxiliary VIs, and static content files.
|Note This topic assumes familiarity with the Web services introduction and Building a LabVIEW Web Service Application tutorial. LabVIEW Web services are available only in the LabVIEW Full Development System and the LabVIEW Professional Development System.|
Web method VIs are the top-level VIs in a Web service application that contain the core functionality of that Web service. You can exchange data between a Web client and Web method VIs over the network. You can configure a VI as a Web method VI when you build and deploy a LabVIEW Web service application. Use the Configure RESTful VI dialog box on the Source Files page of the Web Service Properties dialog box to specify a VI in a Web service as a Web method VI. Each Web service can include multiple Web method VIs.
Web method VI dependencies are necessary components of the Web method VI. Web method VI dependencies include subVIs, shared variables, DAQ channels, and other components that appear within a Web method VI.
LabVIEW Web services automatically package some Web method VI dependencies, such as subVIs, when you deploy the Web service. Deployed Web services does not include Web method VI dependencies such as shared variables.
Auxiliary VIs run as part of a Web service application but do not exchange data with a Web client. However, auxiliary VIs can exchange data with Web method VIs without using network resources, which can increase overall application efficiency. You can configure a VI as an auxiliary VI when you build and deploy a LabVIEW project as a Web service. Use the Configure RESTful VI dialog box on the Source Files page of the Web Service Properties dialog box to specify a VI in a Web service as an auxiliary VI. Each Web service can include multiple auxiliary VIs.