跳转至

Install the Palantir Foundry Connector 2.0 for SAP Applications（安装适用于 SAP 应用的 Palantir Foundry Connector 2.0）

The Palantir Foundry Connector 2.0 for SAP Applications ("Connector") is shipped as an SAP add-on to be installed via SAINT (SAP Add-On Installation Tool). The add-on is delivered in SAR format with the following filename pattern: FOUNDRY-SAPCONN-INST-SP00SPXX.SAR

SP00SPXX represents the installation files from SP00 to SPXX where XX is the support package level.

:::callout{theme="neutral"} If the Connector is being installed on BW/4HANA or S/4HANA, include Attribute Change Packages in the installation. As of SP22, these packages are included in the installation file. :::

These are the high-level steps required to setup the Connector:

  1. Download the installation packages.
  2. Install the Connector add-on via SAINT.
  3. Create a System-type (Type B) technical user for Foundry in SU01. This user is consumed by the Foundry agent for system-to-system calls and is not used to log into SAP GUI. If you plan to enable user-attributed writeback via OAuth 2.0 later, the User Type must be System.
  4. Run the Post Installation Wizard.

:::callout{theme="neutral"} Two distinct SAP users are involved in the installation. They are referred to throughout this page as follows:

Term Definition
Performing user (Basis administrator) A human SAP administrator (Dialog user) who logs in interactively to run SAINT, the Post Installation Wizard, and PFCG. Requires SAINT / PFCG / SU01 authorizations.
Foundry technical user A System-type (Type B) user, no interactive logon, used by the Foundry agent for RFC/HTTPS calls. Receives the /PALANTIR/* roles assigned by the Post Installation Wizard.
:::

Prerequisites

  • SAP_BASIS (the technical component version, applicable to both SAP NetWeaver and SAP S/4HANA systems) 7.4 SP5 or above

or

  • SAP_BASIS 7.5 (no minimum SP level)

These are minimum versions. The Connector supports all higher SAP_BASIS versions, including SAP S/4HANA releases based on SAP_BASIS 8.x (for example, SAP_BASIS 816).

Ensure that the following SAP note has been read and the relevant steps followed where applicable:

  • SAP OSS Note 2645739 - ABAP Add-On OCS package is not digitally signed

Install the Connector add-on

  1. Log into the SAP system client 000 with a user authorized to use SAINT.
  2. Run SAINT transaction.
  3. Import FOUNDRY-SAPCONN-INST-SP00SPXX.SAR to the SAP Server; select Installation package > Load Packages > From Front End.

:::callout{theme="neutral"} For some SAINT/SPAM versions, SPAM or SAINT settings can impact the installation process. Disable the Signature check not possible, SAP note 2520826 is not implemented item under the Checks during import section. Note that for some SPAM versions, this item has no description at all, but should still be disabled. :::

  1. Select Start for installation.
  2. The available packages are listed. If not, deactivate the filter by clicking the filter icon.
  3. Select Continue to go to next step.
  4. For Connector installation, select PALANTIR and PALCONN.
  5. Select Continue to move onto support package selection.
  6. Select the highest available support package from the list and make sure both components have the same SP level selected.
  7. Confirm the installation queue and click Continue.
  8. Select Continue in Dialog mode for Preparation phase, Continue in Background Immediately for other phases, and start installation.

:::callout{theme="neutral"} If warnings are flagged during the installation, follow the steps described in the warning message to resolve. In most cases, warning messages can be ignored for Connector and Remote Agent installations. In particular, the warning message with the heading "Open Data Extraction Requests" can be ignored because the installation does not make changes to DDIC structures and therefore will not cause open data extraction requests to terminate. :::

  1. Select Finish to complete the installation.

Run the Post Installation Wizard

The Connector Post Installation Wizard simplifies the setup activities after Connector add-on installation. To perform post-installation and configuration, a Basis administrator (the performing user, not the Foundry technical user) logs into the main client (not 000) via SAP GUI. The Post Installation Wizard runs under that administrator's session and configures the Foundry technical user; the Foundry technical user itself never logs in interactively. The Post Installation Wizard can be accessed either using transaction code /n/PALANTIR/POST_INST or from the Connector menu (transaction code: /n/PALANTIR/).

Wizard steps

There are 10 steps which can be run together or individually. To finish the installation, all steps need to be enabled. If this is not an SLT installation, disable Create SLT configuration. SLT configuration is detailed in step 7.

:::callout{theme="warning"} The performing user (the Basis administrator running the wizard) needs sufficient authorization to assign required authorization roles to the Foundry technical user. This process is similar to maintaining a user via the SU01 transaction code. If the user assignment is done separately, disable Assign Roles to Foundry User and Perform Healthcheck. :::

1. Run uninstall corrections

This step runs a background program which fixes SAP packages in the Connector Object Directory. This correction program can be run at any time with no adverse side effects.

2. Activate SICF services

This step activates two Connector services that are required for data transfer. Note that this can be done manually with the SICF transaction code if desired. The two services are:

  • /default_host/sap/palantir
  • /default_host/sap/opu/odata/palantir

3. Generate roles

The Connector has its own set of roles which are imported during installation. These roles stay in an ungenerated status after installation. If desired, mass generation of these roles can be done manually with the PFCG transaction code using Utilities > Mass Generation.

  • /PALANTIR/CONTENT_BEX_ALL
  • /PALANTIR/CONTENT_CDS_ALL
  • /PALANTIR/CONTENT_HANA_ALL
  • /PALANTIR/CONTENT_DM_ALL
  • /PALANTIR/CONTENT_EXT_ALL
  • /PALANTIR/CONTENT_FUNCTION_ALL
  • /PALANTIR/CONTENT_INFOPROV_ALL
  • /PALANTIR/CONTENT_SLT_ALL
  • /PALANTIR/CONTENT_TABLE_ALL
  • /PALANTIR/CONTENT_TCODE_ALL
  • /PALANTIR/DEBUG_USER
  • /PALANTIR/MONITORING
  • /PALANTIR/OAUTH_CLIENT
  • /PALANTIR/SERVICE_SLT
  • /PALANTIR/SERVICE_SLT_740
  • /PALANTIR/SERVICE_USER

4. Assign roles to the Foundry technical user

All Palantir roles in step 3 will be assigned to the SAP user that is defined in the selection screen. This should be the System-type Foundry technical user created in step 3 of the high-level steps above, not the performing user.

If this step generates error messages about role assignment, inability to retrieve user details or lack of authorization, this suggests that the performing user does not have sufficient permission. In this case, follow the suggestions in the error messages to correct the performing user's authorization and run the program again.

If this step generates error messages that suggest the Foundry technical user is locked, contact the owner of the lock to have it removed before running the program again.

5. Maintain default parameters

Resource check and continuous resource check parameters can be set via these selections. Default values are in the selection screen and can be changed according to your requirements. When the program is run with this selection, the Connector parameters will be modified according to the selected parameters. These parameters can also be maintained using transaction code /n/PALANTIR/PARAM.

Learn about performance parameters.

6. Check ICM Settings

This step verifies ICM settings, hostname and ports (for HTTP and HTTPS), and creates URLs that can be used to test the connection.

7. Create SLT configuration

:::callout{theme="warning"} This step is only relevant if the connection is via an SAP SLT Replication Server. :::

If the Connector is installed on top of an SAP SLT instance, a new SLT configuration (ODP) can be created by the Post-Installation Wizard. You can also create an SLT configuration using the LTRC transaction code.

The parameters of an SLT configuration are as follows:

Parameter Description
Context Name Unique configuration name.
Context Description Context Description that will be shown to the user in SAP transaction LTRC and in Foundry.
Data Transfer Jobs Number of data transfer jobs.
Initial Load Jobs Number of jobs for initial loads.
Calculation Jobs Number of calculation jobs for initial load range calculations.
Authorization Group No Authorization Group by default.
Replication Mode 1 - Real Time (Default); 2 - Time Interval; 3 - Time Schedule; 4 - On Demand.
Source RFC Destination Logical Destination - RFC Destination name of Source System.
Read from Single Client Enable if data will be read from a single client.
Allow Multiple Usage Enable if multiple usage is allowed.

8. Perform health checks

The Connector has various metrics to measure health in the installed SAP system. The connector performs health checks in the following categories:

  • AGENT: Checks RFC connection and source system authorizations. Only relevant for remote connections via a gateway.
  • AUTHORIZATION: Checks whether the Foundry user has any missing authorization in SM53.
  • CONNECTOR: Checks whether the Connector housekeeping job is scheduled in the system.
  • ROLE: Checks the Foundry user's roles and authorization profiles.
  • SLT: Checks whether SLT configuration is correct and healthy; for example, whether BADI_Implementation is active, Context is active, SLT housekeeping job is scheduled, or source system connection is working.

9. Browser test URLs

After installation, it is important to check if the Connector is running properly by conducting connectivity tests with a web browser. The required URLs are generated by the Post-Installation Wizard.

There are several different tests available. The first and second test are synchronous calls to the Connector service; the third and fourth are for batch extraction.

  • About: About page of the Connector.
  • T000 Table: Direct extraction of T000 table with table object type.
  • T000 with Paging-Init: Initialization of background extraction for T000 table with table object type.
  • T000 with Paging-Read Page 1: First page will be retrieved for the process initialized by the previous URL.

10. Source definition template for Foundry

After running the program with Source Definition in Foundry checked, a new tab, “Source Definition”, will be shown with details for the source configuration in Foundry.

Security and authorization roles

More details can be found in Authorization roles.

Performance parameters

The Connector has the following performance parameters to avoid unwanted system load when the system resources are insufficient to serve Foundry. These settings are compared with ST06 values.

:::callout{theme="neutral"} The default parameter values listed below are for a fresh install of the latest connector version. :::

  • MEMORY_FREE: Free memory percentage. If this percentage is lower than the system default or user-defined value, extraction stops. Connector default is 5%.
  • CPU_IDLE: CPU idle percentage. Connector default is 5%.
  • CPU_USER: CPU utilization by user transactions. Connector default is 80%.
  • CPU_LOAD: Total CPU utilization. Connector default is 80%.

:::callout{theme="neutral"} ST06 key figures are served by SAP to the Connector. If Enhanced Monitoring for virtualization is activated, the operating system-specific information is enriched by virtualization-specific information. This may affect ST06 figures and misguide the Connector. Refer to SAP OSS Article 2266266 for further details. :::

Initial system defaults are deliberately conservative. If you wish to override them to be more permissive, maintain via the /n/PALANTIR/PARAM transaction.

The following parameters are used to enable or disable resource checks:

Param Id Param Name Param Values Default Description
SYSTEM CPU_CHECK TRUE / FALSE TRUE Enables or disables CPU checks.
SYSTEM MEMORY_CHECK TRUE / FALSE TRUE Enables or disables MEMORY checks.
SYSTEM RESOURCE_CHECK TRUE / FALSE TRUE Enables or disables RESOURCE checks. If FALSE, all checks are disabled; if TRUE, other parameters (CPU_CHECK and MEMORY_CHECK) are checked.
SYSTEM CONTINUOUS_RESOURCE_CHECK TRUE / FALSE TRUE Enables resource checks for all requests (init and all paging requests). If FALSE, resource checks are only carried out for the init request.
SYSTEM PROCESS_CHECK TRUE / FALSE TRUE Enables checks on the minimum number of permitted work processes; works in conjunction with PROCESS_MIN_BG and PROCESS_MIN_DIA.
SYSTEM_THRESHOLD PROCESS_MIN_BG numeric 1 Minimum required number of background process available on the SAP Application Server.
SYSTEM_THRESHOLD PROCESS_MIN_DIA numeric 1 Minimum required number of dialog process available on the SAP Application Server.

To check the actual values and parameter values, you can use the system object and resource function from a browser:

https://<sap-server>:<port>/sap/palantir/system?obj=resource

Note that this URL is an SAP system URL; you should ensure that this resource is accessible.

Output will be of this format:

MSGTYP  MSGTXT
S   Current CPU_LOAD value : 0,01 | system threshold value : 95,00
S   Current CPU_USER value : 1,00 | system threshold value : 0,01
S   Current CPU_IDLE value : 99,00 | system threshold value : 5,00
S   Current free memory percentage : 24,22 | system threshold value : 11,00
S   Current PROCESS_MIN_BG value : 5 | system threshold value : 2
S   Current PROCESS_MIN_DIA value : 9 | system threshold value : 2
S   Resource check is Active
S   CPU Load check is Active
S   Memory consumption check is Active
S   Process availability check is Active

中文翻译

安装适用于 SAP 应用的 Palantir Foundry Connector 2.0

适用于 SAP 应用的 Palantir Foundry Connector 2.0（以下简称"连接器"）以 SAP 附加组件（add-on）形式提供，需通过 SAINT（SAP 附加组件安装工具）进行安装。该附加组件以 SAR 格式交付，文件名模式为：FOUNDRY-SAPCONN-INST-SP00SPXX.SAR

SP00SPXX 表示从 SP00 到 SPXX 的安装文件，其中 XX 为支持包级别（support package level）。

:::callout{theme="neutral"} 如果在 BW/4HANA 或 S/4HANA 上安装连接器，请在安装中包含属性变更包（Attribute Change Packages）。自 SP22 起，这些包已包含在安装文件中。 :::

以下是设置连接器所需的高级步骤：

  1. 下载安装包。
  2. 通过 SAINT 安装连接器附加组件。
  3. 在 SU01 中为 Foundry 创建一个系统类型（类型 B）的技术用户（technical user）。该用户由 Foundry 代理用于系统间调用，不用于登录 SAP GUI。如果后续计划启用通过 OAuth 2.0 的用户属性写回，则用户类型必须为 System。
  4. 运行安装后向导。

:::callout{theme="neutral"} 安装过程中涉及两个不同的 SAP 用户。本页面中分别称为：

术语 定义
执行用户（基础架构管理员） 人类 SAP 管理员（对话用户），通过交互方式登录以运行 SAINT、安装后向导和 PFCG。需要 SAINT / PFCG / SU01 授权。
Foundry 技术用户 系统类型（类型 B）用户，无交互登录，由 Foundry 代理用于 RFC/HTTPS 调用。接收安装后向导分配的 /PALANTIR/* 角色。
:::

前提条件

  • SAP_BASIS（技术组件版本，适用于 SAP NetWeaver 和 SAP S/4HANA 系统）7.4 SP5 或更高版本

或

  • SAP_BASIS 7.5（无最低 SP 级别要求）

以上为最低版本要求。连接器支持所有更高版本的 SAP_BASIS，包括基于 SAP_BASIS 8.x 的 SAP S/4HANA 版本（例如 SAP_BASIS 816）。

请确保已阅读以下 SAP 说明，并在适用时遵循相关步骤：

  • SAP OSS 说明 2645739 - ABAP 附加组件 OCS 包未进行数字签名

安装连接器附加组件

  1. 使用具有 SAINT 使用权限的用户登录 SAP 系统客户端 000。
  2. 运行 SAINT 事务代码。
  3. 将 FOUNDRY-SAPCONN-INST-SP00SPXX.SAR 导入 SAP 服务器；选择 安装包 > 加载包 > 从前端加载。

:::callout{theme="neutral"} 对于某些 SAINT/SPAM 版本，SPAM 或 SAINT 设置可能会影响安装过程。请在 导入时检查 部分禁用 无法进行签名检查，未实施 SAP 说明 2520826 项。请注意，对于某些 SPAM 版本，此项可能完全没有描述，但仍应禁用。 :::

  1. 选择 开始 进行安装。
  2. 系统会列出可用包。如果未列出，请点击筛选图标停用筛选器。
  3. 选择 继续 进入下一步。
  4. 对于连接器安装，选择 PALANTIR 和 PALCONN。
  5. 选择 继续 进入支持包选择。
  6. 从列表中选择最高可用支持包，并确保两个组件选择相同的 SP 级别。
  7. 确认安装队列并点击 继续。
  8. 对于准备阶段选择 在对话框模式下继续，对于其他阶段选择 立即在后台继续，然后开始安装。

:::callout{theme="neutral"} 如果安装过程中出现警告，请按照警告消息中的步骤进行解决。在大多数情况下，连接器和远程代理安装可以忽略警告消息。特别是标题为"打开数据提取请求"的警告消息可以忽略，因为安装不会对 DDIC 结构进行更改，因此不会导致打开的数据提取请求终止。 :::

  1. 选择 完成 以结束安装。

运行安装后向导

连接器安装后向导简化了连接器附加组件安装后的设置活动。为执行安装后配置，基础架构管理员（执行用户，非 Foundry 技术用户）需通过 SAP GUI 登录主客户端（非 000）。安装后向导在该管理员的会话中运行，并配置 Foundry 技术用户；Foundry 技术用户本身从不交互登录。可通过事务代码 /n/PALANTIR/POST_INST 或连接器菜单（事务代码：/n/PALANTIR/）访问安装后向导。

向导步骤

共有 10 个步骤，可一起运行或单独运行。要完成安装，所有步骤均需启用。如果不是 SLT 安装，请禁用 创建 SLT 配置。SLT 配置详见步骤 7。

:::callout{theme="warning"} 执行用户（运行向导的基础架构管理员）需要足够的授权才能为 Foundry 技术用户分配所需的授权角色。此过程类似于通过 SU01 事务代码维护用户。如果用户分配单独进行，请禁用 将角色分配给 Foundry 用户 和 执行健康检查。 :::

1. 运行卸载修正

此步骤运行一个后台程序，用于修复连接器对象目录中的 SAP 包。此修正程序可随时运行，无不良副作用。

2. 激活 SICF 服务

此步骤激活数据传输所需的两个连接器服务。请注意，如果需要，也可以使用 SICF 事务代码手动完成。这两个服务是：

  • /default_host/sap/palantir
  • /default_host/sap/opu/odata/palantir

3. 生成角色

连接器拥有自己的一组角色，在安装期间导入。安装后这些角色保持未生成状态。如果需要，可以使用 PFCG 事务代码通过 实用程序 > 批量生成 手动批量生成这些角色。

  • /PALANTIR/CONTENT_BEX_ALL
  • /PALANTIR/CONTENT_CDS_ALL
  • /PALANTIR/CONTENT_HANA_ALL
  • /PALANTIR/CONTENT_DM_ALL
  • /PALANTIR/CONTENT_EXT_ALL
  • /PALANTIR/CONTENT_FUNCTION_ALL
  • /PALANTIR/CONTENT_INFOPROV_ALL
  • /PALANTIR/CONTENT_SLT_ALL
  • /PALANTIR/CONTENT_TABLE_ALL
  • /PALANTIR/CONTENT_TCODE_ALL
  • /PALANTIR/DEBUG_USER
  • /PALANTIR/MONITORING
  • /PALANTIR/OAUTH_CLIENT
  • /PALANTIR/SERVICE_SLT
  • /PALANTIR/SERVICE_SLT_740
  • /PALANTIR/SERVICE_USER

4. 将角色分配给 Foundry 技术用户

步骤 3 中的所有 Palantir 角色将分配给选择屏幕上定义的 SAP 用户。该用户应为上述高级步骤第 3 步中创建的系统类型 Foundry 技术用户，而非执行用户。

如果此步骤生成关于角色分配、无法检索用户详细信息或缺少授权的错误消息，则表明执行用户权限不足。在这种情况下，请按照错误消息中的建议修正执行用户的授权，然后重新运行程序。

如果此步骤生成错误消息表明 Foundry 技术用户被锁定，请联系锁定的所有者解除锁定，然后重新运行程序。

5. 维护默认参数

可通过这些选择设置资源检查（resource check）和持续资源检查（continuous resource check）参数。选择屏幕中提供默认值，可根据需求进行更改。使用此选择运行程序时，连接器参数将根据所选参数进行修改。这些参数也可使用事务代码 /n/PALANTIR/PARAM 进行维护。

了解性能参数。

6. 检查 ICM 设置

此步骤验证 ICM 设置、主机名和端口（用于 HTTP 和 HTTPS），并创建可用于测试连接的 URL。

7. 创建 SLT 配置

:::callout{theme="warning"} 此步骤仅适用于通过 SAP SLT 复制服务器进行连接的情况。 :::

如果连接器安装在 SAP SLT 实例之上，安装后向导可以创建新的 SLT 配置（ODP）。也可以使用 LTRC 事务代码创建 SLT 配置。

SLT 配置的参数如下：

参数 描述
上下文名称 唯一的配置名称。
上下文描述 将在 SAP 事务 LTRC 和 Foundry 中向用户显示的上下文描述。
数据传输作业数 数据传输作业的数量。
初始加载作业数 初始加载的作业数量。
计算作业数 用于初始加载范围计算的计算作业数量。
授权组 默认无授权组。
复制模式 1 - 实时（默认）；2 - 时间间隔；3 - 时间计划；4 - 按需。
源 RFC 目标 逻辑目标 - 源系统的 RFC 目标名称。
从单一客户端读取 如果数据将从单一客户端读取，则启用。
允许多重使用 如果允许多重使用，则启用。

8. 执行健康检查

连接器具有多种指标，用于衡量已安装 SAP 系统的健康状况。连接器在以下类别中执行健康检查：

  • AGENT：检查 RFC 连接和源系统授权。仅适用于通过网关的远程连接。
  • AUTHORIZATION：检查 Foundry 用户在 SM53 中是否缺少任何授权。
  • CONNECTOR：检查连接器维护作业是否已在系统中调度。
  • ROLE：检查 Foundry 用户的角色和授权配置文件。
  • SLT：检查 SLT 配置是否正确且健康；例如，BADI_Implementation 是否激活、上下文是否激活、SLT 维护作业是否已调度、源系统连接是否正常工作。

9. 浏览器测试 URL

安装后，通过 Web 浏览器进行连接测试以检查连接器是否正常运行非常重要。所需的 URL 由安装后向导生成。

有几种不同的测试可用。第一个和第二个测试是对连接器服务的同步调用；第三个和第四个用于批量提取。

  • 关于： 连接器的关于页面。
  • T000 表： 使用 table 对象类型直接提取 T000 表。
  • 带分页初始化的 T000： 使用 table 对象类型初始化 T000 表的后台提取。
  • 带分页读取第 1 页的 T000： 将检索由前一个 URL 初始化的进程的第一页。

10. Foundry 的源定义模板

在选中"Foundry 中的源定义"后运行程序，将显示一个名为"源定义"的新选项卡，其中包含 Foundry 中源配置的详细信息。

安全和授权角色

更多详情请参见授权角色。

性能参数

连接器具有以下性能参数，以避免在系统资源不足以服务 Foundry 时产生不必要的系统负载。这些设置与 ST06 值进行比较。

:::callout{theme="neutral"} 下面列出的默认参数值适用于最新连接器版本的全新安装。 :::

  • MEMORY_FREE： 空闲内存百分比。如果此百分比低于系统默认值或用户定义值，则停止提取。连接器默认值为 5%。
  • CPU_IDLE： CPU 空闲百分比。连接器默认值为 5%。
  • CPU_USER： 用户事务的 CPU 利用率。连接器默认值为 80%。
  • CPU_LOAD： 总 CPU 利用率。连接器默认值为 80%。

:::callout{theme="neutral"} ST06 关键指标由 SAP 提供给连接器。如果激活了虚拟化增强监控，则操作系统特定信息会通过虚拟化特定信息得到丰富。这可能会影响 ST06 指标并误导连接器。更多详情请参阅 SAP OSS 文章 2266266。 :::

初始系统默认值故意设置得较为保守。如果您希望覆盖这些值使其更宽松，请通过 /n/PALANTIR/PARAM 事务进行维护。

以下参数用于启用或禁用资源检查：

参数 ID 参数名称 参数值 默认值 描述
SYSTEM CPU_CHECK TRUE / FALSE TRUE 启用或禁用 CPU 检查。
SYSTEM MEMORY_CHECK TRUE / FALSE TRUE 启用或禁用内存检查。
SYSTEM RESOURCE_CHECK TRUE / FALSE TRUE 启用或禁用资源检查。如果为 FALSE，则所有检查均禁用；如果为 TRUE，则检查其他参数（CPU_CHECK 和 MEMORY_CHECK）。
SYSTEM CONTINUOUS_RESOURCE_CHECK TRUE / FALSE TRUE 对所有请求（初始请求和所有分页请求）启用资源检查。如果为 FALSE，则仅对初始请求执行资源检查。
SYSTEM PROCESS_CHECK TRUE / FALSE TRUE 启用对允许的最小工作进程数的检查；与 PROCESS_MIN_BG 和 PROCESS_MIN_DIA 配合使用。
SYSTEM_THRESHOLD PROCESS_MIN_BG 数字 1 SAP 应用服务器上可用的最小后台进程数。
SYSTEM_THRESHOLD PROCESS_MIN_DIA 数字 1 SAP 应用服务器上可用的最小对话进程数。

要检查实际值和参数值，您可以从浏览器使用系统对象和资源功能：

https://<sap-server>:<port>/sap/palantir/system?obj=resource

请注意，此 URL 是 SAP 系统 URL；您应确保此资源可访问。

输出格式如下：

MSGTYP  MSGTXT
S   当前 CPU_LOAD 值 : 0,01 | 系统阈值 : 95,00
S   当前 CPU_USER 值 : 1,00 | 系统阈值 : 0,01
S   当前 CPU_IDLE 值 : 99,00 | 系统阈值 : 5,00
S   当前空闲内存百分比 : 24,22 | 系统阈值 : 11,00
S   当前 PROCESS_MIN_BG 值 : 5 | 系统阈值 : 2
S   当前 PROCESS_MIN_DIA 值 : 9 | 系统阈值 : 2
S   资源检查已激活
S   CPU 负载检查已激活
S   内存消耗检查已激活
S   进程可用性检查已激活