3.2.7 2.1.x向2.2.x升级

iTop的版本2.2.0与以前的2.x版本(2.1.0、2.0.3、2.0.2…)完全向后兼容,但是此版本引入了许多重大更改。

安装iTop的新先决条件:具有Zip扩展名的PHP 5.3.0(而不是5.2.0)和Graphviz.

如果从2.2.0-beta版本中的升级开始,请确保iTop配置文件中的价值查询_cache_enabled未设置为false。如果是这样,请将变更价值设置为true或从配置文件中完全删除该行。将价值设置为false会导致价值严重减速。

可用性

以下更改可能在用户体验上具有影响度:

  • 应用的配色方案已更改为与Combodo的新品牌一致。
  • 交互式导出已进行了重新加工,以提供更好的灵活性和其他输出格式。
  • 影响度分析图不再使用Flash,现在提供了其他上下文信息,但外观却大不相同。
  • 现在仅允许具有权利bulk_read的用户执行批量导出。 (默认情况下,在iTop中,每个人都具有bulk_read权利)。

导出

菜单管理工具导出现在指向页面导出-v2.php。该页面可以以交互方式或脚本方式(从Web或命令行界面)使用。

自从iTop的上一个版本以来,主要的变更是,新的导出将导出的字段顺序纳入账号,并支持更多格式(某些格式特定的选项完全支持xlsx和PDF格式)。

我们建议您将新导出-v2.php页面上的现有脚本测试替换为导出。php,并尽可能迁移它们。

旧的导出。php仍可使用,未经修改,可实现100%向后兼容。

请注意,如果您自定义简档(角色):出于安全的原因,现在仅允许对指定的对象类具有批量读取特权的用户使用批量导出。这适用于导出。php和导出-v2.php页面。但是,这在默认的iTop导出中是透明的,因为所有用户都被授予了此特权。

XML自定义

XML格式已升级为版本1.2.

这个新的版本支持XML中关系(例如影响或依赖)的定义(和更改)。

如果您自定义了这种关系(通过PHP中的GetRelationQueries()方法),我们建议您迁移到更灵活的XML定义并支持冗余规则的定义。

尽管如此,iTop 2.2.0仍支持方法GetRelationQueries()的重载。

由于存在变更,并且如果通过自定义方式删除了属性,则可能需要调整XML。

以下是删除需要额外调整的属性列表:

属性
FunctionalCIcontacts_list, applicationsolution_list, softwares_list
ApplicationSolutionbusinessprocess_list
Middlewaremiddlewareinstance_list
DBServerdbschema_list
WebServerwebapp_list
Enclosuredevice_list
StorageSystemlogicalvolume_list
SANSwitchdatacenterdevice_list
TapeLibrarytapes_list
NASnasfilesystem_list
LogicalVolumes ervers_list, virtualdevices_list
VirtualHostvirtualmachine_list
Hypervisorfarm_id

示例:假设您已删除属性FunctionalCI :: applicationsolution_list。

您将必须删除相应的关系路径:

<itop_design xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2">
  <classes>
    <class id="FunctionalCI">
      <relations>
        <relation id="impacts">
          <neighbours>
            <neighbour id="applicationsolution" _delta="delete"/>
...

如果不这样做,将在请求任何类型的对象的“详细信息”时产生以下错误:

系影响的错误定义sFunctionalCIIapplicationsolution:FunctionalCI类中的未知属性applicationsolution_list

模块开发人员

您必须升级才能将工具包iTopDataModelToolkit-2.2.zip。该版本仍与旧版本的iTop向后兼容。

对于PHP开发人员,请注意以下变更:所有“搜索”的新基类现在是抽象类DBSearch。这个新类有两个子类:前一个DBObjectSearch和新的DBUnionSearch。

检查您的自定义函数方法:每当将参数键入为DBObjectSearch时,建议变更将其推荐给DBSearch。这样可以确保如果传递的查询的类型为DBUnionSearch(与2.2.0:UNION查询中引入的新能力相对应),您的代码仍然可以正常工作。

身份验证页面和自定义门户

为了支持自定义门户,API LoginWebPage :: DoLogin稍有更改。因此,必须将所有应接受门户用户的页面的身份验证更改为:

LoginWebPage::DoLogin(false /* bMustBeAdmin */, true /* IsAllowedToPortalUsers */);

至:

LoginWebPage::DoLoginEx(null /* any portal */, false);

如果该页面不适合门户用户访问,则相应的身份验证代码为:

LoginWebPage::DoLogin(false /* bMustBeAdmin */, false/* IsAllowedToPortalUsers */);

REST/JSON API

检查RESTTJSON服务文档#changes_history 适用于API的最新版本。

出于安全的原因,现在已禁止用户帐户和简档门户用户一起使用RESTTJSON Web服务。如果仅使用一种Web服务来检查用户的凭据,请调整代码以使用新的core/check_credentials用户。

请注意,如果您自定义简档(角色):出于安全的原因,现在仅允许对指定的对象类具有批量读取特权的用户使用core/get和 core/get_related操作。但是,这在默认的iTop模型中是透明的,因为所有用户都被授予了此特权。

原创链接:https://www.itophub.io/wiki/page?id=2_7_0%3Ainstall%3A210_to_220_migration_notes


