What is the Wise Software Repository and what does it do?

Article:HOWTO5414  |  Created: 2006-10-12  |  Updated: 2008-01-28  |  Article URL http://www.symantec.com/docs/HOWTO5414
Article Type
How To



Question

What are frequently asked database questions about Wise Package Studio?

Answer

What is the Wise Software Repository?

The Wise Software Repository™ is a collection of software packages, resources and information about those resources, project management information, and quality assurance data used by organizations as part of the repackaging process. This scalable repository provides a centralized point for managing software packages at any stage of deployment.

The Wise Software Repository consists of:

  • Share point directory
    Contains shared Wise Package Studio files and shared resources that are used to create Windows Installer installations. It also contains source files for packages in the Software Manager database. All Wise Package Studio databases are associated with a specific share point directory.
  • Workbench database
  • Software Manager database
  • Wise Services database (formerly the Preflight database)

The Repository Manager will update schema changes in the database. 

What does the Wise Repository Do?

The Wise Repository Manager gives you control over database configuration and updates, and lets you see the changes that are made by database updates. The Wise Repository Manager provides a view of the Wise Software Repository and lets you:

  • Create and configure the Wise Package Studio share point and the databases associated with it.
  • Upgrade the databases.
  • Create additional Software Manager databases within a repository.
  • Create a new Wise Software Repository.
  • Change the default repository.
  • Set options for the Revision Control System.
  • Set the account used to launch Wise Package Studio server-side tasks.

Running the Wise Software Repository Manager:
After the initial Wise Package Studio Installation and rebooting the computer, you will need to run Repository Manager which will create the databases.

We recommend against creating empty databases then running the Repository manager against the manually created databases. 

If you have installed SQL Server or MSDE with NT authentication only, the Wise Task Manager, which manages operations on the Wise Package Studio server, will not work. Therefore, during the Wise Package Studio database configuration, the authentication method is changed to mixed mode (NT and SQL).

The Repository Manager does not allow the user to specify the location of the physical database files.  It will use the default location on the server.

The Wise Repository Manager fails to update:
If one or all of the databases fail to run, follow the steps below in an attempt to complete the installation.  If following these steps fail, place a call into our support center. 

  1. In the left pane of the Wise Repository Manager, click a database name that has failed to complete (has a red X through the database name).
  2. Do any of the following:
    • To run all uncompleted actions, click Run All.
    • To run the upgrade actions individually, click the first uncompleted action in the list and click Run. (Uncompleted actions are indicated by a status of Pending.) Then repeat for subsequent actions. You cannot run the actions out of sequence.
    • Select the Upgrade button on the Wise Repository Manager. This will stop the WiseService then restart it, restarting the Repository Manager.

The database or databases should all become updated, the actions you ran are marked as completed,and a record of the upgrade actions is written to WiseAdmin.log. To display the most recent log, click Show Log on the toolbar.

Creating SQL Users through the Wise Repository Manager:
The Repository Manager installation includes a dialog for creating SQL accounts for the WPS users (only available when selecting SQL authentication). These users are given DBO rights. If you want users to have less privileges, then you will need to manually create the users themselves with at least read/write permissions to all tables and execute permissions on all stored procedures.


Legacy ID



28497


Article URL http://www.symantec.com/docs/HOWTO5414


Terms of use for this information are found in Legal Notices