Chat now with support
Chat with Support

Stat 6.0 - Install Notes

Installing Stat
Prepare for installation Unpack the 6.0.0 installer Install the Stat database Create a staging database (PeopleSoft Only) Install the Stat Client Configure the Stat database Update the System Maintenance table Install the Stat Central Agent Install the Stat Oracle Agent (Oracle E- Business Suite only) Configure the SYSTEM user account Update the PS Object Mover Instructions (PeopleSoft Only) Implement Stat

Implement Stat

After you have successfully installed each Stat® component, there remain a number of tasks you need to perform before you can begin to create CSRs and take full advantage of Stat’s change management and version control functionality. These tasks are performed by system administrators and entail specifying values in Stat maintenance tables.

A maintenance table serves as a kind of template that defines certain operational parameters. For example, the options available on CSR drop down lists are defined in maintenance tables. The following subsections briefly summarize the most top level parameters that system administrators need to define when implementing Stat. For more information on these and other maintenance tables, see the book, Stat 6.0.0: System Administration.

Service Domains — Service domains allow you to divide your business into logical units. CSRs can only belong to one service domain and cannot be reassigned. The Service Domain table defines all the service domains in the Stat Repository. When first installed, there are no service domains in Stat. You must log into Stat initially with the “System” user ID. Then you can open the maintenance table and define your service domains.
Environment Connections and Object Types — Stat provides change management and version control support for PeopleSoft, Oracle Applications, and generic application environments. System Administrators configure and maintain the connections between Stat and the environments defined in whichever platform you are using. In general terms, this is done by specifying in Stat maintenance tables the various database login IDs and passwords, the connection pathways and source directories of the application servers or databases, as well as the types of objects that Stat will support. Stat features a separate maintenance table for establishing connections to PeopleSoft, Oracle Applications, and generic application environments. It also features another table, Object Type Maintenance, where system administrators define the types of objects for which Stat will provide change management and version control support.
Migration Paths — Migration paths define sets of environments that objects will be locked across and control the migration of objects from one environment to another. Migration paths must be defined before users can add objects to CSRs or perform any other version control or object migration operation.
Users and User Classes — Individuals authorized to use Stat must be defined in the Stat User Maintenance table. This includes assigning them a unique User ID that identifies them in the system and allows them to log in. User classes are logical groupings of security rights based on the functional roles of users. For example, Stat system administrators would typically belong to a user class that allows them to define and edit service domains, whereas most other Stat users would not belong to that class.
CSR Types and Statuses — CSR types divide CSRs into categories. They help identify what kind of problem or request the CSR represents. CSR statuses, on the other hand, represent the states a CSR goes through in its lifecycle. CSR types are associated with a set of CSR statuses. This way, when a user creates a CSR of a particular type, the drop down list in the Status field displays only the statuses defined for that type.
Customers — The Customer Maintenance table defines all of the customers in the Stat Repository. Customers report the problems or initiate the requests that result in the opening of CSRs. They can be members of client companies or internal employees.

We are on a quest to make your information technology work harder for you. That is why we build communitydriven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quests invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation.

Our logo reflects our story: innovation, community and support. An important part of this story begins with the letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece you to the community, to the new Quest.

For sales or other inquiries, visit https://www.quest.com/company/contact-us.aspx http://quest.com/contact-us.aspx or call +1-949-754-8000.

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

Related Documents