2.1.0 to 2.2.0 Migration Notes

The version 2.2.0 of iTop is fully backward compatible with the previous 2.x versions (2.1.0, 2.0.3, 2.0.2…), however this version introduces quite a few significant changes.

New prerequisites for installing iTop: PHP 5.3.0 (instead of 5.2.0) with the Zip extension and Graphviz.

If you upgrade from the 2.2.0-beta version, make sure that the value query_cache_enabled is not set to false in the iTop configuration file. If so, please either change the value to true or completely remove the line from the configuration file. Letting the value set to false will cause a severe slow down of the application.

Usability

The following changes may have an impact on the user experience:

  • The color scheme of the application has changed to be aligned with Combodo's new branding.

  • The interactive export has been reworked to provide a better flexibility and additional output formats.

  • The impact analysis diagram is no longer using Flash and now offers additional context information, but looks quite different.

  • Only users with the rights bulk_read are now allowed to perform bulk exports. (By default in iTop everyone has the bulk_read rights).

Export

The menu Admin tools / Export now points to the page export-v2.php. This page can be used either in interactive mode or in scripted mode (both from the web or the command line interface).

The main change since the previous version of iTop is that the new export takes into account the order of the fields to export and supports more formats (the xlsx and PDF format are fully supported with some format specific options).

We encourage you to test your existing scripts against the new export-v2.php page in replacement of export.php and to migrate them if possible.

The old export.php is still available, unmodified, for 100% backward compatibility.

Beware if you customized the profiles: for security reasons, the bulk export is now only allowed to users having the bulk read privilege on the specified class of objects. This applies to theexport.php and export-v2.php pages. However this is transparent in the default iTop model, since all users are granted this privilege.

XML customizations

The XML format has been upgraded to version 1.2.

This new version supports the definition (and alteration) of the relations (e.g. impacts or depends on) in XML.

If you customized such relations (via the GetRelationQueries() method in PHP), we encourage you to migrate to the XML definition which is more flexible and supports the definition of redundancy rules.

Nevertheless the overload of the method GetRelationQueries() is still supported in iTop 2.2.0.

Due to this change, and if you have removed attributes by the mean of customizations, you might need to adjust your XML.

Here is the list of attributes which removal requires additional adjustments:

ClassAttribute
FunctionalCIcontacts_list, applicationsolution_list, softwares_list
ApplicationSolutionbusinessprocess_list
Middlewaremiddlewareinstance_list
DBServerdbschema_list
WebServerwebapp_list
Enclosuredevice_list
StorageSystemlogicalvolume_list
SANSwitchdatacenterdevice_list
TapeLibrarytapes_list
NASnasfilesystem_list
LogicalVolumes ervers_list, virtualdevices_list
VirtualHostvirtualmachine_list
Hypervisorfarm_id

Example: Let's assume that you have removed the attribute FunctionalCI::applicationsolution_list.

You will have to remove the corresponding relation path:

<itop_design xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2">
  <classes>
    <class id="FunctionalCI">
      <relations>
        <relation id="impacts">
          <neighbours>
            <neighbour id="applicationsolution" _delta="delete"/>
...

Failing to do so will result in the following error, when requesting the “details” of any type of object:

Wrong definition for the relation impacts/FunctionalCI/applicationsolution: Unknown attribute applicationsolution_list from class FunctionalCI

Module Developers

You must upgrade your toolkit to iTopDataModelToolkit-2.2.zip. That version remains backward compatible with older versions of iTop.

For PHP developers, be aware of the following change: the new base class for all “searches” is now the abstract class DBSearch. This new class has two child classes: the former DBObjectSearch and the new DBUnionSearch.

Check your custom functions/methods: whenever the argument is typed as DBObjectSearch, it is recommended to change it to DBSearch. This ensures that your code will still work if the passed query is of type DBUnionSearch (which corresponds to the new capability introduced in 2.2.0: UNION queries).

Pages authentication and custom portals

In order to support custom portals, the API LoginWebPage::DoLogin slightly changed. Therefore the authentication of all pages which are supposed to acceptPortal Users must be changed from:

LoginWebPage::DoLogin(false /* bMustBeAdmin */, true /* IsAllowedToPortalUsers */);

to:

LoginWebPage::DoLoginEx(null /* any portal */, false);

If the page is not designed to be accessed by Portal Users, then the appropriate authentication code is:

LoginWebPage::DoLogin(false /* bMustBeAdmin */, false/* IsAllowedToPortalUsers */);

REST/JSON API

Check the REST/JSON services documentation#changes_history for the latest version of the API.

For security reasons, the use of REST/JSON webservices by user accounts with the profile Portal User is now disabled. If you use one of the webservices only to check the credentials of a user, adjust your code to use the new core/check_credentials operation.

Beware if you customized the profiles: for security reasons, the operations core/get and core/get_related are now only allowed to users having the bulk read privilege on the specified class of objects. However this is transparent in the default iTop model, since all users are granted this privilege.

标签:
由 superadmin 在 2020/08/27, 15:58 创建
    

需要帮助?

如果您需要有关XWiki的帮助,可以联系:

深圳市艾拓先锋企业管理咨询有限公司