Working with data sources
You can create form designs that go beyond simple data capture. Using LiveCycle Designer ES, you can integrate your form designs with corporate databases or web services to build and maintain data capture solutions that read from, validate against, and add to corporate data sources. To do this, you connect your form design to one or more data sources and bind the data to one or more fields in your form design.
You can connect and bind fields to these data sources:
XML schemas
XML schemas specify how to formally describe the elements in an XML document. By connecting to an XML schema, you can bind the elements and attributes defined in the schema to fields in the form design. You can also select the XML data root element to use for the connection.
OLEDB databases
OLEDB is a Microsoft integration standard, which provides low-level application program interface (API) to data across an organization. By connecting to an OLEDB database, you can create form designs that serve as a data entry or capture tool for enterprise database servers. You can also use a database to provide content for portions of a form at run time.
Sample XML data
By connecting to an XML file, you can bind fields to the elements and attributes defined in the XML file. This method is useful when you do not have an XML schema, but you have an XML file that you can use as a sample.
Web Service Definition Language (WSDL) files
WSDL files describe web services by using XML. By connecting to a WSDL file, you can bind fields in a form design to one or many web services. You can create a data connection to a WSDL document on a web server and use HTTP/HTTPS or message level authentication or both to control access.
Там же дальше по хелпу есть как соединять СУБД с источником данных в форме лайвсайкл.
To create a data connection to an OLE database
You may want your form to have access to information in a database. For example, you may want to retrieve data to populate a form based on a value, such as an employee ID, that the user enters when filling the form. When the user enters the ID number, it triggers a database lookup to retrieve the matching record and display it in the form.
To display, insert, update, or delete data from a database, you make a connection to the database and then bind the fields on the form to the corresponding columns in the database table.
You can also use scripting to perform the Insert, Update, Delete, and Next/Previous navigation of records in the database.
Determining when to use a database versus, for example, an XML data file, is up to the application developer. You could have multiple data connections configured for a form (one to a database, one to an XML file) and bind individual fields to either of the data connections.
OLEDB is the only database connection that you can connect to from LiveCycle Designer ES. Through the use of the Microsoft OLEDB Provider for ODBC Drivers, you can also access databases identified by the ODBC data source name (DSN). You can use OLE drivers other than the Microsoft OLEDB Provider for ODBC, however the form must be certified in Acrobat before it will function at run time.
In Acrobat, security concerns dictate that you cannot specify an ODBC connection string by using the Driver=; syntax. Therefore, the client computer needs a DSN configured for ODBC connections.
If you are using external data sources in a form design that you want users to fill in Adobe Reader, you must set usage rights for the form by using LiveCycle Reader Extensions ES.
1. | Do one of the following tasks: |
• | Select File > New Data Connection. |
• | Select an object on the page. In the Object palette, click the Binding tab, and select New Data Connection from the Default Binding menu. |
2. | In the Name New Connection box, type a name for the connection. |
The name must be one word and no longer than 127 characters. The first character of the name must be a letter or underscore (_). The remaining characters may be letters, digits, hyphens (-), underscores, or periods (.).
3. | Select OLEDB Database and click Next. |
4. | In the OLEDB dialog box, set up your database connection string. If you need assistance with this setup, refer to your database provider documentation. |
5. | Select one of these options then click Next: |
• | Select the Table option and select a table as the record source. The list is populated with a list of all the tables available from the database identified by the connection string. |
• | Select the Stored Procedure option and select the record source from the list. The list is populated with all of the stored procedures available from the database. |
• | Select the SQL Query option and type the SQL query string. |
6. | Type your user name and password into the User and Password boxes and set the appropriate ADO recordset options. |
7. | Click Next. LiveCycle Designer ES validates that the connection to the database is successful and prompts you for credentials, if required. |
8. | Click Finish. The data appears in the Data View palette. |
To create a data connection to an OLE database
You may want your form to have access to information in a database. For example, you may want to retrieve data to populate a form based on a value, such as an employee ID, that the user enters when filling the form. When the user enters the ID number, it triggers a database lookup to retrieve the matching record and display it in the form.
To display, insert, update, or delete data from a database, you make a connection to the database and then bind the fields on the form to the corresponding columns in the database table.
You can also use scripting to perform the Insert, Update, Delete, and Next/Previous navigation of records in the database.
Determining when to use a database versus, for example, an XML data file, is up to the application developer. You could have multiple data connections configured for a form (one to a database, one to an XML file) and bind individual fields to either of the data connections.
OLEDB is the only database connection that you can connect to from LiveCycle Designer ES. Through the use of the Microsoft OLEDB Provider for ODBC Drivers, you can also access databases identified by the ODBC data source name (DSN). You can use OLE drivers other than the Microsoft OLEDB Provider for ODBC, however the form must be certified in Acrobat before it will function at run time.
In Acrobat, security concerns dictate that you cannot specify an ODBC connection string by using the Driver=; syntax. Therefore, the client computer needs a DSN configured for ODBC connections.
If you are using external data sources in a form design that you want users to fill in Adobe Reader, you must set usage rights for the form by using LiveCycle Reader Extensions ES.
1. | Do one of the following tasks: |
• | Select File > New Data Connection. |
• | Select an object on the page. In the Object palette, click the Binding tab, and select New Data Connection from the Default Binding menu. |
2. | In the Name New Connection box, type a name for the connection. |
The name must be one word and no longer than 127 characters. The first character of the name must be a letter or underscore (_). The remaining characters may be letters, digits, hyphens (-), underscores, or periods (.).
3. | Select OLEDB Database and click Next. |
4. | In the OLEDB dialog box, set up your database connection string. If you need assistance with this setup, refer to your database provider documentation. |
5. | Select one of these options then click Next: |
• | Select the Table option and select a table as the record source. The list is populated with a list of all the tables available from the database identified by the connection string. |
• | Select the Stored Procedure option and select the record source from the list. The list is populated with all of the stored procedures available from the database. |
• | Select the SQL Query option and type the SQL query string. |
6. | Type your user name and password into the User and Password boxes and set the appropriate ADO recordset options. |
7. | Click Next. LiveCycle Designer ES validates that the connection to the database is successful and prompts you for credentials, if required. |
8. | Click Finish. The data appears in the Data View palette. |