AIX高可用性集群多处理：Smart Assist开发者指南

版权申诉

134 浏览量更新于2024-06-21 收藏 816KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"HACMP Smart Assist开发者指南-80" 《高可用性集群多处理(AIX)Smart Assist开发者指南》是专为AIX系统设计的一份详细的技术文档，旨在帮助开发者理解和利用HACMP（High Availability Cluster Multi-Processing）的Smart Assist功能。这份文档适用于HACMP版本6.1及其后续的更新和修改。文档的重要注意事项指出，在使用此信息及它支持的产品前，用户应先阅读"通知"部分，这部分在第63页。这份指南的第四版发行于2009年10月，提供了关于HACMP Version 6.1的相关信息。文档内容涵盖了多个方面，包括： 1. **关于文档**：这部分可能介绍了文档的目的、目标读者和文档结构，帮助读者快速定位所需信息。 2. **高亮显示**：可能涉及如何在文档中突出关键信息，以便读者更快地识别重要点。 3. **AIX中的大小写敏感性**：AIX操作系统在处理文件名和命令时的大小写规则可能会对开发者至关重要。 4. **ISO9000**：可能简述了与ISO9000质量管理体系相关的标准和实践，以及它们如何应用于HACMP环境。 5. **HACMP出版物**：列举了关于HACMP的其他官方文档，可能包含参考文献和进一步学习的资源。 6. **HACMP/XD出版物**：HACMP/XD可能扩展了HACMP的功能，这部分可能介绍了相关联的文档集合。 7. **HACMP Smart Assist出版物**：列出了专门针对Smart Assist的其他资料，为开发者提供更深入的学习材料。 8. **Smart Assist开发者指南**：这部分是文档的核心，详细介绍了如何进行Smart Assist的开发工作，包括其概念、工作原理和实施步骤。《Smart Assist开发者指南》的开头部分会介绍Smart Assist的基本概念，帮助开发者理解这个工具如何增强HACMP的性能和可用性。它可能涵盖了Smart Assist的架构、功能特性、开发流程以及如何集成到现有集群环境中。此外，还可能包含示例代码、故障排除策略和最佳实践，以确保开发者能够高效且稳定地利用HACMP的智能辅助功能。这份指南对于那些希望在AIX环境下构建高可用性解决方案的开发者来说是一份宝贵的资源，它通过深入的指导和支持，使得复杂的集群管理变得更为简单和可靠。

资源详情

资源推荐

The Make Applications Highly Available SMIT menu lists the functionality the Smart Assist offers.

Smart Assist Basics of Operation This section presents information on how a Smart Assist works in more

detail. It discusses what issues you must consider and what code you need to write for your own Smart

Assist.

Smart Assist identifiers and component identifiers

The Smart Assist Identifier and Component Identifier(s) uniquely identify a particular Smart Assist

component within the Smart Assist framework.

The first step in developing a Smart Assist is defining these identifiers. The Smart Assist Identifier reflects

the target application such as DB2, Oracle or WebSphere. Examples of Smart Assist IDs are "DB2_8.0" for

DB2 and "Oracle_10G" for Oracle Application Server and RDBMS. Note that in these particular cases the

Identifier also reflects the version of the application. To ensure version compatibility, it may be useful to

develop separate Smart Assists for different versions of the target application. The Smart Assist

Component Identifiers are used to sub-classify a Smart Assist into the various sub-components of an

application, and/or into the sub-features of the Smart Assist. In the case of DB2 and Oracle, the database

instances can be configured in different ways; therefore several Component Identifiers are needed, one for

each way the database can be configured. Examples of DB2 Component Identifiers are shown in the table

that follows:

Component Identifier DB2 Component Name (user visible)

DB2_8.0_NON_DPF_SINGLE DB2 Single Instance

DB2_8.0_NON_DPF_MUTUAL DB2 Mutual Takeover

In the case of WebSphere, the Component Identifiers consists of several distinct functional components (a

web server, a log server, etc.), and so each component has its own Component Identifier. Examples of

WebSphere Component IDs are shown in the following table:

Component Identifier WebSphere Component Name (user visible)

WAS_6.0_IHS_SERVER IHS HTTP Server

WAS_6.0_APP_SERVER WebSphere Application Server (Standalone)

WAS_6.0_DEPLOYMENT_MANAGER WebSphere Deployment Manager

WAS_6.0_TRANSACTION_LOG_ RECOVERY WebSphere Cluster Transaction Log

Packaging and installing

You can package your Smart Assist using tools appropriate to your environment.

The LPP package management system is the preferred method of packaging files on the AIX platform,

but you can use RPMs, or other package and/or file management tools that provide the ability to:

v Install

v Remove

v Update

v Pre-require the HACMP fileset cluster.es.assist.core to be installed prior to attempting to install the

new Smart Assist fileset.

Adding a Smart Assist at install time

When Smart Assist is installed, it performs two tasks for each of its components.

These tasks are:

Smart Assist developer’s guide 5

v Call the UI API routine claddsa which adds information about each component in the HACMPsa ODM

for later use by the framework. Some items specified at this time are the discovery script path and the

