Stat 6.3 - Install Notes

Update the System Maintenance table Install the Stat Central Agent

Installing the Stat Central Agent Configuring the Stat Central Agent

Before starting the Stat Central Agent Resolving port and firewall conflicts Stopping the Stat Central Agent Configuring the Stat Central Agent as a Windows service Installing DB2 Support for the Stat Central Agent Configure the Stat Central Agent character map Setting up support for AES256 Ciphers for SFTP Configure Web Client to use HTTPS Connection pool idle time Configure Web Client and Web Services to use custom URL Installing multiple servers on one host computer

Testing Database and Server Connections

Install the Stat Oracle Agent (Oracle E- Business Suite only)

Configuration Administration Dynamically changing log level Stat Oracle Agent version Custom products and file locations Base directory codes Verifying the Stat Oracle Agent

Configure the SYSTEM user account Update the PS Object Mover Instructions (PeopleSoft Only) Implement Stat

Verifying the Stat Oracle Agent

The Stat® Oracle® Agent performs a series of validations when it’s started. The log, by default, is stored in <STAT_HOME>/log. Parameters in the stat.conf specify the log filename and optionally the log directory. With info level logging enabled, the last line of the log file should be read Main processor started if the agent started. For example:

2004-09-17 13:15:27 INFO - Main processor started

The last line indicates the agent passed all validations and started successfully.

Configure the SYSTEM user account

In the section Update the System Maintenance Table , you were instructed to log into the application for the first time using the special SYSTEM user account. This account is the only way to log into Stat® until you define additional users. However, you cannot define additional Stat users until you have configured Stat to process outbound email and have defined a service domain and associated it with the SYSTEM account.

New users in Stat receive an auto-generated email containing a temporary password, allowing them to log in to the application. When processing the outbound email, Stat uses the SMTP settings configured for the default service domain of the administrator that defined the new user. The SYSTEM account is delivered without a default service domain, however, as none yet exist. This means that after configuring Stat to process outbound email, your next task is to define a service domain and associate it with the SYSTEM user account.

Also, the SYSTEM account is delivered without an email address. After defining a default service domain for the SYSTEM account, you should assign it an email address. This way, if you want to reset the SYSTEM account password for any reason, Stat can deliver a temporary password to the specified email address.

For more information about the SYSTEM account, see the Stat System Administration Guide, Chapter 1, Overview of Stat Administration.

To configure the SYSTEM user account:

Login to Stat with the “SYSTEM” user name and the password you created when you first logged in, as described in the section Update the System Maintenance Table on page 16.

Go to Maintenance | Stat Central Agent| Email Settings and configure the Stat Central Agent to process outbound email.

For detailed instructions, see the section “Outbound Mail Configuration” in the Stat System Administration Guide, Chapter 7, Email Configuration.

Go to Maintenance | General | Service Domains and define a default service domain for the SYSTEM account.

Each service domain must be configured to process outbound email via SMTP. For more information on defining a service domain, see the section “Service Domain Maintenance” in the Stat System Administration Guide, Chapter 4, General Maintenance Tables.

After defining the service domain, you must assign it to the SYSTEM user account as its default service domain.

Go to Maintenance | Security Settings | User Maintenance.

Select the SYSTEM user, click Access Information and select the service domain you just created as its default.

For more information, see the section Defining Stat Users in the Stat System Administration Guide, Chapter 3, Stat Security Settings.

Assign the SYSTEM user account an email address.

When finished, click OK.

Update the PS Object Mover Instructions (PeopleSoft Only)

Stat® requires a set of instructions in order to archive PeopleSoft® objects. These instructions must be loaded using a utility available under the Maintenance menu in Stat. The instructions are contained in the file, psominst.psr, which is installed to the Stat home directory. For more information on the PeopleSoft Object Mover Utility, see the Stat System Administration Guide, Chapter 2, Administrative Utilities.

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 Stat System Administration Guide.

•

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.

About us

We are more than just a name

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 Quest’s 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 brand, our vision. Together.

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.

Contacting Quest

For sales or other inquiries, visit https://www.quest.com/contacthttp://software.dell.com/contact-us.aspx.

Technical support resources

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:

•

Submit and manage a Service Request