| Q: |
Can I use Trinem Project Manager to copy projects between brokers? |
|
| A: |
Yes, this is its primary purpose. Trinem Project Manager
creates a single binary file containing everything
required to restore the project on a second broker
instance. |
| |
| Q: |
Can I use this to backup individual projects? |
| A: |
Yes you can, Trinem Project Manager is a good
alternative to CA-SCM's har (archive) and hrt (restore)
utilities. You can backup a project to a single binary file
and restore that project at any point. You can even
restore the project back to the same broker instance
without removing the original project - Trinem Project
Manager takes care of renaming the project and any
forms to ensure a seamless restoration. |
| |
| Q: |
Can I use Trinem Project Manager to support multi-site
(off shore) development? |
| A: |
Yes. Simply export a project from your off-shore site and
import into your on-site system. You can then crossproject
merge packages between the newly imported
"off shore" project and your main development project. |
| |
| Q: |
My user base is spread across brokers with some users
having access to one broker, other users access to
another and some users having access to both. How is
audit history retained when I import to another broker? |
| A: |
Trinem Project Manager exports details of all referenced
users. During import, checks are made as to the
existence of these referenced users in the target
database. If users already exist then the object ids of the
referenced users are updated automatically to point to
these existing users. If users that are referenced do not
exist in the target database they are created
automatically. Command line options allow for those
users to be created as active users (so that they can
login to the target broker following import) or to be
simply included as references for audit purposes. |
| |
| Q: |
What about User Groups? |
| A: |
Exactly the same. User Groups referenced in a project
lifecycle are created as required in the target broker.
Existing users are mapped to the new user group as
appropriate and new (created users) are mapped to
the new user group if they are set to be created as
"real" users on import. |
| |
| Q: |
I have a custom form type on my source broker. This
form type doesn't exist on my target broker. How does
Trinem Project Manager handle that? |
| A: |
Definitions of all form types are included in the export
file. On import, a check is made to see if the custom
form type exists in the target database. If it does not
exist, then the form type is automatically created. If
the form type does exist, then checks are made to
ensure that the form content (field names and types)
is identical. If there any variations (such as if the form
type is of a different version in the source and target
brokers) then a new form type is created
automatically. |
| |
| Q: |
How secure is the Trinem Project Manager export file? |
| A: |
The export file is in binary format with all version data encrypted. In
addition, the export file can be protected with a password which has to be
provided in order to import the project. |
| |
| Q: |
How does Trinem Project Manager process all the
internal CA-SCM object IDs? |
| A: |
When importing, Trinem Project Manager creates
"shadow" database tables in the target database.
Sequences are then amended and the object IDs are
updated in these shadow tables before the shadow
tables are copied to the main application tables and
the shadow tables are deleted. |
| |
| Q: |
I have one broker running on Solaris with Oracle as a
database. I have another broker running on Windows
Server with SQLServer as a database. Can I use Trinem
Project Manager to copy projects between these two
environments? |
| A: |
Yes you can. The Trinem Project Manager export file is
platform and database vendor neutral. You can export
a project from a Unix/Oracle based broker and import
it into a Windows/SQL Server based broker (and, of
course, vice-versa) with no issues. |
| |
| Q: |
I have a project based on a snapshot. If I export this project and import
it into another broker, what happens to the baseline? |
| A: |
This will depend on what's in the target project. Assume we're
exporting "Project C" which is based on "Snapshot B"
taken from "Project A". If we then take that export and import it
another broker which has "Project A" and "Snapshot B"
then the import will simply restore the baseline to be of "Snapshot
B". If "Project A" and/or "Snapshot B" does not
exist on the target then a new baseline is created on the target with the
baseline made up of the original content of "Snapshot B". In
either case, the project is restored with all baseline data intact. |
| |
| Q: |
Can I use Trinem Project Manager to restore a single project from a
database backup? |
| A: |
Yes. One of the biggest problems in CA-SCM is when you need to restore a
single project without reverting all other projects. Using CA-SCM you can
restore a backup to a second (test) broker and export a single project from
that instance. You can then restore that project to the primary broker - you
don't even need to delete the original project since Trinem Project
Manager renames the project and any included forms automatically. Your team
can then cross-project merge accidentally deleted versions from the restored
backup. |
| |
| Q: |
Who can run Trinem Project Manager? What about security? |
| A: |
Trinem Project Manager is a server-side command line tool. It
connects to the CA-SCM database via ODBC. Since it is a server-side tool, it
is only available to operating system users who have access to the CA-SCM
server machine. It does not authenticate with CA-SCM and requires database
credentials to access the CA-SCM database. |
| |
| Q: |
Can I allow CA-SCM users to export and import projects? |
| A: |
Yes. By using Trilogy you can turn
Trinem Project Manager into a client-server tool and allow your end
users to export projects to files on their own client machines. |
