Chat now with support
Chat mit Support

Stat 6.2 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Server-Specific Pre/Post Migration Step Parameters

In the Pre/Post Migration Step Parameters Maintenance table, system administrators define public server-based parameters that can be included in the definition of pre and post migration command steps executed on any file server configured in Stat. However, because these parameters specify a set of default values that may not be applicable to all servers, such as home directories or version numbers, you can define server-specific parameters in the Server Parameters tab of the Other Options window. Here you can define entirely new parameters, or you can specify server-specific values that override the default values of public parameters.

See the section, Pre/Post Migration Steps Parameters for more information.

To define server-specific parameters:
1
In the File Servers tab, select the file server you want.
2
Click Other Options.
Stat opens the Other Options dialog box.
3
Select the Server Parameters tab.
When first opened, the tab displays all the public server parameters that have been defined in the Pre/Post Migration Parameters Maintenance table. Here you can create a new parameter that is specific to the selected server, or you can define a value specific to the selected server that overrides the public value of a public parameter.
4
To define a new parameter, do the following:
a
Click New.
b
Enter the parameter name.
c
Enter the parameter value in the Value field.
* 
NOTE: If you do not enter a parameter value, the value defaults to null.
d
(Optional) Select the encrypted option if you do not want the parameter value to be visible to users executing the pre or post migration custom command step.
5
To define a server-specific value for a public parameter, do the following:
a
Enter the value you want in the Value field.
When used in the definition of a custom command pre or post migration step executed on the server, this value will be used instead of the public value.
b
(Optional) Select the encrypted option if you do not want the parameter value to be visible to users executing the pre or post migration custom command step.
6
Click OK.

SFTP Public Key-Based Authentication

Whenever Stat accesses file objects on a file server, Stat “logs in” using the username configured in Stat for that server. The file server then authenticates the user ID, typically with a password. For customers wanting a more secure method of authenticating user accounts on their SFTP file servers, Stat supports public key-based authentication.

With public key-based authentication, each user ID has a set of public keys which are authenticated by a set of corresponding, mathematically related private keys. Data encrypted with public keys can only be decrypted by their associated private keys and vice versa. When the user (in this case Stat) attempts to log into a SFTP server, the user ID is sent to the server with an associated public key. The server then checks the list of public keys associated with the user ID. If the public key is identified, the server then requires that the user authenticate their ownership of the public key by sending data encrypted with the associated private key. If the server is able to decrypt the data using the public key, the user is authenticated and granted access to the server.

Stat supports public key-based authentication using either the RSA or DSA algorithms. DSA is recommended as the more secure choice and is used by default. RSA is supported for SFTP servers already configured to use RSA.

To configure public key authentication, you must first assign Stat a user ID on each SFTP server. Then you must define in the Stat Repository a set of public and private key s associated with that ID. Remember that the public keys associated with the user ID must be defined on the server as well.

There are two ways you can acquire the key sets you need:

•
Stat can generate both the public and private keys. You can then export the public keys from Stat to the SFTP server. In this case, the private key is automatically stored in Stat repository.
•
The key set can be generated by some third party. You can then import the private keys into Stat and the public keys into the SFTP server.
* 
NOTE: Configuring your servers to use public key authentication is platform-
specific and lies outside the scope of this document. However, some SFTP servers have key generation capabilities, which typically write key pairs to a file stored in their home directories, such as ~/.SSE/authorized_keys for SSH1 and ~/.ssh/authorized_keys2 for SSH2.
To setup SFTP public key authentication in Stat:
1
In the Object Type Maintenance window, select the File Servers tab.
2
In the FTP Protocol field, select SFTP.
3
In the Auth Type field, select Public Key.
* 
NOTE: Select Password if you want to use standard user ID/password authentication. When you select this option, the Authentication field displays an Enter Password button. To create a password, click Enter Password, and in the Change Password dialog box, enter the password in the Password and Confirm Password fields (50 characters maximum). Then click OK.
4
In the Authentication field, click Public Key Config.
This opens the Public Key Maintenance window where you can generate a key pair and export the generated public key to add to the list of public keys on your file server. If you already have a key pair, you can use this window to import the private key into Stat.
To import a private key:
1
Enter the fully qualified path to the file in the Import/export file field and then click Import Private.
You must have a key that is stored in a text file in the appropriate format.
If the import is successful, the contents of this key are reflected in the Status section of the window.
If the operation fails, Stat displays a pop-up message. Likely causes are (a) the specified file is not accessible, (b) the contents of the importation file are not in a format that is understood by Stat’s SFTP component, or (c) the file contains a public key (you must import a private key).
* 
CAUTION: Imported or generated RSA keys are limited to 1024 bits and DSA keys are limited to 2048 bits. Longer keys are not supported and may cause database corruption.
To export a public key:
1
Enter the fully qualified path to the file in the text box and then click Export Public.
The Status section of the window must indicate the presence of a key. The key can come from the database, be freshly generated, or recently imported.
If the export is successful, the public key is written to the specified file.
If the operation fails, Stat displays a pop-up message. The most likely cause of failure is that the specified file location is not accessible.
To generate a key:
1
Select the key type, either DSA or RSA. DSA is recommended.
RSA is only provided for backwards compatibility with older SFTP servers.
2
In the Size field, select the desired key size.
Options include 768, 1024, and 2048. Longer keys are more secure but take more time to generate. The default is 1024.
* 
CAUTION: Currently, imported or generated RSA keys are limited to 1024 bits, and DSA keys are limited to 2048 bits. Keys longer than these limits are not supported and may cause database corruption.
3
Click Generate.
If the generation is successful, the contents of this key are reflected in the Status section of the window. Note that once the key pair is generated, the private key is automatically stored in Stat repository.

User Default Directories

The User Default Directories Maintenance table defines the default working directories for each Stat user. Whenever an archive set containing a file object is migrated to the working directory, Stat checks to see if a separate working directory for that type of file object has been defined for the assigned user (as described earlier in the Source File Locations section). If not, Stat places the file object in the user’s default directory.

* 
NOTE: You can also define a user’s default working directory in the User File Directories tab of the Other User Information window. For more information, see Defining Stat Users . User can also define their own working directories in the Stat User Options window. For more information, see the “Object Management” sections in the change management chapters of the Stat User Guide.
Value
Description

Stat User
(Key Value)

The user’s Stat user ID

User Name
(Read Only)

The user’s name

Working File Server

Server where the working folder is located

Working File Path

File server path where the working folder is found. Make sure you use the proper syntax when specifying working directories. For more information, see File Path Syntax .

Last Update
(Read Only)

The date and time this record was last updated

Update Userid
(Read Only)

The user who last updated this record

After defining a default directory in the maintenance table, you can make sure that you have entered all the information correctly by clicking Test Connection. See the section, Testing File Locations, Servers, and Default Directory Locations for more information.

Oracle Apps Base Directories

For Oracle Applications, you need to specify file locations only for custom file types (Custom, Custom with Product or Custom with Product and Language). The locations of the proprietary file types (forms, reports, etc.) are managed by Stat automatically. The base directories are defined on the OraApps Base Directory tab, while the file “pathways” are defined on the file type window.

The agent must be able to resolve the server environment variable into a known file location. For all non-R12.2 environments, this is done via the stat.conf file. For example, if in the Object Type Maintenance table you defined a base directory code COMMON_TOP, you must add the following parameter to all the Oracle agents that will process the custom objects using this base directory code:

Dev.env.COMMON_TOP=/apps/dev/common

The syntax for the parameter is <EnvCode>.env.<BaseDirectory>=<value>. The value should be an absolute (i.e., fully qualified) directory with read/write privileges for the Oracle agent. The parameter in this example is added to the Oracle agent for the “Dev” environment. The parameter can be set to a different directory for each agent.

For R12.2 environments, if these base directories are under the Edition-based File System, then the value for each Base Directory must come from the context file. An example of these types of Base Directories would be OA_HTML. This parameter is defined in the context file with a value for both the fs1 and fs2 file system. To retrieve values from the context file, you always need an XPath expression. The Context Pattern field in Stat stores the XPath expression for retrieving the value from the context file. (You may need to consult with your DBA and refer to documentation for EXTRACTVALUE command). For example the expression for retrieving OA_HTML from the context file is: //OA_HTML[@oa_var="s_oahtml"].

Note that if these Base Directories are not under the Edition-based File System, then the value for the Base Directory is defined in stat.conf.

Also Note that in general if a value is defined for any parameter in stat.conf, it always overrides the value read from the context file.

* 
NOTE: Be aware of the following:
•
Custom objects in Stat are specially affected by R12.2 file system. For Custom and Generic custom objects, OA Base Directory values should exist in the Environment's Context File, or it should come from a location outside the AppsTier File System. In the latter case, the values are defined in the stat.conf file as before.
•
Context patterns may be used be all releases of R12, in which case you don’t need to define the base directory as a parameter in the stat.conf file.
To define an Oracle Applications base directory:
1
In the OraApps Base Directories tab, click New.
2
In the Base Directory Cd field, type a name that uniquely identifies the directory.
3
In the Server Environment Variable field, enter the base description as defined in the stat.conf file.
4
For R12.2 environments, if the base directories is under the Edition-based File System, enter the XPath expression for retrieving the value from the context file in the Context Pattern field.
5
Click OK or Apply to save your changes.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen