1 / 8

Configuration aware document generation

RPE document specifications now enhanced with data source property, allowing configuration URI specification. RPE adds OSLC Configuration HTTP header to GET requests. Customize configuration URI value dynamically. Use OSLC delegated UIs for configuration discovery. Embedded web browser for user-friendly selection. Easy template design with no URL changes. Configure data sources effortlessly.

aronnie
Download Presentation

Configuration aware document generation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Configuration aware document generation • RPE document specifications are enhanced with the addition of a data source property that specifies the configuration URI. • If this variable is defined RPE adds an OSLC Configuration HTTP header to every HTTP GET request made to the data service. • This header will be processed by any configuration-capable data service • The global configuration property value may be changed by scripts in the document template during document generation. • RPE allows users to set/discover the value of the configuration URI. • OSLC delegated UIs are used for the discovery process • RPE discovers the URL of the OSLC delegated dialog by reading the service provider resource of the configuration service. • RPE is enhanced with an embedded web browser that can display the OSLC delegated dialog for the user to select the configuration. • Existing templates DO NOT have to change and neither the URLs used to configure the data sources • Template design does not change, it DOES NOT become more complex

  2. Configuration selection – the discovery process • Step 1: provide RPE with the URL of the rootservices document of the configuration provider

  3. Configuration selection – the discovery process • Step 2: select the OSLC Configuration provider and the OSLC Selection Dialog you want to use • Depending on the selection status of the “external browser” checkbox you will proceed to steps 3a or 3b

  4. Configuration selection – the discovery process • Step 3a: use the picker in the embedded browser in RPE • checkbox from step 2 was not selected

  5. Configuration selection – the discovery process • Step 3b: use the picker in an external browser • checkbox from step 2 was selected

  6. Configuration selection – the discovery process • Step 4: complete the wizard. The selected value is set in the “Configuration-Context” property of the data source

  7. Document generation – Configuration 1 (older)

  8. Document generation – Configuration 2 (newer)

More Related