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

MSS SQL Server Database Tuning

MSS SQL Server is basically a self tuning system.

Be sure there is adequate space for Transaction logs based on your backup schedule

TempDB should be a minimum 50M for each database on the server, including the master, model, etc). e.g. if there are 6 databases, the tempdb should be, at minimum, 300M in size.

Run the following on a weekly basis:

Execute STAT_UPDATESTATS

Appendix: Oracle Applications File Type Directory

This appendix documents the directories Stat uses for retrieving an object list, archiving an object, and migrating an object for all the proprietary Oracle Applications file object types. Proprietary Oracle Applications file types require that the user select a product and language before Stat retrieves a list of objects. These attributes are used to determine the archive and migration locations.

Notation:

•
$prod is used to represent the selected product
•
$prodTop is used to represent the directory for the selected product
•
$lang is used to represent the selected language.

Oracle follows a precise file structure convention for locating files for specific types. Many sites do not adhere to the convention strictly for their custom object types. Stat provides flexibility where feasible and useful to accommodate common conventions used by many sites for storing custom files. For example, Oracle stores all FMB files in $AU_TOP/forms/<lang>. Many sites do not store custom FMB files in $AU_TOP, nor do they create a sub-directory for each language. Stat allows custom FMBs to be stored in $prodTop/forms directory.

An Oracle Applications environment can be partitioned across several physical servers. Logically, there are four servers: Web Server, Forms Server, Concurrent Manager, and Database. Objects for each object type are stored on one or more of these logical servers. The table also identifies the server type.

 
Table 20.  
Object Type: Exe File (All Servers)

Object List

Include all files in:

