Release Information

Web Services Support

Stat provides a Web Service inteface that enables external applications to create new and update existing Stat CSRs.

• Stat can create CSRs via inbound emails today, but this new enhancement provides users with tighter integration with other ticketing or change request systems
• Stat also provides bi-directional integration so that status changes in Stat can update an external ticketing system

Pre-Migration Steps

Stat provides pre-migration steps enabling prescribed activities to be performed prior to a migration of objects. This is similar to Stat's ability to perform post migration steps, except that it is just done upfront in the migration process rather than after the fact. This capability is most useful for actions that involve preparing files, running scripts or updating a server prior to moving the objects. 

Users can even organize the different steps by object type or environment or other relevant criteria. 

Note: SSH would need to be supported just like it is for post-migration steps. 

Security concerns are ever-present and while Stat provides some password structure enforcement today, it could be better. This enhancements provides administrators with the ability to:

• Specify the length of password their users must enter for use of Stat
• Change the number of failed logins that occur before an intruder alert is triggered
• Define the minimum number of characters allowed for a userid

Oracle: 9i version 9.0.1 and higher, 10g version 10.1.0.2 and higher, and 11g (Unicode and non-Unicode support for all Oracle DBMS)

MS SQL Server:
2000, 2005, 2008 (Unicode and non-Unicode: ISO Character Set with Unicode collation. Database defined with BINARY collation)

Notes:

• Can reside on same server as PeopleSoft or Oracle E-Business database or separate server.
• If PeopleSoft is configured for Unicode operation, the Stat database must be also.

• Windows, Solaris, and RedHat Linux require Sun’s JDK/SDK 1.5.x
• HPUX 11.11, 11.23 requires HP’s JDK/SDK
• 64bit AIX v5.2, 5.3 and 6.1 requires IBM’s JDK/SDK
• Standalone configuration not recommended on same machine as SQL Server Stat Database

Oracle:
Oracle 8i, 9i 10g, and 11g (Unicode and non-Unicode)
Connectivity: Oracle Client 9i

MS SQL Server:
2000, 2005, 2008 (Unicode and non-Unicode: ISO Character Set with binary collation)
Connectivity: SQL Server 7.0, 2000 client, 2005 client

Note: PeopleTools 8.48 and higher require Stat to be running on SQL Server 2005 client.

Sybase:
ASE 12.5 (Unicode and non-Unicode)
Connectivity: Sybase ASE ODBC client

DB2:
DB2 UDB for AIX 7.2, 8.2 (Unicode and non-Unicode)
DB2 UDB for OS/390 v6.1, DB2 UDB for z/OS & OS/390 7.1 (non-Unicode only), 8.1, 9.1, 9.5
Connectivity: DB2 Connect 7 FixPak 6 or later (for DB2 7), DB2 Connect 8 FixPak 6 or later (for DB2 8)

Notes:

• Stat supports the locking, archival and migration of all PeopleSoft Unicode data. Character sets other than Western cannot be entered directly into Stat through the Stat GUI interface.
• All Stat features are available for use in a Unicode environment except for File Object Impact Analysis and File Compare & Merge.

Must be NT, Unix, MVS or Netware compatible; SSH2 must use standard format listing; OpenSSH (UNIX and Windows), SSH Communications Corp. (UNIX and Windows), bitwise WinSSHD, and wodSSHServer are supported. VanDyke VShell 2.1 is NOT supported.

The configuration of your SSH server determines which ciphers are used when connecting to the Stat Server.  The Stat Server currently supports the following cipher and MAC configurations:

Ciphers:

• Blowfish
• Triple DES
• AES128Ctr
• AES192Ctr
• AES256Ctr

Message Authentication Code (MAC):

• HMAC-MD5
• HMAC-SHA1
• HMAC-MD5-96
• HMAC-SHA1-96