RoAccess provides a large number of features and
capabilities that the Rochade Repository does not support. RoAccess
allows the Rochade Repository to become much more powerful that as provided
by ASG. We extend the amount of metadata that can be stored
in your Repository.
General Topics
RoAccess is utilized internationally. Its maturity
is apparent in its long list of features and functionality.
-
WEB Server front end to a Rochade Repository. Click
for a sample.
-
Runs on all Windows and Unix platforms. Can be accessed by MS Internet
Explorer or Netscape.
-
It comes with both English and German language files. New language
files (like Spanish, Italian, etc. took only 3 days to create).
-
Your data can be accessed with an organization's Intranet or by the world
via the Internet. Anyone with a WEB browser can view and input Rochade
data, with many security options to protect your Repository.
-
A great many users can share only 1 Rochade license, whereas each Autopilot
user needs his own license. Greatly reduces the number of required concurrent
client licenses. Less costly.
-
Completely cross-hyperlinked. Any referenced or referenced by items can
be displayed with a simple mouse click. Finding and navigating data is
now very easy and fast. With RoAccess, you see your data in context,
not as separate pieces of data.
-
Easily select between lists of different Rochade servers.
-
Easily select different databases for each Rochade server.
-
Versioning , extended data-types and BLOB support.
-
Automatic document versioning. You can keep 100 versions of any document
automatically. Rochade versioning does not do this.
-
Can do full multi-ItemType searches and namespace searches utilizing multiple
attributes to search on.
-
Path reports give a large number of options
-
Spreadsheet reports allow both WEB presentation and direct download to Excel.
-
DBA utilities allow you to correct and handle many Rochade problems and
deficiencies.
-
See only the ItemTypes that have Items. Why show all ItemTypes if many
have no Items, like WEB Access does.
-
RoQuery allows you to use a general purpose query language to define simple and
complex queries over multiple ItemTypes, displaying multiple attribute data of
the matching Items, and can be displayed in a WEB and a Windows Explorer style
output.
-
FULL Source code is delivered to facilitate site customization.
-
Contains all the necessary WEB pages, CGI-BIN scripts and rpl procedures.
-
Select Subject Areas or Projects from a list
-
By default Rochade gives new users FULL ACCESS. RoAccess can restrict new
users to read-only as an option.
-
Uses Rochade security
-
You can define what Item Types, Items down to the attribute level are visible/editable
on a PER USER basis.
-
Split screen: ItemTypes on the left and their
items on the right in scrolling panes.
-
Embedded on-line Help with graphics and screen captures
-
Can have multiple browse/update screens up for comparing and entering multiple
items at the same time.
-
A Site defaults/preferences file with incredible capabilities for user
customization..
-
Displays Item &OWNER, &STAMP and other "hidden" attributes if desired.
-
Maintains an optional Audit Log for Last Update information: the user who
did the update, which client was used, and the date/time.
Very user friendly messages. When an operation is not permitted, you
are told exactly why. For example, if an attribute of an Item is Information
only, double clicking on it in Autopilot to edit it results in nothing
happening, and you don't know why nothing happens. With RoAccess, you are
told what is not permitted and why. No more guessing. Another example:
if an Item Type is defined such that only the owner, creator, of the item
can later edit it, if someone else tries, the message not only states he
is not the owner, but is displays who the owner is. Perhaps that person
will perform your update for you. Autopilot provides you none
of this important additional information.-
Has utilities to help determine the cause of slowdowns, like CPU utilization and
network speeds.
-
When many Items are displayed, an index of letters, like A B C, allow you to
click on them and go directly to those Items.
RoAccess Extended Metadata
For some screen captures and detailed information on RoAccess Extended
Metadata, click
here.
There are three types of attributes that Rochade supports: Text,
Value and Blob. Did with Rochade you know you cannot define a
TYPE for an attribute, such as Integer, Float, Character? You
cannot specify a data entry PIC, such as I4, F10.2 or C30.
This would be metadata, but Rochade does not have a way to store it.
When you display a data entry field, how wide should the field be?
Should it be constrained to be INTEGER? None of this information can be
stored in a Rochade Repository, but it is absolutely critical.
To address this shortcoming, RoAccess created Extended Metadata.
It allows you to store a great deal of additional information about your
attributes. Below are some examples:
With RoAccess you can define a TYPE and PIC for each attribute.
For example, with Rochade you can define an attribute as a TEXT or Value
attribute. But with RoAccess you can further define it to be INTEGER
with a PIC of I4. You can define it as CHARACTER with a PIC of C30.
When these attributes appear on a data entry form, RoAccess will automatically
create them the correct size and enforce the data content of the field.
Example, suppose there is an attribute called "FIELD_WIDTH". If
you use standard Rochade, if you want to enter a value, you get a wide
multi-line entry window. However, with RoAccess you can define it
as INTEGER and a PIC of I3, and the data entry field will be exactly 3
characters wide. This is what you would expect of a Repository, but
Rochade does not support it. So RoAccess does!
Suppose you have an attribute called "COMPANY_ADDRESS". WIth RoAccess
you can define it to be 40 columns wide, and starting with 4 lines and
able to grow to 9 lines maximum. Not with standard Rochade.
Rochade supports links, and you can have link qualifiers, which are
quite powerful. A link qualifier can provide additional information,
such as why the link exists. For example, if you have a link attribute
that links to an ItemType of PERSON, you can put in the link qualifier
the relationship of the person, such a EMPLOYEE, PAST_EMPLOYEE, SOFTWARE
CONTRACTOR. Then you can later search the links based on the link
qualifier. But you yourself have to remember the which are the correct
link qualifiers for each link attribute, of which there could be thousands.
Your users can't remember all that, and furthermore Rochade will not store
a list of allowable link qualifiers. You can enter anything you want.
One person could enter EMPLOYEE, another could enter "Person Employed",
another "PROJECT HEAD", so every link qualifier could be different.
However, with RoAccess you can define the list allowable link qualifiers
and
the data entry person must chose from a drop down list. This ensures
the data to be complete, accurate and consistent, which is imperative in
a Repository.
Rochade does not support the concept of "Link Cardinality". You
can enter as many links in a link attribute as you want. But suppose
your Entity Relationship Diagram defines a maximum cardinality of 3 links.
Rochade does not support this. RoAccess does. In the
RoAccess Extended Metadata you can, for example, define for a link
that it will allow up to 3 links. Further you can declare whether
this maximum is mandatory (not permitted to exceed) or you can exceed it
with just an advisory message.
With RoAccess you can also support non-sorted Links. The
order of the links may be important, and RoAccess will allow you to add,
delete and update based on the order you specify.
For more detailed info on the amazing ways that RoAccess can handle
links, click here.
User Friendly ItemType Business Names- can have spaces, mixed case, and make
more sense
User Friendly Business Attribute Names - can have spaces, mixed case, and
make more sense
User Designed Display Forms - create forms with Netscape Composer
, FrontPage or other HTML editors.
Display Order. With standard Rochade, you can specify the
display order for all Text, Value and Bob attributes, but you cannot mix
them. You cannot have a value attribute in between two Text attributes.
The Text attributes come first, then the Value attributes then the Blobs.
However, with RoAccess you can specify any display order you want, freely
mixing all attributes types. To show how easy it is to set the display
order, click
here.
The Rochade DEFINITION attribute is defined to be one line of 80 characters.
But Rochade does not enforce this, and many Rochade applications do not
follow this rule. RoAccess allows you to optionally enforce this
rule. The "long form" displays are presuming that the DEFINITION
is one line. If you enter more than one line, your "long form" displays
may not look right or contain the information you want. With RoAccess
you have more control and uniformity of your data.
Built in Trace. Web Development is a but unusual in that the
application is running on one machine, but your browser is running on another.
If you want to debug a new application you are creating, how do you do
it? RoAccess comes with a build in trace/debug package that you can
turn on at run time. While the trace runs on the WEB server machine,
its output is on your PC. This trace facility has been invaluable
in finding and documenting many actual Rochade bugs. About 9 of every
10 "bugs" that are reported to Support are actually Rochade problems, and
the built in Trace is an easy way to find and document the problem.
Early Release/Patches. Every time RoAccess adds a new feature
or corrects an error, it is put on the WEB via our Early Release/Patch
system. This way, if you don't want to wait until the next release
of RoAccess, you can get those new features immediately! Also,
if an error is corrected for one user, it is then on the WEB so it is available
for all users. You don't have to wait months for new features and
patches like you do with some vendors. Click
here to view the standard DownLoad page where you can get the latest
versions of RoAccess, RoLoader and RoPages. Click
here to view the Early Release/Patches page.
Long Identifiers. Rochade unique identifiers have a maximum
length of 32 characters, which is way too small. Rochade for years
has been promising to increase the length to allow "long identifiers",
but has yet to make good on the promise. For example, if you have
an ItemType called ORA/FIELD and you want the unique key to be the table
name, DOT, and then the field name (like PERSON.SALARY), with Rochade you
can't do it! The reason is the table name and the field name may
be each 16 characters. Concatenating them and a period exceeds 32
characters. However, for years RoAccess has supported Long
Identifiers in excess of 200 characters. If you need long identifiers,
you need RoAccess. For more detailed info on Long Identifiers, click
here.
Frames/No Frames. You get to choose which works best for you
and your users. If you have a large monitor and high resolution,
frames works well, because you can get multiple pages on the screen at
the same time. However if you have a small screen or smaller resolutions,
frames make each page small and not able to let you see everything at a
glance. RoAccess lets you switch from frames to no frames.
Buttons vs. Hyperlinks. When selecting an ItemType or Item
you can specify whether you want to click a button or a hyperlink.
Buttons look neat. Hyperlinks will show by different colors which
ones you have recently used. Different users have different preferences.
With RoAccess you choose the display style.
Many browsers and versions supported. RoAccess supports an
extremely wide range of browsers and versions. Each browser version
corrects some bug, creates others and sometimes just acts differently.
RoAccess, because it has been around so long, is able to handle this wide
range of browsers. If you clients have a number of new and
old browsers, you need RoAccess.
Default User. For the convenience of your users, you can have
a "Default User" automatically inserted into the Login USER ID field.
For example, when you start up RoAccess, you could have GUEST automatically
appear on the Login screen. This is a configuration option.
Default to Read Only. If you create a new user in Rochade,
it gets FULL ACCESS by default. That is definitely NOT what you want.
A RoAccess configuration option is all new users by default become read
only. This makes your Repository much more secure.
Hide Buttons. RoAccess comes with a great deal of functionality.
However, if some of your users or clients are non-techincal you might like
to enable only the very few buttons those users need, and not be confused
by the others. Each RoAccess button can be turned on or off using
a scripting language that can test the user, subject area, user class,
etc. So all the button might show for you, but only a few for
less technical users. This is user friendliness.
Standard Buttons. RoAccess comes with its own set of stylistic
buttons. But if your company has a different look and feel, you can
create and substitute your own extremely easily. RoAccess was
designed to integrate into your environment.
User Buttons. If you create new applications, you can instruct
RoAccess to display your new button on standard screens so when it is clicked,
your application is run. Your application will look like it
shipped as a standard part of RoAccess because its button will be along
with the other buttons.
Message of the Day. When a user logs on, you can display an
optional message. It can inform of important events, like when specific
data will be loaded, or when the Repository will be down for maintenance,
or giving phone numbers to call for support. You specify this message,
and you can enter hyperlinks and graphics besides just text.
When creating a link with Rochade, you are allowed to specify a Item that
does not exist. That will create an inactive/referenced Item,
which usually is NOT what you want. However, with RoAccess you have
the option in RoAccess Extended Metadata to require links to go to only
existing Items, and the user will NOT be allowed to type in any name.
Document Storage and Distribution. RoAccess was designed to
store and deliver documents of any type to your PC. They can be Excel,
MSWord, ABC Flowcharter, graphics of any type, etc. By clicking a
button, RoAccess will download the file to your PC and automatically start
the correct application so you can view or process that file! Some
companies have stored over 10,000 documents in Rochade and use RoAccess
to deliver them to their employees. Rochade does not come with this
capability. RoAccess does.
Item Type List Display Screen
For some screen captures of a typical Item List screen, click
here.
Some Repositories may have thousands of ItemTypes. Since their names
can only be 32 characters, several because of abbreviations may look very
similar. How will you know which one to use? With RoAccess
it is easy. Next to each ItemType there is a "blue info ball" that
if clicked displays all the RIM's internal metadata about that ItemType.
This is REALLY helpful.
You can switch Subject Areas or Projects at any time
It lists all the ItemTypes in the Subject Area that you are allowed to
see
It highlights in blue those ItemTypes enabled for mixed case Item Names.
You can enter a wildcard to help select Items
You can select the "class" of the Items you want to list: Active, Inactive/Referenced,
etc.
You can select the "long form" of Item List were the long form attribute
is also displayed.
If you are the LT or LTS, you can also see "system ItemTypes" such as AP-TEXT-ATTR.
This allows you to browse throughout the Rochade internal metadata to analyze
you system and pinpoint many classes of Rochade errors.
Item List Display Screen
For some screen captures of a typical Item screen, click
here.
It lists the Items of the selected ItemType that matched the wildcard qualifier,
if any was given.
You can click on a button or specify clicking on hyperlinks for each Item.
Your preference.
If there are many Items, a Quick Jump Index appears that will allow you
to jump to be beginning of the A's, B's, C's etc. If you have 1500
Items listed, this Quick Jump Index is a real time saving convenience.
If too many Items would be listed, you are given a chance to refine your
wildcard qualifier.
The Item Display Screen
The screen that displays an Item contains a great number of features.
This lists only a small fraction. For some screen captures of a typical
Item screen, click here.
No data entry is possible in Display Mode.
All allowable data for an item is displayed. This allows viewing everything
about
an item at a glance.
Data display is condensed. Only attributes containing data are displayed.
An item type may have 50 attributes, but if an item has only 10 of them
populated, then only these 10 will be displayed. This reduces clutter by
not displaying empty attributes. When in Edit Mode, all attributes
are presented.
Fully cross-hyperlinked. All items automatically show referenced and referenced-by
items.
Stored documents are downloaded and automatically run in their applications
Graphics, such as a person's picture or product
pictures, can be displayed.
Sound, video, pictures and many more documents
can be stored WITH the items.
Automatic spreadsheet report generator. Select
the item type and which attributes to display. Then the spreadsheet is
displayed in one of two ways:
-
HTML Table (visually looking like a normal spreadsheet). Click
here to see one.
-
Tab delimited data, that can is automatically downloaded and loaded into
any spreadsheet, like Excel.
-
For more info on RoAccess spreadsheets, click
here and here.
Link Attributes are displayed as hyperlinks, displaying both the target
item type and name.
Embedded HTML tags in text attributes, such
as http:, ftp: and mailto:, are show as hyperlinks and are activated with
a mouse click. Click to see example of
URL's embedded within a text attribute.
Multiple browser screens can be up, displaying
multiple items and logged in as different users.
Full security is enforced. You may be allowed to edit certain attributes,
only view others and not even see other attributes. All this is enforced
by RoAccess.
If your profile says a particular attribute is information-only
to you because of a Subject Area or user class profile, even though you
are in Edit mode, that attribute will be merely displayed and no editing
of that attribute will be possible.
If your profile says a particular attribute is not even viewable
by you, the screen will not have that attribute appear at all.
If you follow a hyper-link to an item where you are not permitted to view
that item, but only be allowed to know it exists, you will be denied access
to that Item, and you will be told so and why.
You can switch between Display and Edit Modes, based on the permission
you have.
If you type in a URL, like http://www.roaccess.com or mailto
: support @ roaccess.com
or ftp://www.roaccess.com/pub/perl.exe they automatically become
active hyperlinks that the users can click. It will display that
page, pop up a mail program (pre-addressed), or automatically download
a file.
Rochade requires that each Item have an owner. Much of the Rochade
security is based on the owner of the Item. RoAccess will advise
you when an Item does not have an owner, and will allow you to set the
owner. Standard Rochade will not tell you that the OWNER field is
missing. RoAccess will.
Select a value from a list using a popup list box
Full support for SEQuence fields. This is a list box, where
the allowable values change based upon the current values. Given
a starting state, there will be only certain allowable values.
(Note: you do NOT have to be in a "project" to use SEQ fields in RoAccess)
When you first create a new Item, RoAccess will automatically insert any
default values into the various attributes. Further, RoAccess identifies
in red each default value so you can determine if it is suitable so you
can change or delete it if desired. Standard Rochade will insert
the default values, but does so silently. Also with RoAccess if you
create an Item but don't get around to entering the data until later, RoAccess
remembers that that is the first time to edit the Item, so the loading
of the default values will take place them.
Attribute Information. Rochade stores some information about each
attribute in its RIM. Suppose you forget exactly what an attribute
is used for or what it means? With RoAccess, no problem. THere
is a "blue info ball" next to each attribute, so if clicked it will interrogate
the Rochade metadata and display everything that is available, like a description,
range validations.
Validate LISTs. You can select a value from a list of allowable values.
If you bulk loaded a value not in the list or the attribute has a value
from a prior time that is not in the current list of allowable values,
RoAccess displays a red error message saying the data is invalid and not
in the current list
If you are in "Edit Mode", and you do not have permission to edit an attribute,
it is displayed but no entry field is provided.
Each link attribute has hyperlinks to the linked to Items. Clicking
its hyperlinks immediately displays THAT Item.
At the bottom of each Item Display is the "Referenced By" section.
It shows all the Items that have links to it (refer to it via a link).
By clicking these hyperlinks, you immediately display those Items.
When a field is validated, it is done as you enter. You do not have
to send it to the database to see if the validation failed.
You can tell RoAccess not to display certain attributes without having to resort
to user profiles. The DEFINITION attribute is many times garbage put there
by the loader, and should not be displayed. RoAccess can do this.
User friendly business names for ItemTypes and Attribute names. You do not
need to go through a "discovery" process.
You an user your own Icons rather than ours. This gives your RoAccess a
custom look and feel.
You can add new screens to your RoAccess without any programming
You can change many defaults.
You can change the way many things on a standard screen are displayed.
You can change the text on screens to match what your users would prefer with
merely a text editor. The "User Language Files" allow you to make these
screen changes so that future RoAccess upgrades will not overwrite your changes.
For example, you can have "Table" display instead of "ItemType" on all the
screens, if your users prefer. Every phrase on every screen can be
overwritten.
There is an XML Import service for Windows facility that comes with RoAccess.
When creating a new Item, any blanks in the name are converted to underscores.
Rochade does not allow blanks in an identifier, and automatically changing
them to blanks makes RoAccess much easier for non-techincal users who don't
want to have to remember a lot of rules that Rochade imposes
Embedded Document Storage
RoAccess makes storing and retrieving files and graphics a snap.
Some companies store more than 10,000 documents on-line using RoAccess
for general distribution. RoAccess lets you do thing with Rochade
you might not expect.
Graphics and other documents can be stored with EVERY item of all item
types. Click to see a document with sound and movie files.
Stores virtually any kind of file format: binary or text
Specially named attributes automatically store/retrieve files
File storage attributes can be put into ANY item types
Attributes that are populated with files show icons for the type of file
Click on the icons to download the file and automatically start up its
application
Documents are stored inside the Rochade Repository, not separately, and
can be uploaded from a Windows or Unix workstation.
RoAccess supports just about every file type
If you have a blob in an Item that is used to store images, like a picture
or logo for instance, you have the choice of display the image automatically
when the Item is displayed (most convenient) or having an icon display
that must be clicked to view the image (perfect for low bandwidth connections
or employees who work from home using slow modem connections.
Blob attributes can be locked by RoAccess at the attribute level.
Rochade locks at the Item level. But for blobs, which store files
which many people may be editing, RoAccess locks at the attribute level.
For more information on how Blob Attributes can be reserved, checked out,
locked, and released, click
here.
DBA Utilities
RoAccess comes with a number of utilities and special functions to make
your life easier:
ItemType Statistics: analyzes in great detail the number of Items and type
of Items for every ItemType in your Subject Area. This is extremely
useful to finding which Itemtypes have not been loaded yet, are only partially
loaded, or have inactive Items, which usually means misspellings or missing
data
Show HIdden Instances. HIdden Items are a real headache sometimes.
If an Item appears in different configurations, a delete may "hide" it.
Later you can't find the Item, but you know it is there. This utility
will let you find all these annoying, but hard to find hidden Items.
If you have development, test and production versions of your repository,
how can you tell if you always have the most current stored procedures
(including user created stored procedures) and have you copied the latest
versions to the production repository? This utility make it easy.
A utility to show the version and patch level of every RoAccess family
related product.
Path Reports
RoAccess full graphics, interactive path reports are wonderful.
The automatic layout from top to bottom or left to right lets you view
your relationships the way it makes sense to you. You can define
a shape, color and even a special image for each ItemType symbol displayed,
which makes the graphics very intuitive and easy to use. Even for
non-techincal users. There are many different ways to display the results
of Path Reports.
Stored Reports
You can create some incredibly powerful reports and keep them as stored
procedures. RoAccess add Extended Metadata to the stored reports,
and even lets you output them in HTML if you desire. THis means your
reports can have formatting, color, bold, images and more.
User Preferences
There are a number of preferences a user can set.
A user can specify a "user cascading stylesheet". This can give a
custom look and feel, different fonts, background colors, etc.
Item List maximums to display before asking you to re-qualify with a wildcard
Editing Preferences. When entering a great deal of repetitive data,
you might want to automatically switch from Edit Mode (for entering) to
Display Mode after you save the data, so you can view it just as a user
would see it. Or you might want to stay in Edit Mode.
This is a great time saving feature and convenience.
Set your default Subject Area or Project.
User and System Cascading Style Sheets
RoAccess utilized HTML Cascading Style Sheets. These are similar
to a MS Word stylesheet, where you can define fonts, sizes, colors, background
colors and indentation offsets. The power in style sheets is that
you can override all or just one parameter. This allows you to customize
RoAccess to look more like your other applications.
RoLoader
RoLoader makes loading data into Rochade really easy. But it also
allows you to make sure that your data is correct and valid, which is extremely
important. Some loaders will load anything, including bad or invalid
data, and expect your to later to somehow find the problems and correct
them. RoAccess, on the other hand, allows you the option of identifying
and correcting problems in advance, letting you load only valid data.
Once your users start seeing bad data, they will start to not not have
faith in your Repository because they will say, "the other data was bad,
this data might be bad too, and I can rely on it." RoLoader can help
make sure you users always see valid data.
Many Rochade loaders just load the data, and you don't get to see what
you loaded until it might be too late. However with RoAccess, you can first
view the data in Excel (or other spreadsheet), find and correct errors
or make other changes. Once you are satisfied with the data, then
you can load it.
RoLoader loads tab separated data. The is probably the worlds most
common for of data interchange. You can load spreadsheets (like Excel,
123, etc.), simple text files or output generated by a program.
It loads the file on your PC up to the Rochade Repository
Load multi-line text attributes.
Load value and link attributes
Bulk load files into Blob attributes.
An option to load links to non-existing Items
An option to load links to non-existing ItemTypes! Very handy.
An option to load links only to existing Items
All validations are optional, and can be turned on or off individually.
Validate a numeric range
Validate that the link qualifier is one of the allowable ones (only in RoAccess,
not Rochade)
Validate against a PIC. If the PIC is C40, then the value must be
40 or fewer characters. If it is I4, then the data must be
an Integer and a max of 4 digits.
You can load only one or more or all columns of data. You don't have
to load the entire file.
You can load only a few rows of the data file, like lines 100-200, or you can
load 10's of thousands.
You select which columns to load and validate all with point and click
Given a list of ITems, you can bulk delete them.
If you loaded data, later found an error, you can just reload the data.
You also have the option of just deleting the Items first, then re-loading
them. This is very powerful.
Data files loaded are retained for historical purposes.
Only specific users are allowed to bulk load, as a security measure.
RoQuery
Only RoAccess has a standardized query language that can produce reports.
RoQuery is a optional product.
On-Line Rochade Command Interpreter
Allows a DBA to execute highly specialized Rochade instructions in real-time.
Useful in diagnosing database problems.
Error Checking
Perhaps 1/3 of all the RoAccess code is constantly checking for data inconsistencies,
Rochade errors and what is returns meets reasonableness criteria.
This is to ensure that any Repository data or metadata problems can be
quickly identified and corrected. About 90% of all "bugs" reported
to support are in actuality Rochade problems, stemming from various data
and metadata corruptions, or profiles or RIM incorrectly configured.
Most software presumes everything is OK, and you may not even know there
is a problem until it is too late. Not RoAccess. RoAccess wants
your users to feel absolutely confident that the data they are viewing
is correct and complete. If there is a data or Repository problem,
you want to know about it.
Security
You can customize your security model to fit your organizations requirements.
Many companies have done this because source code is provided.
Stand Alone RoLoader
RoLoader comes in a "stand alone" version for users that do now own full
featured RoAccess. It comes with a stripped down RoAccess. You can do
everything needed to load data. However, you cannot:
- Access ItemTypes other than RoLoader
- create, view modify or delete non-RoLoader Items
- display spreadsheets
- display path reports
- display general reports (RoQuery)
- use the DBA Utilities
- use the command interpreter
- do graphical representations of data
- use drag and drop for group collaboration.
- repair database corruptions caused by Rochade
- analyze Rochade malfunctions or do metadata corrections
- add new applications
- do full searches or namespace searches
- use the mass renaming utilities to correct ASG scanners namings.
- creates screens with FrontPage
- manipulate Hierarchical or Virtual Hierarchical Subject Areas
|
Normal WEB Server Security
-
You decide the degree of access security
-
Use the standard capabilities of your WEB server and firewall
Rochade Security
-
Rochade username and password are supported
-
In general, you only see what you are supposed to see and update what you
have authority to.
-
RoAccess utilizes enhanced Rochade security measures.
-
Application/Item Type Profiles are enforced. You can specify at the Item
Type level if creates, deletes or renaming is permissible, or have Item
Types not even appear
Attribute level security: Mandatory, Info, Optional or "not displayed"
Optimization
As the numbers of your internal and external users and clients increase,
can RoAccess handle the increased numbers of accesses? Absolutely.
First, you can have additional RoAccess servers (for no additional cost).
RoAccess comes with in-memory Daemons, constant connect servers and
source pre-processors. You also have RoPages, the highest speed Rochade
caching available. There are companies that have literally
thousands of RoAccess users!