Add and Modify SMIT menu paths.

v Add the particular Add and Modify SMIT screens specified for each component to the SMIT ODM for

use when the end user invokes the Smart Assist. Any other dependent SMIT menus must be added to

the ODM at this time as well.

Here is an example of a claddsa call:

claddsa -s “Apache_2” -c “APACHE_2.0_HS_SSL” \

COMPONENT_ID=“APACHE_2.0_HS_SSL” \

SMARTASSIST_VERSION=“1.0” \

SMIT_ADD=“clsa_apache_add” \

SMIT_MODIFY=“clsa_apache_modify \

SMIT_ADD_TYPE=”d“ \ SMIT_MODIFY_TYPE=”d“ \

REQUIRE_SITES=”false“ \

DISCOVERY_COMMAND=”/usr/es/sbin/cluster/sa/apache/sbin/discover“ \

DEINSTALLATION_COMMAND=”/usr/es/sbin/cluster/sa/apache/sbin/discover“ \

REGISTRATION_COMMAND=”/usr/es/sbin/cluster/sa/apache/sbin/register“ \

DEREGISTRATION_COMMAND=”/usr/es/sbin/cluster/sa/apache/sbin/deregister“ \

MIGRATION_COMMAND=”/usr/es/sbin/cluster/sa/sample/sbin/migrate“ \

SA_ROOT=”/usr/es/sbin/cluster/sa/sample/sbin/“ \

SA_NAME=”Sample Smart Assist“ \

COMPONENT_NAME=”Sample Smart Assist Component“

See Smart Assist commands for details on the call.

Related concepts:

“Smart Assist commands” on page 18

Use these topics as reference for the commands you use to develop a Smart Assist for HACMP. Each

topic lists syntax diagrams and provides examples for using each command.

Directory structure

Smart Assists should adhere to the directory structure underneath the Smart Assist name.

/usr/es/sbin/cluster/sa/SmartAssistID

Note: The SmartAssistID is the same Identifier used in the claddsa command.

Directory Contents

./sbin/ executables, and scripts that need to be executed on behalf of the Smart Assist; this includes any scripts run

via SMIT

./appserver/ HACMP application server start and stop scripts

./monitor/ HACMP custom application monitors

./verification/ HACMP cluster custom verification files for performing validation of configured applications

./smit A collection of SMIT menus to be added to the HACMP cluster. If the Smart Assist developer does not

provide a mechanism at install time to add these ODM stanzas, it is required that the framework be able to

find the SMIT ODM stanzas in this directory. One or more SMIT ODM stanzas may reside in this directory

with the file extension 'odm'.

There are no ILS message catalog requirements. ILS message catalogs are not required to be installed in a

particular location. However if you do use AIX msgcat catalogs, they must be installed in a location

readable by the msgcat binary.

Developing SMIT panels

The Smart Assist you develop must fit into the current HACMP SMIT panels designed for Smart Assists.

Note: See the IBM

documentation for instructions on coding SMIT.

6 High Availability Cluster Multi-Processing for AIX: Smart Assist developer's guide

The SMIT menus are either installed via the Smart Assist at the time of installation, or alternatively the

Smart Assist can request that the registration API inject the ODM stanzas. The preferred approach is to

request the registration API to add the ODM stanzas, so that the Smart Assist deinstallation process can

remove the ODM entries on your behalf.

The four SMIT stanza types: sm_cmd_opt, sm_cmd_hdr, sm_menu_opt, sm_name_hdr are supported by

the HACMP registration API. The Smart Assist framework keeps track of the entries added into the SMIT

ODM stanzas, and at the time of deinstallation removes the appropriate entries simply by calling the

deregistration command. If the Smart Assist performs the operation of adding the entries, then it is

assumed by the framework that the Smart Assist will also remove the entries upon deinstallation.

There are several points in the Smart Assist framework where control will transfer from the Smart Assist

framework to your new Smart Assist. You must use the correct Smart Assist Identifiers for the SMIT

ODM classes in order for control to properly transfer from one session to another.

Add an application to the HACMP configuration

The Add an Application to the HACMP Configuration SMIT session goes through a number of

transitions before finally passing control off to the Smart Assist.

The user must first specify nodes for the cluster (if nodes exist). Then if the Smart Assist requires sites

and no sites exist, the user must specify the sites for the cluster. After both of the above tasks are

accomplished, the user is then presented a selector screen showing the available applications. Once the

user selects an application, control is passed along to the Smart Assist Add screen.

If nodes and/or sites were specified by the user, then the discovery information within SMIT would

provide the following name / value pairs:

#nodes:sites: SmartAssistID_ComponentID

nodeA nodeB:siteA siteB:<SmartAssistID_ComponentID>

Change/show an application's HACMP configuration

Similar to the Add An Application To The Hacmp Configuration SMIT screen, users will select a

particular application already defined to HACMP, and then modify the existing values.

Control will be passed off to the Smart Assist once the user selects the application to change or show.

Manage your applications

The Manage Your Applications SMIT screen is different from the Add and Change/Show SMIT screens

