Page History

...

• COTS Installations: npm, node.js, loki.js
• S4S must be installed in the target mode (use S4S mkcfg).
• Start the S4S service (S4SStart)
• Required information:
  
  • The port associated with this mode's instance of S4S (usually 30XX)

Use Cases

Tips & Warnings

Configuring S4S

Section

Column width 50% Section There are 2 application configuration variables in the Data Access GUI that govern its interactions with the S4S database: SUBSCRIPTION_ENDPOINT_URL DEFAULT_FULFILLMENT_FREQUENCY Image Added SUBSCRIPTION_ENDPOINT_URL (xs:string) allows the Data Access GUI to perform database operations using HTTP requests. The format of this value is http://x5oml01:30XX/todos DEFAULT_FULFILLMENT_FREQUENCY (xs:integer) allows the operator to generate subscriptions without having to specify the fulfillment frequency each time. Column width 50% Image Added  Image Added

Use Cases

Viewing Subscriptions

The "Subscription Management" tab allows an operator to view existing subscriptions.

Clicking on a subscription will reveal the details of its processing instructions in the lower half of the window in a readable format.

Image Added

When no subscriptions are present in the database, a message like this might be received:

Image Added

Creating a Subscription

Edit Existing Subscriptions

Cancel a Subscription 

Tips & Warnings

• If unable to connect to the database or retrieve subscriptions, relevant error messages will be shown in the table.
• When troubleshooting, use both the firefox webpage debugger and the Data Access GUI log file (DA_Gui.log)
• As previously described, the OPeNDAP OLFS must be active in the target mode before starting.
• If no data is found for the target collection, make sure it has been ingested properly.
• If a form for the configured collection cannot be uploaded, verify that the service configuration is correct and that the collection data has been exported to CMR.

Related

• See the FormUpload.rb and DataAccess GUI Form Upload pages for further guidance.