If you need to manually configure the link between the XLANG Scheduler application because something happened to your default file DSN, or if you create another COM+ application to host XLANG schedules, you will have to provide the DSN information necessary to allow the XLANG application to know where to hydrate its schedules.You might also need to create multiple XLANG Schedule persistence databases to separate records for different vendors or business partners. Follow the path outlined previously and as shown in Figure 2.28, this time select the XLANG tab. On this tab you will have the options to Create DSN, Configure DSN, and Initialize Tables. If you created a new database within SQL Server to use as a persistence database, follow these steps to complete the configuration:
1. Select the XLANG tab for the component that will host the XLANG schedules that will be hydrated to the new database you created.
2. Click Create DSN.This will launch the ODBC DSN wizard. DSN files are limited in that they do not support connection pooling, but they are easier to share in a networked environment. Typically, System DSN provides all the options you need.Walk through the remainder of the wizard screens selecting your database; in most cases, you can use the defaults.
3. After you finish creating your DSN, you are not yet done—the database is still empty.We must click Create Tables on the XLANG tab to prepare the data structures that will hold our hydrated schedules. Do not select this option for an existing database, because it will destroy all the current data.
Was this article helpful?