Technical Details (Oracle)
- Copy Space for Confluence (Unlicensed)
- Kenny Teves
Advanced WebCenter Sites Configuration
Workflows
Enterprise Inside Oracle WebCenter Sites depends on Sites workflow step actions to operate correctly. The source document must be in a workflow and two dedicated step actions must be added to this workflow. The SendForTranslation step action creates translation stubs of the source asset in Sites, and adds all of them to a child workflow. This child workflow exists primarily to prevent editors from accidentally editing translated assets when they should really be editing those assets in Enterprise. The SendUpdatesForTranslation step action is used to update the source content of an asset in Enterprise that was previously sent to Enterprise for translation (i.e. if an asset was updated in WebCenter Sites after it was sent to Enterprise for translation).
The default installation automatically installs a sample workflow for the source asset that looks like this:
| Process Name | Enterprise: Main Sample |
|---|---|
| Description | Â Enterprise: Main Sample |
| Start Step | Create |
| Sites | Any |
| Asset Types | Any |
| Roles | AdvancedUser SitesUser |
| Admin Roles | WorkflowAdmin |
| Process Deadline | Not allowed |
| Delegate Actions | No delegate actions are currently configured. |
...and a dedicated workflow for the child asset that looks like this:
| Process Name | Enterprise: Translate Child |
|---|---|
| Description | Enterprise: Translate Child |
| Start Step | Start Translation |
| Sites | avisports FirstSite II |
| Asset Types | Any |
| Roles | AdvancedUser SitesUser |
| Admin Roles | WorkflowAdmin |
| Process Deadline | Not allowed |
| Delegate Actions | No delegate actions are currently configured. |
Many users will prefer to integrate the step actions into their own main workflow. It should not be necessary (nor is it supported) to create a custom child workflow.
Customization Hooks
The Enterprise Integration has several customization hooks for adding implementation-specific logic. Using these hooks requires specific java interfaces defined in the Enterprise Jar. If you implement any of these interfaces, they can be hooked up to WebCenter Sites using a GSF Factory to implement the methods that return interfaces of these interfaces. For more information on using the GSF, see the GSF website (gst-foundation.org) and this blog post, http://www.function1.com/2013/04/how-to-add-your-own-dao-to-the-gsf-actions
Interface class: com.lingotek.owcs11g.report.LingoStatusReportAssetService GSF Factory method: public LingoStatusReportAssetService createLingoStatusReportAssetService(final ICS ics);
This interface is used by the Lingotek Status Report to add your own implementation of asset loading and translation lookups.
Interface class: com.lingotek.owcs11g.bulk. BulkUploadChecker GSF Factory method: public BulkUploadChecker createBulkUploadChecker(final ICS ics);
This interface is used when sending new assets to Enterprise. One method, boolean canBulkUpload(AssetId id, String subtype), is used to add your own logic for deciding if an asset should be sent to Enterprise by the Bulk Upload Utility. For example, maybe you only want to send a Page to Enterprise if it was created after a certain date. Also, if you are using GSF vanity URLs, by default the path of translation assets in WebCenter Sites is blank. This interface has a method for customizing the path of newly created translation assets. If you are using native WebCenter Sites vanity URLs, then this method is not necessary since WCS URL Patterns are used instead.
Next: Install FAQs