SiberSafe Core Features
SiberSafe provides a powerful access control mechanism that allows the administrator to control access to content at the fragment level rather than the whole document level. Permissions can be assigned to individual users, simple or nested user groups, documents, fragments, tasks, assignments, and user accounts. Once assigned, permissions are automatically propagated down through the user/group, content and workflow hierarchies.
SiberSafe supports DOD class "B" requirements for clearance and sensitivity levels. Every user or group can be assigned a clearance level and every object or folder can be assigned a sensitivity level. The user can only access any given object if its sensitivity level is lower than or equal to the user's clearance level.
SiberSafe supports multiple transactions to perform security and access control operations, improving cache scalability by removing any security reference monitor bottleneck.
SiberSafe supports the Windows Single Sign-On protocol. Users already authenticated by Microsoft Windows (i.e. logged onto a Windows session) can access the SiberSafe repository without re-entering their credentials.
Administrators can manage user credentials via Microsoft Windows facilities, such as Active Directory, so that user passwords do not have to be stored in SiberSafe.
Interface with an external LDAP repository for accounts, roles, and credentials; authenticate with LDAP external authentication service.
Web Access Services
SiberLogic Web Access Services enable XML content management over the Internet, via browser interface to specialized consoles including:
- Content management for accessing content
- Assignment management for accessing a virtual "to do" list
- Document builder for constructing documents from queries
- Supervisor console for control over workflow tasks
- Workflow definition console
- SiberSafe Author Dashboard
- SiberSafe Reviewer Console
Users accessing the SiberSafe repository via Web Access Services have the same up-to-date view of the repository as any other users. All workflow functionality is available, and all access to content is still mediated by the SiberSafe server, ensuring consistent and conflict-free collaboration.
SiberSafe Web Access Services can be located outside the enterprise firewall to allow remote access to the repository. HTTPS connections are also supported, for enhanced security of remote connections.
Users who opt for a desktop XML content creation tool may decide on the SiberSafe Desktop Client. In addition to the functionality available from the browser-based client, the desktop client manages the local working folder by tracking which files in the working folder have been superseded by newer versions in the repository, and vice versa. This client is useful for authors who need to work offline for long periods of time, providing a failsafe method of determining what has changed in the repository since the last time they connected. It is also useful for performing bulk operations on the repository. Note that the administration functionality is only available from the desktop interface.
Out of the box, SiberSafe supports any JDBC-compatible database, including Oracle, MySQL, MS SQL and Microsoft Access.
Multiple database write connections allow for multiple transactions to simultaneously write to the database.
Users can access the latest or any historical version of any document in the project.
Users can check XML or other content into and out of the repository to avoid authoring conflicts. Each user can safely edit checked-out content in their local working folder. Other users cannot override these edits until the content is checked back into the repository.
Document Centric Workflow
Document Centric Workflow is designed to automate the XML content production process.
In SiberSafe, workflow is defined as the progression of a task (or tasks) of a particular task type from state to state along predefined transitions triggering actions and notifications. A task remains in a state while a person assigned a role performs work on the documents attached to the task. A task exits from one state to another based on the outcome of the assignment. The assignee selects the transition (for example, accept or reject) that triggers actions and notifications. A transition places the task in the next state where it becomes the responsibility of the next assignee to complete the actions required of their assigned role.
SiberSafe allows teams to define different workflows for different task types. For example, a documentation team may have one workflow for generating new feature documentation and a different workflow for documentation bugs. SiberSafe also includes special support for managing translation tasks.
Roles, states and transitions can be arranged into simple yet powerful process implementations. With the ability to select which user or system events trigger automatic notification, administrators can select tailor the system response to workflow events that meets their audit and notification needs. In addition, user-defined triggers allow special processing at any point in the workflow.
As a task flows through the process, every contributor can view the task history, participate in task-specific discussion, and view attachments or operate on task documents. As the task completes its lifecycle, the history of who did what is preserved for future reference.
Documentation managers can define a task workflow and associate a workflow with any document. The manager assigns sub-tasks to different team members and, as the parent task moves through its lifecycle, they are automatically notified by email of their required contribution and the manager can easily track the documentation development process.
The manager can attach any file from the SiberSafe repository to the assigned task. Workflow module consoles enable task assignees to perform basic access operations with attached files: view, lock/unlock, check-in/check-out, get latest version. For translation tasks, files can be automatically selected from only those documents with an outstanding translation requirement.
"Strict" workflow option
When enabled, this new global option enables more efficient workflow management and task supervision. Only a single task can be in progress at one time, and all transactions performed by a user in the repository are associated with the task which is in progress. All user actions in the repository can therefore be tracked.
SiberSafe can create a new content stream based on the snapshot of an existing one, and is especially useful when supporting multiple releases of product documentation. The branch operation creates references to existing objects rather than replicating them, ensuring that the history of tracked documents, fragments, and entities is preserved in the branch. It also means that branching is fast, and uses minimum disk space.
Software Development Kit
The SiberSafe SDK, comprising C#, C++ and Java APIs, documentation and code samples, is available for download upon request. The SiberSafe SDK enables third party software developers to customize SiberSafe's look and feel, and to add custom-built functionality based on SiberSafe's powerful content management framework. SiberSafe Developer's Guide now available.
Command Line Interface
SiberSafe can execute custom-defined scripts from a command line prompt. SiberSafe CLI provides command line access to common SiberSafe operations, allowing users to add new files to the repository, create new folders and apply classification properties to multiple documents in a single batch using a custom script file. Available reports can now be run from the CLI.
Creation of stream configurations is streamlined via commands to:
- import a granularity
- create an empty knowledge model
- add knowledge storage schemes
- add inference rules
- recursively add folders
- add perspective definitions
- add ontologies
- set granularity on an XML document
- share a file or a folder
SiberSafe provides automatic performance-related issue reporting and activity logging via two diagnostic tools:
A configurable facility that triggers when a server request is not processed in certain period of time and periodically dumps server state into a disk file until processing of the request is completed.
Logging of requests received by SiberSafe Server and object usage conflicts caused by simultaneous access to the objects during operations that modify the repository.
The SiberSafe Stream Deletion utility makes it possible to remove repository streams that are no longer in use, optimizing the database and freeing disk space.
History maintenance utilities
The new History Compression and Inheritance Elimination utilities help minimize history-related performance degradation. You can choose the date from which to keep information about object changes and remove all preceding history records. The Inheritance Elimination utility enables history compression for databases initially created in SiberSafe 5.0 or earlier.
Staging and Deployment
SiberSafe's content deployment component, SiberStage, enables administrators to move content from the repository to external servers, either web servers or build systems.
SiberStage is designed to allow web developers to deploy changes to a web site from a central location. It is fully configurable and runs on any client that supports Java applications.
A SiberStage client can periodically check with the repository to see if any files have changed in the development stream, extract any changed files and process them according to the SiberStage client configuration - for example, it could launch an XSL translation to convert the XML files to HTML, and place all deployed files in the file system, available for access via the web or application server. The client can also handle all the server restarts, registry updates, etc. associated with deploying application components.
SiberSafe requires password specification on user accounts, to ensure that all repository operations are secure and can be traced to the user who actually performed them.
Oct 1, 2013
SiberSafe 7 released featuring new built-in XML editor, small footprint default database engine
Sep 1, 2013
Styler 7 released with major ease-of-use features, a new DITA layout template and powerful tagless XPath context support
Jul 31, 2013
SiberSafe CMS 6.4.1 build 2019 is out with many exciting new features for DITA, S1000D, MIL-STD-2361 and other applications.
Feb 28, 2013
SiberSafe 6.4.1 is out with about 80 new features and over 300 enhancements, both generic and standard-specific, including S1000D, DITA and MIL-2361-related ones.
Nov 30, 2011
SiberLogic signs an enterprise license agreement for its SiberSafe CCMS with Ericsson, the market leader in telecommunications technology.
Mar 27, 2011
SiberSafe XML CMS now offers the XQuery index and search capability as well as programmatic access to the XML metadata through a variety of interfaces, such as XML:DB, for systems integration and other purposes.
What our customers say:
"The unprecedented flexibility of the SiberSafe solution and the responsiveness of SiberLogic’s team help us to successfully manage the conversion of technical manuals into any of the evolving standards of the Department of Defense Community.”
"We use SiberSafe in a highly collaborative and complex global environment where it has proven to be both a reliable and flexible CMS. Streamlining the workflow from concept to deliverable with features such as conditional and multi-channel publishing has made us better at what we do. We've run SiberSafe through the paces, but SiberLogic have always been ready to turn whatever was hanging us up into the next great, new feature."
"Our experience with SiberLogic during our implementation has been very good. The quality of responses we receive go beyond simply correcting any issue but also provide alternatives and best practice suggestions."
Product Information Line
If you have a specific question about our technology, please call our product information line at 905-761-7334 ext 233 from 9am to 5pm EST.