- $prodTop/bin/*

Object Archive

$prodTop/bin

Migration
Destination

$prodTop/bin

 
Table 21.  
Object Type: Menu File (Forms Server only)

Object List

Include all files in:

$prodTop/resource/$lang/*.mmb

Object Archive

$prodTop/resource/$lang

Migration Destination

$prodTop/resource/$lang

NOTE: The MMX file is always generated in $prodTop/resource/$lang (not $AU_TOP/resource).
 
Table 22.  
Object Type: Form File (Forms Server only)

Object List

Consider possible forms in:

- Registered Form

- FMX files in $prodTop/forms/$lang

Include if FMB file exists in $AU_TOP/forms/$lang

If $prod is custom

Include all FMBs in $prodTop/forms/$lang

Include all FMBs in $prodTop/forms

EndIf

NOTE: Stat does not return any objects if selected product is AU*

Object Archive

If $prod is custom

Consider following directories using first where file is found

- $prodTop/forms/$lang
- $propTop/forms
- $AU_TOP/forms/$lang

If file not found, throw exception.

Else

$prodTop/forms/$lang

EndIf

Migration
Destination

If $prod is custom

Consider following directories using first where file is found

- $prodTop/forms/$lang
- $propTop/forms
- $AU_TOP/forms/$lang

If file not found, consider following directories using first that exists

- $prodTop/forms/$lang
- $propTop/forms

If directory not found, throw exception.

Else

$prodTop/forms/$lang

EndIf

NOTE: The FMX file is always generated in $prodTop/forms/$lang
 
Table 23.  
Object Type: Form Library File (Forms Server only)

Object List

Include all files in:

- $prodTop/resource/*.pll

NOTE: Since Oracle stores all PLLs in $AU_TOP/resource, no files will typically be returned with standard products except for AU. However, Stat searches the product top to allow custom PLLs to be stored with the custom product top.

Object Archive

$prodTop/resource

Migration
Destination

$prodTop/resource

NOTE: The PLX file is always generated in $prodTop/resource (not $AU_TOP/resource). This requires FORMS60_PATH to include $prodTop/resource if custom PLLs are not stored in $AU_TOP/resource.
 
Table 24.  
Object Type: Oracle Workflow File (Database Server only)

Object List

If $prod is custom

Include all files in:

- $prodTop/admin/import/$lang/*.wft
- $prodTop/admin/import/*.wft
- $prodTop/admin/$lang/*.wft
- $prodTop/admin/*.wft

Else

Include all files in:

- $prodTop/patch/115/import/$lang/*.wft
- $prodTop/patch/115/import/*.wft
- $prodTop/admin/import/$lang/*.wft
- $prodTop/admin/import/*.wft

EndIf

Object Archive

If $prod is custom

Consider following directories using first where file is found

- $prodTop/admin/import/$lang
- $prodTop/admin/import
- $prodTop/admin/$lang
- $prodTop/admin

If file not found, throw exception.

Else

Consider following directories using first where file is found

- $prodTop/patch/115/import/$lang
- $prodTop/patch/115/import
- $prodTop/admin/import/$lang
- $prodTop/admin/import

EndIf

Migration Destination

If $prod is custom

Consider following directories using first where file is found

- $prodTop/admin/import/$lang
- $prodTop/admin/import
- $prodTop/admin/$lang
- $prodTop/admin

If file not found, consider following directories using first that exists

- $prodTop/admin/import/$lang
- $prodTop/admin/import
- $prodTop/admin/$lang
- $prodTop/admin

If directory not found, throw exception.

Else

Consider following directories using first where file is found

- $prodTop/patch/115/import/$lang
- $prodTop/patch/115/import
- $prodTop/admin/import/$lang
- $prodTop/admin/import

If file not found, consider following directories using first that exists

- $prodTop/patch/115/import/$lang
- $prodTop/patch/115/import
- $prodTop/admin/import/$lang
- $prodTop/admin/import

If directory not found, throw exception.

EndIf

NOTE: The WFT file is always loaded into the database using WFLOAD
NOTE: For R12.2 environments, the WFT file is loaded into the Run Edition of the database when migrating to Run or Both Editions and is loaded into Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.
 
Table 25.  
Object Type: PKB (PL/SQL Body) File (Database Server only)

Object List

Include all files in:

- $prodTop/admin/sql/.pkb,.plb

$prodTop/patch/115/sql/*.pkb, *.plb

Object Archive

Consider following directories using first where file is found

- $prodTop/patch/115/sql

- $prodTop/admin/sql

Migration Destination

If $prodTop/patch/115/sql directory exists

- $prodTop/patch/115/sql

Else

- $prodTop/admin/sql

EndIf

NOTE: The file is always executed in the database using sqlplus
NOTE: For R12.2 environments, the file is executed in the Run Edition of the database when migrating to Run or Both Editions and is executed in Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.
 
Table 26.  
Object Type: PKH (PL/SQL Body) File (Database Server only)
NOTE: This object type looks for files with both .pkh and .pks extensions.

Object List

Include all files in:

- $prodTop/admin/sql/(*.pkh, *.pks)

$prodTop/patch/115/sql/(*.pkh, *.pks)

Object Archive

Consider following directories using first where file is found

- $prodTop/patch/115/sql

- $prodTop/admin/sql

Migration Destination

If $prodTop/patch/115/sql directory exists

- $prodTop/patch/115/sql

Else

- $prodTop/admin/sql

EndIf

NOTE: The file is always executed in the database using sqlplus.
NOTE: For R12.2 environments, the file is executed in the Run Edition of the database when migrating to Run or Both Editions and is executed in Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.
 
Table 27.  
Object Type: PL/SQL File (Database Server only)

Object List

Include all files in:

- $prodTop/admin/sql/*.pls if exists, otherwise $prodTop/sql/*.pls
- $prodTop/patch/115/sql/*.pls

NOTE: All standard products include the $prodTop/admin/sql directory. Stat checks the $prodTop/sql directory to accommodate sites that store their custom PLS files in this directory

Object Archive

Consider following directories using first where file is found

- $prodTop/patch/115/sql/

$prodTop/admin/sql if exists, otherwise $prodTop/sql

Migration Destination

If $prodTop/patch/115/sql directory exists

- $prodTop/patch/115/sql

Else if $prodTop/admin/sql directory exists

- $prodTop/admin/sql

Else

- $prodTop/sql

EndIf

NOTE: The file is always executed in the database using sqlplus
NOTE: For R12.2 environments, the file is executed in the Run Edition of the database when migrating to Run or Both Editions and is executed in Patch Edition of the database when migrating to Patch Edition
 
Table 28.  
Object Type: Report File (Concurrent Manager Server only)

Object List

Include all files in:

- $prodTop/reports/$lang/*.rdf if exists, otherwise $prodTop/reports/*.rdf

NOTE: Stat uses the value of $APPLREP instead of “reports” for the subdirectory. This environment variable is always set to “reports

Object Archive

$prodTop/reports/$lang if exists, otherwise $prodTop/reports

Migration Destination

$prodTop/reports/$lang if exists, otherwise $prodTop/reports

NOTE: The file is always compiled.
 
Table 29.  
Object Type: SQL Report (Concurrent Manager Server only)

Object List

$prodTop/sql/*.sql

Object Archive

$prodTop/sql

Migration Destination

$prodTop/sql

NOTE: The file is never executed in the database.
 
Table 30.  
Object Type: SQL Script (Database Server only)

Object List

Include all files in:

- $prodTop/admin/sql/*.sql
- $prodTop/patch/115/sql/*.sql

Object Archive

Consider following directories using first where file is found

- $prodTop/patch/115/sql
- $prodTop/admin/sql

Migration Destination

If $prodTop/patch/115/sql directory exists

- $prodTop/patch/115/sql

Else

- $prodTop/admin/sql

EndIf

NOTE: The file is always executed in the database using sqlplus.
NOTE: For R12.2 environments, the file is executed in the Run Edition of the database when migrating to Run or Both Editions and is executed in Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.
 
Table 31.  
Object Type: OAF - OA Component XML File (Database Server only)

Object List

Include all .xml files in:

MDS Repository for a specific $prodTop

Object Archive

XMLExporter is used to extract the xml file from MDS Repository.

Migration Destination

XMLImporter is used to deploy the xml file to MDS Repository of target

NOTE: For R12.2 environments, the xml file is loaded into the Run Edition of the database when migrating to Run or Both Editions and is loaded into Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.
 
Table 32.  
Object Type: OAF - OA Component Class File (Web Server only)

Object List

Include all seeded files in:

$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui/*.class

And any custom files in:

$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui/*.class

Object Archive

Consider following directories

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui

Migration Destination

Seeded files are migrated to:

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui

Custom files are migrated to:

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui

NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.
 
Table 33.  
Object Type: OAF - OA Component Java File (Web Server only)

Object List

Include all seeded files in:

$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui/*.java

And any custom files in:

$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui/*.java

Object Archive

Consider following directories

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui

Migration Destination

Seeded files are migrated to:

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/webui

Custom files are migrated to:

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/webui

NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.
 
Table 34.  
Object Type: OAF - BC4J Component XML File (Web Server only)

Object List

Include all seeded files in:

$JAVA_TOP/oracle/apps/$ProdTop/<component>/server/*.xml

And any custom files in:

$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server/*.xml

Object Archive

Consider following directories:

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/server

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server

Migration Destination

Seeded files are migrated to:

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/server

Custom files are migrated to:

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server

NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.
 
Table 35.  
Object Type: OAF - BC4J Component Class File (Web Server only)

Object List

Include all seeded files in:

- $JAVA_TOP/oracle/apps/$ProdTop/<component>/server/*.class

- $JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>/*.class

And any custom files in:

- $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server/*.class

- $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/<all except webui>/*.class

Object Archive

Consider following directories

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/server

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/<all except webui>

Migration Destination

Seeded files are migrated to:

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>

Custom files are migrated to:

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server

NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.
 
Table 36.  
Object Type: OAF - BC4J Component Java File (Web Server only)

Object List

Include all seeded files in:

- $JAVA_TOP/oracle/apps/$ProdTop/<component>/server/*.java

- $JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>/*.java

And any custom files in:

- $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server/*.java

- $JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/<all except webui>/*.java

Object Archive

Consider following directories

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/server

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/<all except webui>

Migration Destination

Seeded files are migrated to:

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>

-$JAVA_TOP/oracle/apps/$ProdTop/<component>/<all except webui>

Custom files are migrated to:

-$JAVA_TOP/$mycompany/oracle/apps/$ProdTop/<component>/<layer type>/<layer value>/server

NOTE: Custom files could be placed under a directory other than $JAVA_TOP, as long as that directory is on the classpath.
 
Table 37.  
Object Type: XDO XML Publisher Template Files (Database Server only)

Object List

Include all templates for a specific $prodTop from XDO_LOB table where LOB_TYPE is one of

TEMPLATE, TEMPLATE_SOURCE, XML_SCHEMA, XML_SAMPLE and DATA_TEMPLATE

Object Archive

XDOLoader is used to extract the template from XDO_LOB table

Migration Destination

XDOLoader is used to deploy the template to XDO_LOB table of target

NOTE: For R12.2 environments, the template file is loaded into the Run Edition of the database when migrating to Run or Both Editions and is loaded into Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.
 
Table 38.  
Object Type: XDO XML Publisher Translations (Database Server only)

Object List

Include all translations for a specific $prodTop from XDO_LOB table where LOB_TYPE is XDO_TRSL

Object Archive

XLIFFLoader is used to extract the translation from XDO_LOB table

Migration Destination

XLIFFLoader is used to deploy the translation to XDO_LOB table of target environment

NOTE: For R12.2 environments, the template file is loaded into the Run Edition of the database when migrating to Run or Both Editions and is loaded into Patch Edition of the database when migrating to Patch Edition. Note that you need to have the ‘OraApp Migration to Run Edition’ right to migrate to Run Edition.
 
Table 39.  
Object Type: XDO XML Publisher DS by Template (Database Server only)

Object List

Include all active data sources from XDO_DS_DEFINITIONS

Object Archive

FNDLoad is used to extract the data source from XDO_DS_DEFINITIONS table

Migration Destination

FNDLoad is used to deploy the data source to XDO_DS_DEFINITIONS table of target environment

 
Table 40.  
Object Type: XDF Editioning Views (R12.2 and Database Server only)

Object List

Include all Editioning Views from DBA_EDITIONING_VIEWS

Object Archive

xdfgen.pl is used to extract the xdf file from the Run Edition

Migration Destination

-xdf file is copied to

If $prodTop/patch/115/xdf directory exists

-$prodTop/patch/115/xdf

Else if $prodTop/admin directory exists

-$prodTop/admin

EndIf

-xdfcmp.pl is used to deploy the xdf file to

the target environment

NOTE: When migrating xdf files to Run or Both Editions of a target environment:
•
If there is an active Patch Cycle in effect, Stat deploys the xdf file to the file system and returns with a warning.
•
If there is no Patch Cycle in effect, Stat deploys the xdf file to the file system and loads it to the Run Edition of the environment.

When migrating xdf files to Patch Edition of a target environment:

•
If there is an active Patch Cycle in effect, Stat deploys the xdf file to the file system and loads it to the Patch Edition of the environment.
•
If there is no Patch Cycle in effect, Stat deploys the xdf file to the file system and returns with a warning.
 
Table 41.  
Object Type: XDF Editioning View Files (R12.2 and Database Server only)
NOTE: This object type is available to users in case the generated xdf file using the xdfgen.pl needs to be modified before deployment to a target environment.

Object List

Include all files in:

- $prodTop/patch/115/xdf/*.xdf

Object Archive

$prodTop/patch/115/xdf

Migration Destination

If $prodTop/patch/115/xdf directory exists

- $prodTop/patch/115/xdf

and xdfcmp.pl is used to deploy the xdf file to the target environment

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

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen