Verifying an HTTPS connection
You can check whether HTTPS requests from SAP can be successfully routed through your Content Collector for SAP environment. For the HTTPS requests, server authentication or client authentication can be used. The passwords for the truststore and, optionally, the keystore must be specified on the command line.
Parameters
- -m server_name
- Specifies the host name or the IP address of the system where Collector Server runs.
- -p port
- Specifies the value of the SSL_WEBPORT keyword.
- -a archive_id
- Specifies the logical archive ID of the archive for which the request applies.
- -t seconds
- Specifies the period, in seconds, before the archcheck program times out.
- -url_encoding string
- Specifies the encoding of the URL that is sent to Collector Server. It must match the value of the URL_ENCODING keyword in the server configuration profile.
- -log file_name
- Specifies the file name of the log. You can include a file extension.
However, you cannot change the path to the log file.
The log file is stored in the checkLogs folder of the instance directory of Collector Server.
Each time the archcheck program is run, a log file with the specified name is created. Any existing log file with this name is overwritten.
Do not specify this parameter if you want to keep a history of log files. If you omit this parameter, Content Collector for SAP generates a log file each time the archcheck program is run. The name of the log file is as follows:archive_id_yyyy_mm_dd_hh_mm_ss_ms.log - -https
- Specifies that the HTTPS connection is to be used.
- -trustStore file_name
- Specifies the fully qualified file name of the truststore on the system where the archcheck program runs.
- -trustStorePassword password
- Specifies the password for the truststore.
- -keyStore file_name
- Specifies the fully qualified file name of the keystore on the system where the archcheck program runs. You must specify this parameter only if archcheck sends an HTTPS request with client authentication.
- -keyStorePassword password
- Specifies the password for the keystore.
- -h
- Displays help information about the archcheck command.
Examples
java -jar archcheck.jar -p 5510 -a A1- Sends the HTTP request to archive A1 by using the Collector Server that runs on the same server as the archcheck program and that uses the fixed port 5510. The file name of the log, which is created in the checkLogs folder of the instance directory, is generated.
java -jar archcheck.jar -m ginkgo -a A1 -p 5510- Sends the HTTP request to archive A1 by using the Collector Server that
runs on server
ginkgoand that uses the fixed port 5510. The file name of the log, which is created in the checkLogs folder of the instance directory, is generated. java -jar archcheck.jar -p 5510 -a A1 -log A1_log- Sends the HTTP request to archive A1 by using the Collector Server that runs on the same server as the archcheck program and that uses the fixed port 5510. The log, which is created in the checkLogs folder of the instance directory, has the following file name: A1_log
java -jar archcheck.jar -p 5510 -a A1 -https -trustStore C:\ssl\truststore.jks -trustStorePassword TSPWD- Sends the HTTPS request to archive A1 by using the Collector Server that runs on the same server as the archcheck program and that uses the fixed port 5510 for the SSL communication. Truststore truststore.jks, which is stored in the C:\ssl directory and is secured by the password TSPWD, contains the certificate for the server authentication. Client authentication is not required by Collector Server. The file name of the log, which is created in the checkLogs folder of the instance directory, is generated.
java -jar archcheck.jar -p 5510 -a A1 -https -trustStore C:\ssl\truststore.jks -trustStorePassword TSPWD -keyStore C:\ssl\keystore.jks -keyStorePassword KSPWD- Sends the HTTPS request with client authentication to archive A1 by using the Collector Server that runs on the same server as the archcheck program and that uses the fixed port 5510 for the SSL communication. Truststore truststore.jks, which is stored in the C:\ssl directory and is secured by the password TSPWD, contains the certificate for the server authentication. Keystore keystore.jks, which is stored in the C:\ssl directory and is secured by the password KSPWD, contains the certificate for the client authentication. The file name of the log, which is created in the checkLogs folder of the instance directory, is generated.
