The following example tests whether the publication is connected to a data source and, if it is not, specifies and connects a data source to the publication. (Note that PathToFile must be replaced with a valid file path, and TableName with a valid data source table name, for this example to execute properly.)
The JNDI location of the database persistence provider. This JNDI location represents a valid data source defined for the application or for the OC4J instance.
If you use the RDSServer.DataFactory object on your Internet Web server, remember that doing so creates a potential security risk. External users who obtain valid data source name (DSN), user ID, and password information could write pages to send any query to that data source. If you want more restricted access to a data source, one option is to unregister and delete the RDSServer.DataFactory object (msadcf.dll), and instead use custom business objects with hard-coded queries.
If you select Database Store, you must select the JNDI location of a valid data source from the drop-down menu. For more information, see Browsing the JNDI Namespace for an OC4J Instance.
Enter a name for the new resource provider in the Resource Provider Name field. Select the JNDI location of a valid data source from the Data Source JNDI Location.
No valid data source is specified for connection. Specify a valid data source to proceed.
接続に有効なデータ ソースが指定されていません。有効なデータ ソースを指定して継続します。
Valid Data Source Header Field Types
有効なデータ・ソース・ヘッダー・フィールド・タイプ
Conținut posibil inadecvat
Exemplele au rolul de a te ajuta să traduci cuvinte sau expresii corect si adaptat la context. Nu sunt selectate sau validate manual, așadar pot conține termeni inadecvați. Te rugăm să raportezi exemplele pe care le consideri inadecvate. Traducerile vulgare sau colocviale sunt în general marcate cu roșu sau cu portocaliu.