in that it transfers control over to a SMIT menu system written by the Smart Assist, rather than to a SMIT

dialog.

After selecting the Manage Your Applications SMIT screen, the user is presented a list of applications

that are already configured and have management screens. Once the user selects a particular component

of the Smart Assist, control is passed to the Smart Assist menus. The Smart Assist developer must

provide a sm_menu_opt SMIT ODM with an id of clsa-manage <your_next_id>.

General guidelines for developing SMIT

Each Smart Assist will need two developing SMIT displays at a minimum: One for adding an application

and one for modifying an existing configuration. It is beyond the scope of this document to explain how

to develop SMIT, but we can mention some requirements that facilitate a smooth flow from the Smart

Assist menus to the displays that add or modify the application's configuration within HACMP. The

Smart Assist Framework will also supply some useful information you can choose to use.

You may find that you will need additional selectors prior to navigating to the SMIT display to add your

application. For instance, if you are trying to make a database instance highly available, your Smart

Assist may need to have the user select a specific database instance from a list. In this case, you may

choose to have a selector rather than a display as an entry point. SMIT menus are not an option (due to

Smart Assist developer’s guide 7

SMIT requirements). To register the entry points for Add and Modify, when the Smart Assist is installed,

the clquerysa command that needs to run must specify these parameters:

SMIT_ADD String containing the ID for the SMIT stanza.

SMIT_ADD_TYPE String "d" for display, "n" for selector. "d" by default.

SMIT_MODIFY String containing the ID for the SMIT stanza.

SMIT_MODIFY_TYPE String "d" for display, "n" for selector. "d" by default.

The Smart Assist Framework will provide values for the following cooked field names for use by the

SMIT display or selector:

sa_id Smart Assist ID

component_id Component ID

cluster_name Name of the cluster

nodes Space-separated list of nodes on which the component was installed.

application_id (for modify only) the application Identifier

The Smart Assist may need to offer a way of getting additional information from the user, or give the

user operations to perform other than add, change/show, remove, and test.

You as the developer can provide additional SMIT menus, selectors, and dialogs under the Manage Your

Applications menu heading of SMIT (clsa_manage). Your first sm_menu_opt stanza will need to start

with a sequence number that does not collide with any of the existing Smart Assist sequence numbers.

The fileset packaging for your Assist should check the available SMIT IDs and use the next available ID,

or pre-assign a set of IDs and check to ensure that range is available. If the ID is not available, the SMIT

sm_menu_opt IDs will need to be changed by your installation script.

Note: As of this writing, sequence numbers of 100 and below and 900 and above are reserved for

clsa_manage.

Smart Assist component discovery

When you select the main Smart Assist Add an Application to the HACMP Configuration screen, the

discovery scripts provided by each added Smart Assist component are called.

Each script checks to see if the base application (such as DB2 or WebSphere) is installed on the nodes of

the cluster, and then checks to ensure the sub-component or sub-feature can be used on the local node

where the discovery command is executed. If the functionality or application is installed, the Smart Assist

is ”enabled“ on the menu and the node where the feature or application sub-component is accessible will

be listed next to the Smart Assist. This gives the user a menu constructed in real-time indicating what

applications are installed, and which Smart Assists are usable on which cluster nodes. If the application is

not installed, the user can install it and restart the Smart Assist.

The discovery script is run on each node where the Smart Assist is installed; it is up to the Smart Assist

developer whether to require the base application be installed on all defined cluster nodes. To ensure that

multiple nodes, or all cluster nodes contain the Smart Assist fileset, you can use the parameterized

verification functionality. This functionality is described in the section Parameterized verification check

files.

8 High Availability Cluster Multi-Processing for AIX: Smart Assist developer's guide

剩余79页未读，继续阅读

weixin_40191861_zj

粉丝: 69
资源: 1万+

会员权益专享

AIX高可用性集群多处理：Smart Assist开发者指南

HACMP Smart Assist for DB2 user's guide-48

hacmp、集群、多实例三种实现mq

hacmp 日常系统管理

redia和MySQL怎么保证同步

MindeNLP+MusicGen-音频提示生成

WNM2027-VB一款SOT23封装N-Channel场效应MOS管

线上营销推广策略设计与效果评估研究

钢铁集团智慧工厂信息化建设解决方案两份文档.pptx

2024年投资策略-AIGC海阔凭鱼跃，数据要素破浪会有时.pdf

2023中国文化产业和旅游业年度盘点报告（2022）-北京京和文旅发展研究院.pdf

英锐恩电子烟相关芯片推荐

2024年东南亚断续器市场深度研究及预测报告.pdf

ElasticSearch.pdf

智慧农牧业解决方案两份文件.pptx

Object-C语言教程&案例.md

2023中国制造业的可持续生存之道-中国企业ESG实践调研问卷分析报告-IMA(1).pdf

Brand Finance：2023年银行业500强(1).pdf

钢铁集团智慧工厂信息化建设解决方案双份资料.pptx

Maven安装指南：详细步骤与环境配置教程

2023医药行业薪酬白皮书-锐仕方达(1).pdf

会员权益专享

最新资源