Chatta subito con l'assistenza
Chat con il supporto

Stat 7.0 - 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 Enabling Web Client to perform PeopleSoft migrations 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: Oracle Agent: Stat.conf and log4j2.xml configuration Appendix: Custom Report Files

Appendix: Ports and Firewalls

This appendix provides instructions for resolving port conflicts and firewall issues that may prevent the Stat Central Agent from running. Typical port and firewall conflicts include:

•
Other applications are using the same port as the Stat Central Agent
•
You are running multiple Stat Central Agents on the same host machine and the installations are trying to access the same ports
•
The default timeout setting on a firewall prevents the Stat Central Agent from opening properly

Resolving port and firewall conflicts

If the Stat™ Central Agent will not run when started, the port assigned to it may already in use by a different program or there are firewalls that need to have ports opened for the Stat Central Agent to communicate with the database or with the Stat Client.

 

Typical port and firewall conflicts include:

•
Other applications are using the same port as the Stat Central Agent
•
You are running multiple Stat Central Agents on the same host machine and the installations are trying to access the same ports
•
The default timeout setting on a firewall prevents the Stat Central Agent from opening properly

If you have port conflicts, the server will display one or more error messages, such as:

java.net.BindException: Address already in use: Bind

The Stat Central Agent utilizes a set of ports that are already defined.

These values are defined for a default port offset of zero which is set in a variable called jboss.socket.binding.port-offset in standalone.conf.bat or standalone.conf file. If there is a conflict situation or a second or third agent is necessary, you may change the jboss.socket.binding.port-offset in standalone.conf.bat or standalone.conf file. The value for offset is added to all the default values.

For example:

•
if offset is zero, ports 8080, 8443, 9990, 9993, 4712, and 4713 are used.
•
If offset is one, ports 8081, 8444, 9991, 9994, 4713, and 4714 are used.
•
If offset is two, ports 8082, 8445, 9992, 9995, 4714, and 4715 are used.
•
If offset is 100, ports 8180, 8543, 10090, 10093, 4812, and 4813 are used.
 
Table 42. Ports
Description
Ports

HTTP socket binding

8080

HTTPS socket binding (See Note)

8443

Management socket binding

9990

Management socket binding https (See Note)

9993

Transaction sockets

4712

4713

* 
NOTE: Be aware of the following:
•
Stat invokes the DNS server to resolve the fully qualified server name when communicating between the client and the central agent. When server hostname is not registered on the DNS server, use etc/hosts file to map hostname and its IP address.
•
HTTPS connector socket and Management socket — These ports are only necessary if the Stat Central Agent is configured to support HTTPS.
Port configurations

When other applications are using the same port as the Stat Central Agent, you need to change the port offset in your standalone.conf.bat or standalone.conf file.

1
Review the port configurations described above and decide on a proper offset.
2
Open <STAT_HOME>\app\bin\standalone.conf.bat with Notepad or other text editor. For Stat Central Agent on Unix, you need to open the <STAT_HOME>/app/bin/standalone.conf file.
3
Search for the setting: -Djboss.socket.binding.port-offset=0
4
Change the setting to a proper offset. For example, -Djboss.socket.binding.port-offset=10
Firewall configuration

The http port is the only port that needs to be opened on existing firewalls.

•
Client to Central agent: 8080 (If port-offset has changed, add the value to 8080)
•
Central Agent to Oracle agent: 8080 (If port-offset has changed, add the value to 8080)

Other ports used by the Stat Central Agent include the following (the actual port numbers will vary according to your site specifications):

•
Stat database (Oracle® default=1521; MSS default = 1433)
•
PeopleSoft® databases
•
E-Business databases
•
FTP/SFTP (default = 21/22)
•
Email: SMTP/POP3/IMAP4 (default= 25/995/993)

The Stat Client will need the same ports opened if there is a firewall between the client and any of the above items.

Natted firewall between the Stat Central Agent and Stat Oracle Agents

If there is a natted firewall between the Stat Central Agent and the Stat Oracle Agents, the following options must be configured in the stat.conf file for the Stat Oracle Agents. Older versions of Stat always required the fields to be filled in, but since 5.6.0, the Stat Oracle Agents query the Stat Central Agent for the secure Stat database information. You need only change the stat.db.server: value and indicate the natted ip address. For this scenario, they are not optional.

################################################################################

# Stat Repository

################################################################################

stat.db.jdbc_driver:oracle.jdbc.driver.OracleDriver

stat.db.server:<stat repository server name/ip> <-- Natted IP Address

Appendix: REST Web Services API

Stat provides programmatic access to CSR information via a Web Service API. The Stat Web Services are available when the Stat Central Agent is live. API calls represent specific operations that your client applications can use to retrieve or update data.

The following information is intended for developers and system administrators who want to use Stat Web Services to develop an interface to one or more of their in-house applications.

Authentication

The preferred authentication method for the Stat REST API is HTTP basic authentication (when using SSL).

The Stat Web client uses cookie-based authentication in the browser, so you can call REST from JavaScript on the page and rely on the authentication that the browser has established.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione