Remedy ITSM平台安装手册_Sample

合集下载

Sterisample 安装与操作手册说明书

STERISAMPLE® Installation and Operation Manual2 Table of Contents1Introduction 32General description 33Orientation of Sample port 54Sampling 55.Technical data 66.Checklist for Sample Port 7Read this user manual carefully before unpacking Sterisample®.Legal Note.Steridose reserves the right to alter instructions and/or specifications without prior notice.Steridose does not give any warranty for products that have not been approved by Steridoseincluding but not limited to similar products and/or copies of original Steridose products. AllSteridose products are validated to work in cooperation with Steridose products and Steridosevalidated products only.Sterisample®– Installation and Operation Manual 3 1IntroductionThe hypodermic sample port makes it possible to take samples of the product in an asepticmanner without disrupting the production. It is suitable for a wide range ofprocesses/production lines within the pharmaceutical sector. Prior to sampling, the port issterilized with alcohol and then sampling takes place by simply penetrating the special siliconemembrane with a needle.2General descriptionThe design of the sample port permits connection to any appropriate TC-connection. There isno need for a specially designed connection on the vessel, any standard TC-connection can beused.The sample port unit consists of a blind flange with finger-pull, two TC-clamps, two TC gaskets,one sample port and one sample port membrane, see the table below and the figure.4 There are two types of sample ports depending on where and how it will be installed.Short Port for pipe with TC-end.Long Port for vessel using flush mounted Steriflange.Note that the correct Steriflange must be used with the Long sample port in order to ensureproper sealing of the membrane.Steriflange according to Tube standard ASTM A270 (mm)Sterisample®– Installation and Operation Manual 5 3Orientation of Sample portThe sample port unit should be mounted so that the membrane is vertically or horizontallyorientated. If the sample port unit is mounted with the membrane horizontal the sample portunit should be uppermost.4SamplingThe sample port is designed for sampling by using a hypodermic needle. The needle can beadapted to a syringe for sampling of small volumes, or connected to a sampling vessel by sshort flexible hose. The sampling equipment should in both cases be sterile.1.Spray the sample port unit with a 70% alcohol solution (or other equivalentdisinfecting solution).2.Dismount the TC-clamp, TC-gasket and the blind flange. Place the removed parts in adisinfecting solution (use gloves).3.Spray disinfecting solution on the sample port and the membrane. Wait forapproximately 30 seconds.4.Study the checklist for the correct part number to identify which sampling well shouldbe used (paragraph 6).5.Insert the needle for sampling. In order to achieve reseal of the puncture spot, it ismost important that the recommended insertion angle through the membrane isaccomplished. See figure below. Recommended needle diameter is maximum 1mm.6.Collect the required sample.7.Pull out the sampling needle.8.Spray disinfecting solution on the sampling port and the membrane.9.Mount the TC-gasket, the blind flange and the TC-clamp.10.Mark on the checklist which sampling well has been used.Note: Penetration of the sampling port membrane should only be done once through the samesampling well. A penetrated membrane withstands a vessel pressure of 7 barg 80°C.6 5.Technical dataIf the sample port is connected in a WFI-system, please follow the instruction for exchange ofmembrane in WFI-system.This should be done when the checklist for the sample port is completed.5.1Replacement procedure1.Shut down the system to which the sample port is connected. Ventilate the system.Drain the system to avoid spillage.2.Dismount inner TC-clamp and place the outer parts of the sample port unit in adisinfecting solution.3.Replace the used membrane. The new membrane should be soaked in disinfectingsolution before exchanging.4.Mount the outer part of sample port unit along with the TC-gasket and TC-clamp.5.Change of membrane means that the system has been opened. It is thereforerecommended that the systems is disinfected or sterilized as soon as possible.Note: Only an original Steridose membrane can guarantee a leak-free sample port.Sterisample®– Installation and Operation Manual 7 6.Checklist for Sample PortOnly one sample should be taken from each sampling wellChange the membrane when all sampling wells have been used.8 Steridose is a global brand manufactured at the IDEX Material Processing Technologies plant in Canada. We are highly specialized in the design, development and manufacturing of magnetic coupled mixers and radial diaphragm valves.Steridose is part of IDEX Corporation, with regional offices in key locations around the world. Steridose is represented in important certifying and standards organizations, most notably and relevant to the pharmaceutical industry, ASME BioProcessing Equipment standards committee (BPE). We help develop the standards and Good Manufacturing Practices that minimize risk for process interference. Steridose partners with the best distributors and representatives in the industry all over the world. Together we become the perfect mix; a premium product with global references combined with local presence for product and application support.。

Remedy ITSM产品及License配置说明

Remedy ITSM产品及License配置说明2012年8月目录1REMEDY ITSM产品架构和配置模式 (2)2REMEDY ITSM产品的用户体系架构和LICENSE实现机制 (4)3REMEDY ITSM产品LICENSE测试报告分析 .......................... ERROR! BOOKMARK NOT DEFINED. 4REMEDY ITSM产品配置原则建议 (7)页码：11 Remedy ITSM产品架构和配置模式基于BMC Remedy的IT服务管理解决方案主要由三大部分组成：1) 基于ITIL最佳实践流程的Remedy ITSM应用模块；2) 提供CMDB及一些系列管理工具的BMC Atrium Core；3) 强大的工作引擎平台Remedy AR System如上图所示，BMC Remedy ITSM主要应用模块为服务台，变更管理，资产管理，服务请求管理，知识管理，服务水平管理应用模块，这些应用模块都采用了ITIL V3最佳实践，并基于BMC Remedy强大的工作流引擎平台ARS和统一的CMDB构建而成：BMC Remedy IT Service Management Suite是BMC Remedy的基础软件包BMC Service Desk：实现服务台功能，事件管理和问题管理；BMC Change Management：实现变更管理和发布管理；BMC Asset Management：实现全生命周期的资产配置管理和IT财务管理；BMC Service Request Management：实现服务请求管理；BMC Knowledge Management：实现知识管理；BMC Atrium Service Level Management：实现服务水平管理；基于以上产品架构，用户在选择BMC Remedy产品时，将基于以下配置模式：一．产品模块配置：BMC在IT服务管理领域的解决方案为Service Support（基于BMC Remedy ITSM产品构建），Service Support Solution Pack的产品配置模式非常简单，只有一个： Remedy IT Service Management Suite （包括ARS平台，CMDB，ITSM全部的应用模块及共享应用模块），同时还包括开发和备份的产品和License（与采购的生产系统License一致）。

IMS-SYSM 系统平台操作手册说明书

IMS-SYSM系统平台操作手册广东盘古信息科技股份有限公司更新记录序号修改内容编写人编写日期审核人1 新增石灵2020-04-202 增加流程图与数据角色石灵2020-11-103 增加优化功能石灵2021-10-15目录1. 简介 (5)1.1 目的 (5)1.2 背景 (5)2. 软件概述 (6)2.1目标 (6)2.2系统功能 (6)3. 系统要求 (6)3.1 硬件设备要求 (6)3.2 支持软件客户程序软件 (7)4. 运行环境 (7)4.1界面要求 (7)4.2登录页面 (7)4.3系统首页 (8)4.4主页面 (10)4.5 单选框、多选框 (13)4.6 卡片式 (13)4.7 必填项、选填项 (14)4.8 关联字段 (14)4.9 显示列自定义 (15)4.10 产品图标 (16)5. 系统操作流程图 (19)6. 系统权限分配 (20)6.1系统资源分配管理 (20)6.2 设置外部资源 (22)6.3 系统配置 (25)6.4 创建角色并分权限 (27)6.5 创建数据角色并分权限 (28)7. 维护机构信息 (31)7.1 机构管理 (31)7.1.1新增机构 (31)8. 用户信息维护 (36)8.1 用户管理 (37)8.1.1. 创建用户账号并分配权限 (37)8.1.2. 新增用户 (37)8.1.3. 给用户分配权限 (39)8.1.4. 导入用户 (41)8.1.5. 重置密码 (43)9. 通用配置 (44)9.1 资源管理 (44)9.2 参数管理 (49)9.2.1新增参数 (49)9.3 国际化管理 (50)9.3.1 新增国际化 (51)9.3.2 编辑国际化 (52)9.3.3 删除国际化 (53)9.4 页面配置管理 (54)9.4.1 新增页面配置 (55)9.4.2 删除页面配置 (57)9.5 下拉选择页面配置管理 (58)9.5.1 新增下拉选择页面配置 (59)9.5.2 新增下拉选择页面配置 (62)1. 简介1.1 目的本文档是系统管理后台操作指导书，通过该文档用户可以了解该系统后台新增用户、新增角色、权限分配、创建权限等功能。

Linux下的BMC Remdey ARS 安装

注意：安装前首先要安装配置好本地的Oracle客户端和oracle server的监听，然后以安装用户执行export LANG=zh_CN.utf8,然后进入安装介质目录下执行./ar_instll*。

以下是安装记录，请参考！Platform: solarisVersion: 5.10OS Locale: zh_CN.GBK2009年06月27日星期六13时41分50秒CSTInstalling as root******************************************************************** Action Request System(R) Installation*******************************************************************A record of this installation will be kept in /usr/tmp/ar_install.logStage 1: 2009年06月27日星期六13时41分50秒CSTYou will be prompted to enter the product directory.This is the name of the CD mount directory whichcontains the arsystem/solaris/arsystem.tar file.For example:If the tar file is located at<dir>/arsystem/solaris/arsystem.tarthen the product directory would be "<dir>".Enter the product directory [/workflow/install_soft]Looking for the END USER LICENSE and MAINTENANCE AGREEMENT.To continue with this installation, please read the followingEND USER LICENSE and MAINTENANCE AGREEMENT.Press the Return key to scroll through the agreement.At any time while reading this agreement, you canpress "q" to accept, reject or re-read the agreement.【输入q同意】Remedy, All rights reserved.Please select one of the following,1) Yes, I agree to the terms of this agreement.2) No, I disagree to the terms of the agreement.3) I would like to read the agreement again.(1) I accept, (2) I reject or (3) re-read this agreement. [3] 1【输入1同意】The Server package contains the binaries for the AR SystemServer and its associated administration programs. Itrequires an additional 120 MB for the executable programsand 1 MB for the database.The API package contains the AR System programminglibraries and example files. If installed, it consumes10 MB of disk space.Since this installation script will also back up existingAR System directories, make sure that there is enoughdisk space to include both the old and the new installations.The above disk space requirement only outlines how muchadditional disk space is required for the new installation.Do you want to install the Server package? [y] 【输入y继续安装】cq-bomc-db is the first AR System server installed on this machine.Each AR System server requires a unique name that clients can resolve into an IP address.If clients cannot resolve the name into an IP address, they will not communicate correctlywith the AR System server. If you have not defined a unique name for this server, you canopen a separate shell and define a name, and then return to this script and enter the name. You can also stop the installer script, define the name, and start the script again.To install a new AR System server, enter the new server name.To upgrade or overwrite an existing AR System server,please enter the name of the AR System server from the list:------------------------------------------------------------cq-bomc-dbEnter the server name: [cq-bomc-db] 【输入ar server服务名,注意首次安装可能不会提示你输入ar server服务名，首次安装默认的ar server服务名是主机名】You have chosen to upgrade or overwrite cq-bomc-db.Type y to continue.Type n to change your selection.Type q to stop the installation.Enter your selection: [y] 【输入y继续】Do you want to register this AR System server with the Port Mapper ? [n] 【输入n不使用port mapper】Do you want to run this AR System server on a specific TCP Port ? [n] y 【输入y指定tcp端口】The TCP port number is the port address used to connect to this AR System server.The port address must be unique for each server installation and unused by anyother services. Preferably use port addresses greater than 1024.What TCP port will this AR System server use ? 2722【输入指定的tcp端口】未被使用的端口都可以What UDP port will this AR System server use ? 2723【输入指定的udp端口】Do you want to install the API package? [y] 【默认回车】Do you want to install the Central Preferences Forms and Workflow? [y] 【默认回车】Do you want to install the Sample Forms and Workflow? [y] 【默认回车】Do you want to install the ARDBC LDAP package? [n] 【默认回车】Do you want to install the AREA LDAP package? [n] 【默认回车】Do you want to install the BMC Portal package? [n] 【默认回车】Have you installed or will you be installing Full Text Search capabilities? [n] 【默认回车】You can configure SNMP at this time.If you choose NOT to configure SNMP, you will be requiredto manually configure the SNMP configuration file priorto running the SNMP agent.Do you want to configure SNMP? [n] 【默认回车】Web Services requires Java JRE version 1.4.2 or greaterDo you want to configure Web Services? [n] 【默认回车】Which database system will the AR System use?[db2|informix|oracle|sybase] oracle 【输入oracle】Is the ORACLE database on a remote machine? [n] y 【输入y，指定oracle server在远程服务器上】What is the ORACLE home directory? /opt/oracle/product/10g 【输入本地Oracle客户端的位置】What is the remote system ID (TWO_TASK) connect string variable? bomcdb_localhost 【指定oracle server的监听名】What is your AR User Name? [ARAdmin] 【输入数据库用户名】For security reasons, your password will not be displayed.What is your AR User Password for ARAdmin? [*****] 【输入数据库用户密码】Found existing tablespaces (system, undotbs1, sysaux, temp, users, arsystem, artmp) for owner ARAdmin.You can either choose an existing tablespaceor, if you have DBA access, create a new tablespace.1) Choose an existing tablespace2) Create a new tablespace for this user3) Quit this installationSelect the operation do you want to perform [1, 2 or 3]: [1] 1【输入1来选择一下已存在的表空间】What is the AR System Tablespace Name? (system, undotbs1, sysaux, temp, users, arsystem, artmp) [ARSystem] 【默认是arsystem】The ARSystem tablespace exists for owner ARAdmin*** It is a good idea to have a backup of your database before*** attempting an upgrade or overwrite operation. If you do not*** have a recent backup, you may want to pause here or quit the*** installation to make a backup before continuing.At this point, you will be prompted for the action to take.You must choose from the following actions:o - Overwrite the existing ARSystem tablespace for ARAdmin.All existing AR System data will be lost and a new ARSystem tablespaceinstalled.u - Upgrade the existing ARSystem tablespace for ARAdmin.The current AR System tablespace will be upgraded to the new release. Allcurrent data will be preserved and the tablespace restructured.s - Share the existing ARSystem tablespace for ARAdmin.The current AR System tablespace will be retained. All current datawill be preserved and available for sharing with this server.q - Quit the installation at this point.Action? [u] s 【输入s来共享安装】Your existing AR System database will be shared*** Passwords are now required for the proper functioning of*** some applications. To change the passwords after the*** installation you must use BMC Remedy Administrator.*** Please set your initial passwords:For security reasons, your password will not be displayed.Enter the local DSO User password: 【输入DSO的密码，一般输入arsystem】For security reasons, your password will not be displayed.Enter the Application Service password: 【输入Application Service的密码，一般输入arsystem】For security reasons, your password will not be displayed.Enter the Mid-Tier Administration password: 【输入midtier的管理密码，一般输入arsystem】Selecting UNICODE to create or overwrite an existingOracle tablespace REQUIRES that the database alreadybe configured to support the AL32UTF-8 UNICODE character set.If you are upgrading an existing database to use UNICODE, the databasemust already be configured to support the UNICODE character set.Do you want to use the UNICODE character set? [y] 【输入y，使用unicode】Directory to install AR System? [/workflow/ar/cq-bomc-db] 【输入准备安装ar server的位置】AR System will be installed in the /workflow/ar/cq-bomc-db directory.Is this OK? [y] 【输入y确认安装位置】Do you want to put the AR System server in a system startup file? [n] 【输入n，不把ar server 放到自启动脚本中，下面就开始安装了！】Creating Configuration Directory /workflow/ar/cq-bomc-db/confCreating Database Directory /workflow/ar/cq-bomc-db/dbCreating AR System server configuration file /workflow/ar/cq-bomc-db/conf/ar cq-bomc-db AR;NTStage 2: 2009年06月27日星期六13时44分07秒CSTYou may need to wait a few minutes if you load media from a remotedevice or load on a remote file system.[Silent]=cq-bomc-dbremedy.arsystem.server.portmapper=Tremedy.arsystem.server.tcpport=2722remedy.arsystem.server.pluginport=remedy.arsystem.server.autostart=Fremedy.arsystem.server.debugmode=ponent.samples=Trueponent.api=Trueponent.central.preferences=Trueponent.area.ldap=Falseponent.ardbc.ldap=Falseremedy.arsystem.server.plugin.wasp=Falseponent.webservices=Falseremedy.java.install.dir=remedy.arsystem.server.plugin.wasp=Falseremedy.arsystem.server.wasp.url=ponent.snmp=Falseponent.fts=Falsenguage.view.fr=Falsenguage.view.de=Falsenguage.view.it=Falsenguage.view.ja=Falsenguage.view.ko=Falsenguage.view.es=Falsenguage.view.ru=Falsenguage.view.zh_CN=Falseremedy.arsystem.install.dir=/workflow/ar/cq-bomc-dbremedy.arsystem.db.unicode=Falseremedy.arsystem.db.type=Oracleremedy.arsystem.install.mode=sremedy.arsystem.server.dso.local.password=remedy.arsystem.server.apps.service.password=remedy.arsystem.server.midtier.password=remedy.arsystem.db.remote=Trueremedy.arsystem.db.oracle.twotask=bomcdb_localhost remedy.arsystem.db.id=remedy.arsystem.db.home=/opt/oracle/product/10g er=ARAdminer=system=ARSystem remedy.arsystem.db.oracle.datatablespace.filename= remedy.arsystem.db.oracle.datatablespace.size==remedy.arsystem.db.oracle.temptablespace.filename= remedy.arsystem.db.oracle.temptablespace.size=---------- List of Extracted Files -----------x api, 0 bytes, 0磁带块x api/src, 0 bytes, 0磁带块x api/src/daysOpen, 0 bytes, 0磁带块x api/src/daysOpen/README, 5119 bytes, 10磁带块x api/src/daysOpen/daysOpen.c, 36809 bytes, 72磁带块x api/src/daysOpen/holiday.txt, 79 bytes, 1磁带块x api/src/daysOpen/Makefile, 637 bytes, 2磁带块x api/src/driver, 0 bytes, 0磁带块x api/src/driver/api.c, 334082 bytes, 653磁带块x api/src/driver/api.h, 4807 bytes, 10磁带块x api/src/driver/get.c, 165383 bytes, 324磁带块x api/src/driver/get.h, 5220 bytes, 11磁带块x api/src/driver/globals.h, 5153 bytes, 11磁带块x api/src/driver/main.c, 57150 bytes, 112磁带块x api/src/driver/main.h, 15756 bytes, 31磁带块x api/src/driver/print.c, 257022 bytes, 502磁带块x api/src/driver/print.h, 7300 bytes, 15磁带块x api/src/driver/util.c, 44418 bytes, 87磁带块x api/src/driver/util.h, 1987 bytes, 4磁带块x api/src/driver/Makefile, 493 bytes, 1磁带块x api/src/driver/driver, 2769036 bytes, 5409磁带块x api/src/JavaDriver, 0 bytes, 0磁带块x api/src/JavaDriver/Makefile, 161 bytes, 1磁带块x api/src/JavaDriver/build.xml, 319 bytes, 1磁带块x api/src/JavaDriver/Commands.java, 20272 bytes, 40磁带块x api/src/JavaDriver/InputFile.java, 1266 bytes, 3磁带块x api/src/JavaDriver/InputReader.java, 134594 bytes, 263磁带块x api/src/JavaDriver/JavaDriver.java, 310809 bytes, 608磁带块x api/src/JavaDriver/LocaleCharSet.java, 1689 bytes, 4磁带块x api/src/JavaDriver/OutputWriter.java, 207771 bytes, 406磁带块x api/src/JavaDriver/RowIterator.java, 499 bytes, 1磁带块x api/src/JavaDriver/SyncObject.java, 282 bytes, 1磁带块x api/src/JavaDriver/ThreadControlBlock.java, 11416 bytes, 23磁带块x api/src/JavaDriver/ThreadStartInfo.java, 3448 bytes, 7磁带块x api/src/area, 0 bytes, 0磁带块x api/src/area/example, 0 bytes, 0磁带块x api/src/area/example/areasamp.c, 14071 bytes, 28磁带块x api/src/area/example/Makefile, 382 bytes, 1磁带块x api/src/area/skeleton, 0 bytes, 0磁带块x api/src/area/skeleton/areaskl.c, 14651 bytes, 29磁带块x api/src/area/skeleton/Makefile, 379 bytes, 1磁带块x api/src/area/ldap, 0 bytes, 0磁带块x api/src/area/ldap/arealdap.c, 19054 bytes, 38磁带块x api/src/area/ldap/Makefile, 481 bytes, 1磁带块x api/src/ardbc, 0 bytes, 0磁带块x api/src/ardbc/skeleton, 0 bytes, 0磁带块x api/src/ardbc/skeleton/ardbcskl.c, 24503 bytes, 48磁带块x api/src/ardbc/skeleton/Makefile, 454 bytes, 1磁带块x api/src/arfilterapi, 0 bytes, 0磁带块x api/src/arfilterapi/example, 0 bytes, 0磁带块x api/src/arfilterapi/example/arfilterapisamp.c, 14321 bytes, 28磁带块x api/src/arfilterapi/example/Makefile, 395 bytes, 1磁带块x api/src/arfilterapi/skeleton, 0 bytes, 0磁带块x api/src/arfilterapi/skeleton/arfilterapiskl.c, 11864 bytes, 24磁带块x api/src/arfilterapi/skeleton/Makefile, 393 bytes, 1磁带块x api/include, 0 bytes, 0磁带块x api/include/ar.h, 258382 bytes, 505磁带块x api/include/ardbc.h, 6878 bytes, 14磁带块x api/include/area.h, 2434 bytes, 5磁带块x api/include/arerrno.h, 66538 bytes, 130磁带块x api/include/arextern.h, 43807 bytes, 86磁带块x api/include/arfilterapi.h, 453 bytes, 1磁带块x api/include/arfree.h, 16075 bytes, 32磁带块x api/include/arplugin.h, 7969 bytes, 16磁带块x api/include/arstruct.h, 112097 bytes, 219磁带块x api/include/artypes.h, 2488 bytes, 5磁带块x api/lib, 0 bytes, 0磁带块x api/lib/libar.a, 4559560 bytes, 8906磁带块x api/lib/libar.so, 2956868 bytes, 5776磁带块x api/lib/libarjni70.so, 4941096 bytes, 9651磁带块x api/lib/libarutiljni70.so, 602436 bytes, 1177磁带块x api/lib/arapi70.jar, 306819 bytes, 600磁带块x api/lib/libarxmlutil.so, 5921140 bytes, 11565磁带块x api/doc, 0 bytes, 0磁带块x api/doc/ardoc70.jar, 1258636 bytes, 2459磁带块x bin, 0 bytes, 0磁带块x bin/runmacro, 5667648 bytes, 11070磁带块x bin/arimportcmd, 3045092 bytes, 5948磁带块x bin/libarcrypto.so, 384940 bytes, 752磁带块x bin/armonitor, 269252 bytes, 526磁带块x bin/arforkd, 154424 bytes, 302磁带块x bin/arservdsd, 2754428 bytes, 5380磁带块x bin/arplugin, 1229996 bytes, 2403磁带块x bin/arinst.nfs, 27583 bytes, 54磁带块x bin/ARSystem, 1774 bytes, 4磁带块x bin/ARSystem.ja, 796 bytes, 2磁带块x bin/arsystem, 15792 bytes, 31磁带块x bin/ardist, 2485260 bytes, 4855磁带块x bin/arsvcdsp, 2624476 bytes, 5126磁带块x bin/arftreader.txt, 56 bytes, 1磁带块x bin/install.sh, 109 bytes, 1磁带块x bin/patch_install.sh, 807 bytes, 2磁带块x bin/axis-ant.jar, 33501 bytes, 66磁带块x bin/axis.jar, 1599495 bytes, 3125磁带块x bin/commons-discovery-0.2.jar, 71442 bytes, 140磁带块x bin/commons-logging-1.0.4.jar, 38015 bytes, 75磁带块x bin/jaxrpc.jar, 32071 bytes, 63磁带块x bin/log4j-1.2.8.jar, 352668 bytes, 689磁带块x bin/saaj.jar, 19427 bytes, 38磁带块x bin/wsdl4j-1.5.1.jar, 126771 bytes, 248磁带块x bin/wsdl4j.jar, 113853 bytes, 223磁带块x bin/xercesImpl.jar, 1730053 bytes, 3380磁带块x bin/xercesSamples.jar, 264454 bytes, 517磁带块x bin/xmlParserAPIs.jar, 131895 bytes, 258磁带块x bin/junit.jar, 117522 bytes, 230磁带块x bin/apache_axis_license.txt, 11359 bytes, 23磁带块x bin/apache_crimson_license.txt, 2469 bytes, 5磁带块x bin/apache_log4j_license.txt, 2431 bytes, 5磁带块x bin/websvc70.jar, 70672 bytes, 139磁带块x bin/reportplugin.so, 2788084 bytes, 5446磁带块x bin/libarflib.so, 38308 bytes, 75磁带块x bin/libwebservice.so, 580132 bytes, 1134磁带块x bin/arsnmpd, 3790480 bytes, 7404磁带块x bin/arsnmptrap, 882852 bytes, 1725磁带块x bin/libwasp.so, 4283992 bytes, 8368磁带块x bin/libwasp.so.5, 4283992 bytes, 8368磁带块x bin/libwasp.so.5.0.0, 4283992 bytes, 8368磁带块x bin/libwasp_, 1928 bytes, 4磁带块x bin/libwasp_openssl.so, 232948 bytes, 455磁带块x bin/libwasp_openssl.so.5, 232948 bytes, 455磁带块x bin/libwasp_openssl.so.5.0.0, 232948 bytes, 455磁带块x bin/libwasp_, 1421 bytes, 3磁带块x bin/libwasp_stl.so, 22124 bytes, 44磁带块x bin/libwasp_stl.so.5, 22124 bytes, 44磁带块x bin/libwasp_stl.so.5.0.0, 22124 bytes, 44磁带块x bin/libgcc_s.so.1, 37780 bytes, 74磁带块x bin/libstdc++.so.5.0.5, 728944 bytes, 1424磁带块链接到libstdc++.so.5.0.5 的x bin/libstdc++.so 符号链接到libstdc++.so.5.0.5 的x bin/libstdc++.so.5 符号链接到libstdc++.so.5.0.5 的x bin/libstdc++.so.4 符号链接到libgcc_s.so.1 的x bin/libgcc_s.so 符号x bin/arcache, 2512548 bytes, 4908磁带块x bin/arreload, 2519452 bytes, 4921磁带块x bin/arsignal, 2475556 bytes, 4836磁带块x bin/arlogdec, 2521036 bytes, 4924磁带块x bin/arlogdec.txt, 474 bytes, 1磁带块x bin/arufix63, 2527828 bytes, 4938磁带块x bin/arufix63.txt, 4768 bytes, 10磁带块x bin/arconv, 98776 bytes, 193磁带块x bin/arconv.txt, 2205 bytes, 5磁带块x bin/arlabel, 2573724 bytes, 5027磁带块x bin/arlabel.txt, 19394 bytes, 38磁带块x bin/artext, 2560580 bytes, 5002磁带块x bin/artext.txt, 8514 bytes, 17磁带块x bin/arufix63c.txt, 1915 bytes, 4磁带块x bin/aeufix63c.txt, 1603 bytes, 4磁带块x bin/apufix63c.txt, 1969 bytes, 4磁带块x help, 0 bytes, 0磁带块x help/remerror.def, 19951 bytes, 39磁带块x help/errars.arx, 823360 bytes, 1609磁带块x locale, 0 bytes, 0磁带块x locale/C, 0 bytes, 0磁带块x locale/C/runmacro.cat, 66360 bytes, 130磁带块x locale/C/arsystem.cat, 3266991 bytes, 6381磁带块x locale/de, 0 bytes, 0磁带块x locale/de/runmacro.cat, 66360 bytes, 130磁带块x locale/de/arsystem.cat, 4437275 bytes, 8667磁带块x locale/es, 0 bytes, 0磁带块x locale/es/runmacro.cat, 66360 bytes, 130磁带块x locale/es/arsystem.cat, 4450575 bytes, 8693磁带块x locale/fr, 0 bytes, 0磁带块x locale/fr/runmacro.cat, 66360 bytes, 130磁带块x locale/fr/arsystem.cat, 4449080 bytes, 8690磁带块x locale/it, 0 bytes, 0磁带块x locale/it/runmacro.cat, 66360 bytes, 130磁带块x locale/it/arsystem.cat, 4436377 bytes, 8665磁带块x locale/ja, 0 bytes, 0磁带块x locale/ja/runmacro.cat, 66360 bytes, 130磁带块x locale/ja/arsystem.cat, 3553430 bytes, 6941磁带块x locale/zh, 0 bytes, 0磁带块x locale/zh/runmacro.cat, 66360 bytes, 130磁带块x locale/zh/arsystem.cat, 3492213 bytes, 6821磁带块x locale/ru, 0 bytes, 0磁带块x locale/ru/runmacro.cat, 66360 bytes, 130磁带块x locale/ru/arsystem.cat, 3577491 bytes, 6988磁带块x locale/ko, 0 bytes, 0磁带块x locale/ko/runmacro.cat, 66360 bytes, 130磁带块x locale/ko/arsystem.cat, 3535604 bytes, 6906磁带块x locale/en.UTF-8, 0 bytes, 0磁带块x locale/en.UTF-8/arsystem.cat, 3266717 bytes, 6381磁带块x locale/de.UTF-8, 0 bytes, 0磁带块x locale/de.UTF-8/arsystem.cat, 4440549 bytes, 8673磁带块x locale/ja.UTF-8, 0 bytes, 0磁带块x locale/ja.UTF-8/arsystem.cat, 3621486 bytes, 7074磁带块x locale/fr.UTF-8, 0 bytes, 0磁带块x locale/fr.UTF-8/arsystem.cat, 4455128 bytes, 8702磁带块x locale/it.UTF-8, 0 bytes, 0磁带块x locale/it.UTF-8/arsystem.cat, 4438134 bytes, 8669磁带块x locale/ru.UTF-8, 0 bytes, 0磁带块x locale/ru.UTF-8/arsystem.cat, 3708198 bytes, 7243磁带块x locale/es.UTF-8, 0 bytes, 0磁带块x locale/es.UTF-8/arsystem.cat, 4454520 bytes, 8701磁带块x locale/zh.UTF-8, 0 bytes, 0磁带块x locale/zh.UTF-8/arsystem.cat, 3531402 bytes, 6898磁带块x locale/ko.UTF-8, 0 bytes, 0磁带块x locale/ko.UTF-8/arsystem.cat, 3588357 bytes, 7009磁带块x ora_db, 0 bytes, 0磁带块x ora_db/arservora, 12663232 bytes, 24733磁带块x ora_db/arupora, 1494312 bytes, 2919磁带块x ora_db/arftread.so, 523476 bytes, 1023磁带块x ora_db/ARS_del.ora, 213 bytes, 1磁带块x ora_db/ARSini71.ora, 74 bytes, 1磁带块x ora_db/ARSini72.ora, 105 bytes, 1磁带块x ora_db/ARSinit7.ora, 635 bytes, 2磁带块x ora_db/ARSystem.ora, 38839 bytes, 76磁带块x ora_db/dynamic.ora, 49 bytes, 1磁带块x ora_db/rewrite.ora, 32 bytes, 1磁带块x ora_db/test4.ora, 5 bytes, 1磁带块x ora_db/upgrade.ora, 32 bytes, 1磁带块x ora_db/version.ora, 30 bytes, 1磁带块x plugins/ardbcconf, 0 bytes, 0磁带块x plugins/ardbcconf/solaris, 0 bytes, 0磁带块x plugins/ardbcconf/solaris/ardbcconf.so, 605444 bytes, 1183磁带块x plugins/ardbcconf/ardbcconf.def, 33310 bytes, 66磁带块x plugins/areahub, 0 bytes, 0磁带块x plugins/areahub/solaris, 0 bytes, 0磁带块x plugins/areahub/solaris/areahub.so, 229948 bytes, 450磁带块x plugins/areahub/README.TXT, 5242 bytes, 11磁带块x plugins/ssoldap, 0 bytes, 0磁带块x plugins/ssoldap/solaris, 0 bytes, 0磁带块x plugins/ssoldap/solaris/ssoldap.so, 665504 bytes, 1300磁带块x plugins/ssoldap/solaris/libfreebl_hybrid_3.so, 232448 bytes, 454磁带块x plugins/ssoldap/solaris/libfreebl_pure32_3.so, 217272 bytes, 425磁带块x plugins/ssoldap/solaris/libiutil50.a, 1584 bytes, 4磁带块x plugins/ssoldap/solaris/liblber50.a, 32704 bytes, 64磁带块x plugins/ssoldap/solaris/libldap50.a, 390080 bytes, 762磁带块x plugins/ssoldap/solaris/libldap50.so, 347240 bytes, 679磁带块x plugins/ssoldap/solaris/libldif50.a, 8448 bytes, 17磁带块x plugins/ssoldap/solaris/libnspr4.a, 435728 bytes, 852磁带块x plugins/ssoldap/solaris/libnspr4.so, 362072 bytes, 708磁带块x plugins/ssoldap/solaris/libnss3.so, 743840 bytes, 1453磁带块x plugins/ssoldap/solaris/libplc4.a, 40684 bytes, 80磁带块x plugins/ssoldap/solaris/libplc4.so, 34200 bytes, 67磁带块x plugins/ssoldap/solaris/libplds4.a, 13436 bytes, 27磁带块x plugins/ssoldap/solaris/libplds4.so, 14032 bytes, 28磁带块x plugins/ssoldap/solaris/libprldap50.so, 28868 bytes, 57磁带块x plugins/ssoldap/solaris/libssl3.so, 191624 bytes, 375磁带块x plugins/ssoldap/solaris/libssldap50.so, 43020 bytes, 85磁带块x plugins/ssoldap/ssoldap.def, 165727 bytes, 324磁带块x plugins/ssoldap/README.TXT, 5889 bytes, 12磁带块x plugins/serveradmin, 0 bytes, 0磁带块x plugins/serveradmin/solaris, 0 bytes, 0磁带块x plugins/serveradmin/solaris/ServerAdmin.so, 3283532 bytes, 6414磁带块x plugins/FlashboardObject, 0 bytes, 0磁带块x plugins/FlashboardObject/solaris, 0 bytes, 0磁带块x plugins/FlashboardObject/solaris/FlashboardObject.so, 2871020 bytes, 5608磁带块x samples, 0 bytes, 0磁带块x samples/de, 0 bytes, 0磁带块x samples/de/AlertList_view.def, 57928 bytes, 114磁带块x samples/de/Business_view.def, 274222 bytes, 536磁带块x samples/de/CurrencyL10NLabels.arx, 3409 bytes, 7磁带块x samples/de/Group.arx, 4018 bytes, 8磁带块x samples/de/Group.imp, 297 bytes, 1磁带块x samples/de/Group_view.def, 66595 bytes, 131磁带块x samples/de/HomePage_view.def, 64129 bytes, 126磁带块x samples/de/MessageCatalog.arx, 154666 bytes, 303磁带块x samples/de/MessageCatalog.xml, 321965 bytes, 629磁带块x samples/de/ReportType.arx, 2400 bytes, 5磁带块x samples/de/UpgrUserPref.imp, 5153 bytes, 11磁带块x samples/de/User.arx, 560 bytes, 2磁带块x samples/de/User.imp, 122 bytes, 1磁带块x samples/de/UserPref_view.def, 384187 bytes, 751磁带块x samples/de/User_view.def, 62890 bytes, 123磁带块x samples/de/adf_ServerApps_de.xml, 778 bytes, 2磁带块x samples/de/cdf_groupuser_de.xml, 826 bytes, 2磁带块x samples/de/cdf_prefcomp_de.xml, 768 bytes, 2磁带块x samples/de/cdf_servercomp_de.xml, 982 bytes, 2磁带块x samples/de/reportforms_view.def, 333060 bytes, 651磁带块x samples/de/reportvendor_view.def, 177662 bytes, 347磁带块x samples/en, 0 bytes, 0磁带块x samples/en/AdminPref.def, 183586 bytes, 359磁带块x samples/en/AlertList.def, 65707 bytes, 129磁带块x samples/en/BusTimeHolidayWorkday.def, 157393 bytes, 308磁带块x samples/en/CurrencyCodes.arx, 3192 bytes, 7磁带块x samples/en/DataVisForms.def, 89886 bytes, 176磁带块x samples/en/FlashForms.def, 133289 bytes, 261磁带块x samples/en/FlashForms.xml, 292 bytes, 1磁带块x samples/en/FlashboardObject.def, 426855 bytes, 834磁带块x samples/en/Group.arx, 3732 bytes, 8磁带块x samples/en/Group.def, 91206 bytes, 179磁带块x samples/en/Group.imp, 123 bytes, 1磁带块x samples/en/HomePage.def, 119106 bytes, 233磁带块x samples/en/ReportType.arx, 2404 bytes, 5磁带块x samples/en/Sample_app.def, 1091426 bytes, 2132磁带块x samples/en/Sample_app.imp, 138 bytes, 1磁带块x samples/en/SearchesPref.def, 38944 bytes, 77磁带块x samples/en/ServerStat.def, 196670 bytes, 385磁带块x samples/en/UpgrBusinessTimes.imp, 245 bytes, 1磁带块x samples/en/UpgrSvrAdmin.imp, 170 bytes, 1磁带块x samples/en/UpgrUserPref.imp, 4721 bytes, 10磁带块x samples/en/User.arx, 556 bytes, 2磁带块x samples/en/User.def, 77135 bytes, 151磁带块x samples/en/User.imp, 122 bytes, 1磁带块x samples/en/UserPref.def, 500565 bytes, 978磁带块x samples/en/adf_BusinessTime.xml, 453 bytes, 1磁带块x samples/en/adf_SampleApps_en.xml, 451 bytes, 1磁带块x samples/en/adf_ServerApps.xml, 608 bytes, 2磁带块x samples/en/adf_ServerApps_en.xml, 778 bytes, 2磁带块x samples/en/cdf_BusinessTime.xml, 518 bytes, 2磁带块x samples/en/cdf_groupuser_en.xml, 816 bytes, 2磁带块x samples/en/cdf_prefcomp_en.xml, 814 bytes, 2磁带块x samples/en/cdf_sampcomp_en.xml, 714 bytes, 2磁带块x samples/en/cdf_servercomp_en.xml, 1028 bytes, 3磁带块x samples/en/reportforms.def, 414107 bytes, 809磁带块x samples/en/reportforms.xml, 1806 bytes, 4磁带块x samples/en/reportvendor.def, 484926 bytes, 948磁带块x samples/en/reportvendor.xml, 11349 bytes, 23磁带块x samples/en/sample_app_attach, 0 bytes, 0磁带块x samples/en/sample_app_attach/class1prep_0.htm, 147 bytes, 1磁带块x samples/en/sample_app_attach/class1syllabus_1.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class2prep_16.htm, 152 bytes, 1磁带块x samples/en/sample_app_attach/class2prep_2.htm, 152 bytes, 1磁带块x samples/en/sample_app_attach/class2syllabus_17.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class2syllabus_3.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class3prep_4.htm, 144 bytes, 1磁带块x samples/en/sample_app_attach/class3syllabus_5.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class4prep_18.htm, 146 bytes, 1磁带块x samples/en/sample_app_attach/class4prep_6.htm, 146 bytes, 1磁带块x samples/en/sample_app_attach/class4syllabus_19.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class4syllabus_7.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class5prep_8.htm, 152 bytes, 1磁带块x samples/en/sample_app_attach/class5syllabus_9.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class6prep_10.htm, 157 bytes, 1磁带块x samples/en/sample_app_attach/class6syllabus_11.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class7prep_12.htm, 139 bytes, 1磁带块x samples/en/sample_app_attach/class7syllabus_13.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class8prep_14.htm, 146 bytes, 1磁带块x samples/en/sample_app_attach/class8prep_20.htm, 146 bytes, 1磁带块x samples/en/sample_app_attach/class8syllabus_15.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/class8syllabus_21.doc, 19456 bytes, 38磁带块x samples/en/sample_app_attach/Sample Class List_1.arr, 315 bytes, 1磁带块x samples/en/sample_app_attach/Sample Roster_0.arr, 288 bytes, 1磁带块x samples/en/sample_reports.arx, 709 bytes, 2磁带块x samples/en/serveradmin.def, 834417 bytes, 1630磁带块x samples/es, 0 bytes, 0磁带块x samples/es/AlertList_view.def, 57910 bytes, 114磁带块x samples/es/Business_view.def, 275064 bytes, 538磁带块x samples/es/CurrencyL10NLabels.arx, 3142 bytes, 7磁带块x samples/es/Group.arx, 4033 bytes, 8磁带块x samples/es/Group.imp, 297 bytes, 1磁带块x samples/es/Group_view.def, 66638 bytes, 131磁带块x samples/es/HomePage_view.def, 64297 bytes, 126磁带块x samples/es/MessageCatalog.arx, 151081 bytes, 296磁带块x samples/es/MessageCatalog.xml, 318795 bytes, 623磁带块x samples/es/ReportType.arx, 2410 bytes, 5磁带块x samples/es/UpgrUserPref.imp, 5153 bytes, 11磁带块x samples/es/User.arx, 568 bytes, 2磁带块x samples/es/User.imp, 122 bytes, 1磁带块x samples/es/UserPref_view.def, 386693 bytes, 756磁带块x samples/es/User_view.def, 62986 bytes, 124磁带块x samples/es/adf_ServerApps_es.xml, 778 bytes, 2磁带块x samples/es/cdf_groupuser_es.xml, 826 bytes, 2磁带块x samples/es/cdf_prefcomp_es.xml, 768 bytes, 2磁带块x samples/es/cdf_servercomp_es.xml, 982 bytes, 2磁带块x samples/es/reportforms_view.def, 333211 bytes, 651磁带块x samples/es/reportvendor_view.def, 177621 bytes, 347磁带块x samples/fr, 0 bytes, 0磁带块x samples/fr/AlertList_view.def, 57921 bytes, 114磁带块x samples/fr/Business_view.def, 275551 bytes, 539磁带块x samples/fr/CurrencyL10NLabels.arx, 3231 bytes, 7磁带块x samples/fr/Group.arx, 4016 bytes, 8磁带块x samples/fr/Group.imp, 297 bytes, 1磁带块x samples/fr/Group_view.def, 66648 bytes, 131磁带块x samples/fr/HomePage_view.def, 64172 bytes, 126磁带块x samples/fr/MessageCatalog.arx, 151054 bytes, 296磁带块x samples/fr/MessageCatalog.xml, 321270 bytes, 628磁带块x samples/fr/ReportType.arx, 2410 bytes, 5磁带块x samples/fr/UpgrUserPref.imp, 5153 bytes, 11磁带块x samples/fr/User.arx, 569 bytes, 2磁带块x samples/fr/User.imp, 122 bytes, 1磁带块x samples/fr/UserPref_view.def, 386562 bytes, 756磁带块x samples/fr/User_view.def, 62992 bytes, 124磁带块x samples/fr/adf_ServerApps_fr.xml, 778 bytes, 2磁带块x samples/fr/cdf_groupuser_fr.xml, 826 bytes, 2磁带块x samples/fr/cdf_prefcomp_fr.xml, 768 bytes, 2磁带块x samples/fr/cdf_servercomp_fr.xml, 982 bytes, 2磁带块x samples/fr/reportforms_view.def, 333078 bytes, 651磁带块。

Remedy ITSM平台安装手册_Sample

Remedy ITSM 项目—系统安装配置手册Remedy ITSM 系统安装配置手册系统安装配置手册安装配置文档信息表文档基本信息项目名称当前项目阶段文档名称文档版本文档创建日期文档存放路径文档审批信息审阅人职务审阅时间审阅意见 Remedy ITSM系统安装配置手册是否为正式交付件当前修订日期文档审批要求是文档修订信息版本修正章节日期作者变更记录Remedy ITSM 项目—系统安装配置手册第一章文档介绍1.1 内容范围本文档用于描述 ITSM 项目的 Remedy 系统安装及其配置说明。

1.2 适用的对象本文档主要针对该系统的管理维护人员。

1.3 保密原则此文档获取的数据信息属于 xxxxxx 公司及 xxxxxxx 公司机密信息，相关人员承诺不将本文档和相关资料泄漏给其他公司或本公司与项目无关的人员。

1.4 参考资料资料名BMC Remedy Action Request System 7.6.04： BMC Installation Guide BMC Atrium Core 7.6.04 ： Installation Guide BMC Remedy IT Service Management 7.6.04： BMC Installation Guide BMC Remedy Knowledge Management 7.6.04： BMC Installation Guide作者版本与日期BMC1.5 术语与缩写解释缩写、术语缩写、 ITIL 解释 Information Technology Infrastructure LibraryRemedy ITSM 项目—系统安装配置手册第二章系统环境准备第三章系统安装3.1 安装环境配置3 .1 .1 J DK &J RE 环境 Remedy 服务器需要安装 64 位和 32 位 JDK 及 JRE（1.5.0_06 以上版本）安装路径如下： JDK 64 位 32 位 C:\Program Files\Java\jdk1.6.0_26 C:\Program Files(X86)\Java\jdk1.6.0_26 JRE C:\Program Files\Java\jre C:\Program Files(X86)\Java\jre3 .1 .2 终端服务配置选项更新（ W in do ws Se rv er ） 1) 2) 点击开始-》运行，输入“gpedit.msc” ，然后回车；选择计算机配置-》管理模板-》Windows 组件-》终端服务-》终端服务器-》临时文件夹（Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Terminal Server -> Temporary folders）；Remedy ITSM 项目—系统安装配置手册3)设置“Do not delete temp folder on exit”为启用；4)设置“Do not use temp folders per session”为启用；Remedy ITSM 项目—系统安装配置手册5) 6)重启服务器。

Mi.Node M 安装工具用户指南说明书

Product Name Document Title1Mi.Node M Install ToolUser Guide880-0199-001Firmware version 1.0.11Document version 2.03/29/2017ContentsOverview (5)Keypad Operation (6)Features (6)User Interface (7)Battery (7)Charger and Battery Status symbols (7)Walk-by meter reading (8)To read one meter (8)To read all meters (8)To read meters currently in “Install” mode (9)To log all meters (9)To read meters using Transparent Mode (9)Viewing readings (10)To view readings in a route (10)To view readings not in a route (10)To view last 9 readings (10)To select a reading (10)Interpreting a meter read (11)Troubleshooting (12)Confirming successful installation (12)To test an installation (12)Alternative installation test (12)Troubleshooting read/installation issues (13)Troubleshooting transmission issues (13)Meter data (14)To clear Meter Data (14)To clear List Data (14)To change RF frequency (14)To change Key Click (14)To change Message Click (14)Handheld-to-computer interface (15)OverviewThe handheld Mi.Node M Install Tool collects readings from a single meter, or collects and stores data from up to 1024 separate water meter accounts when used with EZExport software. When used as an installation tool, it can verify correct wiring connections and successful node activation and communication.The basic installation process:•Physically attach the Mi.Node M unit (mounted on a wall or in a pit)•If necessary, connect the Mi.Node M unit’s wires to the meter register wires•The wiring connections for Mueller Systems products is always Red to Red, White to White and Black to Black.o For other wiring or manufacturers’ devices, consult Mueller Systems support.•Swipe a magnet across the side of the Mi.Node M unit to the right of the logo. This process initiates the node reading of the register. Example:•Confirm the Install Tool displays the meter reading shown on the register. Verify signal level, and absence of event/duration codes.The compact unit is about the size of a standard smart phone. Powered by a lithium battery, the install tool is charged via USB cable and is rated to run for an entire shift of continuous operation. TheMi.Node M Install Tool is capable of operating on two different frequencies. Its antenna is flexible to accommodate meter readers while clipped to a belt or pocket.Note: This document covers only M networks; procedures in this document differ from those for systems using older v3 and v4 Mi.Nodes.Keypad OperationUse the keypad to select commands or enter digits as needed.Important keys include:•ENT: Turns on unit, advances to main menu•CLR: Goes back or cancels current process•1-4: Select menu optionsFeaturesUse the Mi.Node M Installation Tool for small scale meter reading and meter installation. Options:1.Meter Reading – Walk by meters to gather readings, view results. You can collect readings froma list loaded to the Install Tool, as well as all meters in range.2.Installation Tool – Verify meter-to-node connection and successful data transmission3.Datalog Confirm - Confirm the node is transmitting logged meter readings to the Mi.Node MMobile transceiver.4.Unit Setup – change the tool’s frequency, mute soundsUser InterfaceThe Mi.Node M Install Tool’s screen displays menu commands and data. Battery strength is indicated at the top right of the screen.Start screen If the unit is off, press ENT twice to view the main menu. Individual commands are described in the following procedures.The Mi.Node M Install Tool’s screen displays menu commands and data. Battery strength is indicated at the top right of the screen.BatteryTo charge fully, the Install Tool should be plugged into a standard 5-volt USB powered by either an electric outlet or computer for approximately 7-8 hours. If you are plugging the install tool into a computer, make sure the computer is plugged in and configured to provide power to the USB when it times out or is powered down. (By default, most Windows computers supply power to a USB while turned off. Check your computer’s USB Root Hub Power Management Properties, accessed via Device Manager.)Charger and Battery Status symbolsA battery strength indicator is displayed in the upper-right corner of the display screen.Install Tool is plugged into a USB source, battery is charging.Battery is almost depleted, less than 10% charge remaining. Battery is 20-40% charged.Battery is 50-80% charged.Battery is 95-100% full, charge process complete. Note: The install tool turns itself off after ten minutes of non-use, unless it is operating in Transparent mode or Logging mode.Walk-by meter readingThe Mi.Node M Install Tool collects readings from any node in its range. When displaying or uploading reads, it keeps data from meters in the route/list (List Data) separate from the rest of the meter reads (UnList Data).You can read up to 1,024 meters within close range of the tool as you walk.To read one meterThis procedure assumes the Mi.Node M unit has been swiped with a magnet after wires are connected.1. Press ENT or CLR as needed to access the main menu.2. Press 2 > 1 > 2 (Receive One).3. Type the 10-digit ID on the meter’s node. (Note: if the number has fewer than 10 digits, enter leading zeroes. For example enter “0012345678” if the node’s ID has only 8 digits.4. Press ENT .5. Verify the ID on the node label matches the ID shown on the screen and note the Read. See Interpreting a meter read for more information.To read all metersThis procedure is recommended only if a limited number of meters is in range. This mode listens for all meters, in or out of a route.1. Press ENT or CLR as needed to access the main menu.2. Press 2 > 1 > 1 (Receive All). The Install Tool scrolls through all received reads quickly on the screen. Press CLR to stop reading and return to the previous menu. Press any other key to pause/resume reading.To read meters currently in “Install” modeThis procedure scans for up to three Mi.Node M units transmitting an initial beacon sent when the unit is swiped during the install process. You can use it to verify the installation you just performed is transmitting its install beacon. The Mi.Node M unit sends the beacon for two minutes, and the install tool listens for one minute.1.Press ENT or CLR as needed to access the main menu.2.Press 2 > 1 > 3 (Receive Install).3.If the screen displays the register ID you are interested in, press 1, 2, or 3, as it corresponds tothe ID you want.The tool displays the meter data information.To log all metersThis procedure captures datalogs from all Mi.Node M units within receiving range of the install tool. You can pause the process, but cannot view data on the screen. Datalogs are stored in the install tool for later upload to a computer.The install tool runs continuously when in Logging mode; it does not turn off automatically after 10 minutes. Exit Logging mode if you want the unit to turn off automatically.The screen will show the List Count, the Non List Count, the register ID and meter read of the last collected reading.1.Press ENT or CLR as needed to access the main menu.2.Press 1 > 1 > 1 (Start Logging). Wait for the logging to complete, or press CLR to stop loggingand exit to the Meters Logging menu screen.To read meters using Transparent ModeThis procedure requires a laptop or other mobile device. This mode listens for all meters, in or out of a route.1.Press ENT or CLR as needed to access the main menu.2.Press 1 > 2 (Transparent Mode).Note: The Install Tool runs continuously when in Transparent mode; it does not turn off automatically after 10 minutes. Exit Transparent mode if you want the unit to turn off automatically.Viewing readingsTo view readings in a route1.Press ENT or CLR as needed to access the main menu.2.Press 1 > 1 > 2 (View List Data).To view readings not in a route1.Press ENT or CLR as needed to access the main menu.2.Press 1 > 1 > 3 (View UnList Data).To view last 9 readings1.Press ENT or CLR as needed to access the main menu.2.Press 2 > 2 (View Last 9).The top row of the display shows the number of the reads currently shown, for example, reads 7 through 9.To select a readingThe Install Tool displays three readings at a time. Press ENT to scroll through the list three meter readings at a time.To access details of a single read, press the number of the reading (1-9) to access the read. For example, if “4-6” is displayed, you can press 4, 5, or 6 to see more details about that register’s reading.Interpreting a meter readWhen the Mi.Node M Install Tool successfully reads a Mi.Node M unit, it displays consumption, status, and other information described below.The top line is a header for ID and Read, and the received signal strength is at top right. Each line of the display shows: Line 2:• Meter ID: If ID has fewer than 10 digits, leading zeroes are added. • Meter read: 4 to 9 digits. The reading is right-aligned. Line 3:• Status code – “St ”o Good Reado Small Leak – register has detected a leak of approximately 1/8 gpm or less o No Flow o Back Flowo High Leak – register has detected a leak of approximately 1/4 gpm or more o Q-Mark – register’s wheel(s) not fully rolled over to the next digit o No Response o SSR Tamper o SSR Removal• Duration: Length of time the condition persisted, usually a range. “W ” indicates weeks. Line 4:1. Battery strength () — Good, Low, VLow (very low), Fail. If VLow, the Mi.Node M unitshould be replaced immediately. If Low, replace within 6 months. 2. SSR battery status () – (if an SSR is attached to a Mi.Node M unit): Good, Low.3. Last received transmission – “Rx ” time elapsed in seconds since the last transmission receivedfrom node. This number is updated as the Time elapsed since the last transmission received, inseconds.TroubleshootingConfirming successful installationYou can use the Mi.Node M Install Tool to verify that a newly installed meter is correctly connected to the Mi.Node M unit, and is transmitting reads.After the Mi.Node M unit has been physically installed and (if necessary) connected to the register, swipe the unit with a magnet to force an immediate read of all register data.To test an installationUse the standard procedure for reading a single meter.1.Press ENT or CLR as needed to access the main menu.2.Press 2 > 1 > 2 (Receive One).3.Type the 10-digit ID shown on the Mi.Node M unit’s label. Enter leading zeroes if there are lessthan 10 digits.4.Press ENT.The Mi.Node M Install Tool scans for the reading. The display should show “St Good Read” in the status line if the read was successful. See Interpreting a meter read for information on other responses from the Mi.Node M unit.Additionally, make note of:•The ID number shown. If it matches the label on the Mi.Node M unit, this means the unit has not properly received the register’s ID.•Any error codes returned from an electronic register.•Signal strength (dBm) shown in the upper-right corner. The lower the number, the stronger the signal.Alternative installation testWhen swiped, a Mi.Node M unit broadcasts a datalog file. In this procedure, the Mi.Node M Install Tool ‘listens’ for units broadcasting a datalog.1.Press ENT or CLR as needed to access the main menu.2.Press 3 (Datalog Confirm).3.Swipe the Mi.Node M unit of the meter to be read.4.Look for the ID of the register just installed (or the ID on the Mi.Node M unit’s label).Troubleshooting read/installation issuesWhen investigating field issues, it is recommended you bring a spare Mi.Node M unit and register that are verified operational. You can swap the node and register individually to help identify issues. Condition Possible Cause Recommended StepsStatus = No Response Mi.Node M unit is notconnected to register 1.Examine wiring and connectionsfor damage or detachment.2.Try replacing node with anoperational node. Swipe andcheck for a reading.3.If unsuccessful, and wiring is OK,try swapping in the operationalregister.4.If still unsuccessful, it could be anissue internal to the device(s). 5.If a successful read was made,ensure the Install Tool displaysthe correct Mi.Node M unit ID.Status = Q Mark Typically, register was unable todetermine every odometerwheel’s position. Check the register to see if a wheel is in transition. This normally clears as the odometer wheels continue to turn with additional flow.Battery level below Good Mi.Node M unit battery isdegrading. Replace Mi.Node M unit if battery level is Very Low (VLow).Troubleshooting transmission issuesKeyboard commands recommended here begin at the main menu. Condition Possible Cause Recommended StepsNo communication from the node to the receiver (inability to read node) Mi.Node M unit fell off itsmount, or is buried undermud, water, debris, etc.In worst case, waterinfiltration rendered nodeinoperable.•Physically examine node to verifyproper installation or environmentalissues causing problems.•Check connection between Mi.NodeM unit and register; reconnect ifnecessary.Mi.Node M unit transmissionis blocked or unit ispositioned poorly.Physically examine node to verify properinstallation or environmental issuescausing problemsNo reading from the Cut wire, problem at 1.Check connection between Mi.Nodemeter register connection points to theregister or node, or at theinline (Nicor) connector withregister.M unit and register; reconnect ifnecessary.2.Attempt to perform a read (2 > 1 >2, enter ID).Meter dataYou can clear data, which erases readings without deleting the downloaded route.To clear Meter Data1.Press 1 > 3 > 1 (Clear Meter Data).2.Press ENT to clear the data or CLR to cancel and return to the previous screen.To clear List Data1.Press 1 > 3 > 2 (Clear List Data).2.Press ENT to clear the data or CLR to cancel and return to the previous screen.To change RF frequency1.Press 4 > 1 (Channel Set Select). The screen displays an arrow pointing at one channel or theother.2.Press 1 or 2 - the option without the arrow.3.Press ENT.To change Key ClickTo enable or disable the clicking sound when a key is pressed:1.Press 4 > 2 (Key Click). The screen displays an arrow pointing to either 1-Key Click Off or 2-KeyClick On.2.Press 1 or 2 to select Off or On.3.Press ENT.To change Message ClickTo enable or disable the clicking sound when the unit processes messages such as reads:1.Press 4 > 3 (Message Click). The screen displays an arrow pointing to either 1-Msg Click Off or2-Msg Click On.2.Press 1 or 2 to select Off or On.3.Press ENT.Handheld-to-computer interfaceThe Mi.Node M Install tool is charged with a USB cable plugged into a desktop or laptop computer. The USB cable also transmits data from the tool to the computer. The computer must have EZ Export installed.A driver automatically configures the Mi.Node M Install Tool as a serial device with its own COM port defined on the computer. To view The COM designation, navigate on the computer to the Device Manager in the Windows Control Panel. With the Mi.Node M Install Tool unplugged from the computer, scroll to the Ports (COM & LPT) list (if this list is not present, it is because there are no COM ports present on the computer). When the tool is connected to the computer and powered on, its COM port designation will appear in the Ports (COM & LPT) list.About Mueller SystemsWhere Intelligence Meets Infrastructure® Mueller Systems provides Smart Meteringsolutions to optimize the delivery and use of water and energy. Municipalities that supply water, electricity or gas — or any combination of the three services — need innovative ways to increase efficiencies, reduce costs, conserve water and energy, and improve customer service. The ® Mueller Infrastructure Network for Utilities from Mueller Systems meets that need.Mueller Systems develops meters and metering systems that are a Smart Move™ for the most demanding applications including residential, commercial and fire-line meters, advanced metering infrastructure (AMI)/automated meter reading (AMR) systems and related products. We provide utilities with infrastructure technology—including the water industry’s first AMI system with 2-way multidirectional network configuration—that enables them to access the intelligent, actionable data needed to increase efficiencies, reduce costs, conserve water and energy, and improve customer service.Mueller Systems is part of Mueller Water Products, Inc., a leading manufacturer and marketer of products and services used in the transmission, distribution and measurement of water. Contact:Customer SupportMonday – Friday 8am – 7pm ET (800) 323-8584******************************* ************************** Mueller Systems48 Leona Drive Middleborough, MA 02346 Mueller Systems10210 Statesville Blvd. Cleveland, NC 27013Contact:Customer SupportMonday – Friday 8am – 7pm ET (800) 323-8584******************************* **************************。

ITSM使用手册

IT服务管理系统-咨询师使用指南【ITSM工具】简单易用•让咨询服务更高效版本号：V1.0一、编写目的指导咨询师在为客户提供运维服务管理咨询时使用，助力咨询师便捷为客户搭建满足评估要求的ITSM解决方案，减少咨询的工作量、降低咨询成本、提升服务效率、提升客户满意度。

二、使用步骤及操作指南第一步：建立租户1.咨询师为咨询客户申请建立租户向MetaBrother服务经理申请建立租户；2.MetaBrother服务经理建立租户环境，返回链接和账户、密码提示：ITSM工具，SaaS交付，开箱即用3.咨询师使用服务经理返回的链接和管理员账户登录平台第二步：初始化客户的组织和人员1.设置客户的LOGO提示：与咨询客户的实际Logo一致，请务必一次性设置正确。

操作入口截图：2.设置咨询客户组织结构和人员信息提示：系统已缺省设置运维业务和管理部门和角色，直接赋予相关人员角色即可。

必须的操作：导入运维服务团队相关人员信息，并建立和角色（系统已有的角色）的对应关系。

操作入口截图：新增用户：新增用户-发送邀请-用户接收邀请填写验证-验证通过加入组织赋予角色、新增或修改角色：赋予用户所属组织，赋予用户具体角色例如（运维部门经理、服务台人员、服务团队主管、服务团队人员、知识管理人员、备件库管理员、质量人员、其他系统管理人员）等角色，可根据实际情况新增角色；新增角色：填写角色名字，角色编码自动生成，分配个角色独有工作台，分配菜单权限与按钮操作权限；第三步：初始化业务1.设置客户信息提示：系统已缺省设置客户示例，咨询师可设置客户信息基础上做修改即可，修改成与客户项目运维合同中客户信息一致。

操作入口截图：2.设置合同信息提示：咨询师可设置客户合同信息，信息须与客户咨询运维项目的合同信息一致。

操作入口截图：新增合同：支持关联客户，关联合同类型，关联业务对象，关联服务包（服务条目），关联合同附件，成本类合同支持关联物资清单，合同变更及时通知对象维护，支持合同各阶段的履约计划、发票登记。

用户使用手册Remedy系统管理

用户使用手册R e m e d y系统管理文稿归稿存档编号：[KKUY-KKIO69-OTM243-OLUI129-G00I-FDQS58-MG129]凯捷3#4#楼智能化系统BMC Remedy实施项目用户使用手册-系统管理前言本文作为Remedy项目-系统管理员的使用手册，请用户认真阅读此文档后再进入系统。

基本操作系统登录用户可通浏览器端登录。

登录前的准备请在登录前确保您的计算机与系统服务器间的网络保持畅通，同时请检查浏览器中的Flash Player在9.0以上版本。

浏览器端登录（生产环境），按回车键：上图所示为系统的登录页面，请在用户名/密码处输入正确的验证信息后，点击“登录”按钮，即可进入系统。

提示1：显示登录页面后，若浏览器上方提示“是否允许弹出窗口”时，请选择“总是允许该网站的弹出窗口”。

提示2：建议收藏登录地址，以便以后访问。

修改密码当用户需要修改密码时，在登录后的“IT主页”中，找到“更改密码”链接，进入并输入“当前密码”、“新密码”、“确认新密码”后，点击“保存”按钮：提示1：系统管理员在后台重置用户密码后，用户第一次登录时，系统将强制更改密码。

基础配置可在定制配置中【基础】配置处查看详细的高级配置。

公司管理功能描述：创建一个公司,用于之后创建组织人员等等。

操作说明：i.点击创建并配置新公司；ii.弹出窗口可填写公司名称，公司类别分为: Customer(客户)；Operating Company(运营公司)；iii.选择完成点击保存，即可创建公司。

组织管理功能描述：创建一个组和部门.操作说明：i.点击创建即可创建组和部门；ii.弹出窗口需填写组织信息和部门信息，可创建多个组织和部门；iii.点击添加就可以创建组织和部门。

位置管理功能描述：填写公司所在的区域、城市、国家、街道、邮编等。

操作说明：i.点击创建即可创建位置信息；ii.弹出位置窗口，可填写信息有区域、地点组、地点，以及地点地址位置，国家/地区、州/省、城市、邮编、街道、时区；iii.其中需要说明的有国家/地区、州/省、时区等，需要使用系统提供的下拉菜单来进行选择。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

1.2 适用的对象本文档主要针对该系统的管理维护人员。

如果上述设置没有生效，可以采取以下方法：开始菜单-》运行…-》regedit. 然后找到 “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server，然后更新“PerSessionTempDir”和“DeleteTempDirOnExit”为 0 ，重启服务器。

3.2 L icense 的安装Remedy ITSM 项目—系统安装配置手册在安装 Atrium Core 和 Remedy ITSM Suite 应用之前，需要在 AR System 中提前输入相应的 License。

3 .2 .1 申请 Lic en se 安装完 AR System 后，登陆 AR System 的管理员控制台，获取 Host ID，通过 BMC Support 网站申请 AR Server 的 License；开发测试服务器永久 License：： Product Feature: AR Server Expire Date: Host ID: 005056952F95 License: TSE-030554 # of Licenses: 1 生产服务器永久 License：： Product Feature: AR Server Expire Date: Host ID: 005056956115 License: GVM-772172 # of Licenses: 13 .2 .2 L ic en se 安装步骤 1) 通过浏览器或者客户端 BMC Remedy User 工具，使用 Demo 用户登陆 AR System , 在系统管理员管理控制台（Administrator Console），打开 Add or Remove License 页面； 2) 点击 Add New 按钮， License Type 输入框中选择 AR Server 选项， Number of 在在 Licenses 框中输入 1，在 Key 输入框中输入获取的 License，在 Expiration Date 中输入截止日期，点击 Save 按钮保存设置； 3) 按照步骤 2，继续添加如下 License： BMC:Atrium CMDB Application BMC:Atrium Integration Engine BMC:FinancialMgmt ApplicationRemedy ITSM 项目—系统安装配置手册BMC:IncidentMgmt Application BMC:ProblemMgmt Application BMC:AssetMgmt Application BMC:ChangeMgmt Application …… 4) 按照步骤 2，添加 AR User Floating、AR User Fixed 的 License 信息（其中，Key 中不需要输入信息，Number of Licenses 中根据项目采购合同输入相应的数字）； 5) 按照步骤 2，添加 Remedy ITSM Suite（IM，PM，CM，AM，SLM）的 License 信息（其中，Key 中不需要输入信息，Number of Licenses 中根据项目采购合同输入相应的数字）；3.3 系统安装步骤在安装每一个 Remedy 应用软件之前，都需要将其可执行文件添加到系统的 DEP （数据执行保护）列表中： 1) 开始-》计算机-》单击对话框菜单中的“系统属性-》选择左边列表中的“高级系统设置” ：Remedy ITSM 项目—系统安装配置手册2)在高级 Tab 页面中，单击“性能”框的设置按钮，然后选择数据执行保护 Tab 页3)点击添加，将 Remedy 应用的可执行文件添加进来。

（需要添加的可执行文件名称请参考对应的应用安装文档）Remedy ITSM 项目—系统安装配置手册3 .3 .1 A R Sy ste m 7. 6.0 4 平台的安装 1) 启动 AR System 的安装文件“Setup.cmd” ；Remedy ITSM 项目—系统安装配置手册2)根据需要，选择安装路径：3)AR系统安装有两个选项“Minimal Setup”和“Custom Setup”，建议选择“Custom Setup”，根据需要对安装组件进行取舍：4)根据系统未来的应用需求，来对AR System Server下的组件进行选取（根据其它项目的经验，一般后三项很少使用到，因此可以考虑不安装，如果未来有需求，可以在进行增加）5)AR系统目前支持32位和64位的JRE/JDK，但是针对64位的JRE，部分组件的功能还存在一定问题，可以根据系统的情况，决定采用哪种JRE（建议，在缺失功能不影响系统的前提下，建议64位操作系统采用64位JRE）6)选择AR系统的端口，如果客户内部网络对系统端口有限制，建议与客户网管部门确认好一个端口后，在以下界面中输入；否则，采用系统缺省配置即可；7)选择数据库类型8)输入数据服务器的相关信息（可咨询DBA以获取准且的信息）9)输入AR服务器的相关信息（缺省即可）10)输入数据管理员账户名称和密码11)以下为数据库的相关警告信息，如果可能的话，可以在安装前要求DBA将数据库的相关设置进行相应的修改，当然也可以不予理会这些警告，在安装完成后进行调整也可以12)AR系统数据库的文件信息，要注意根据未来安装的Remedy应用情况来修改DatafileSize和Temp Datafile Size13)设置一些AR系统的口令（建议都一样，这样便于管理）14)选择AR系统的启动方式（自动启动或者手工启动）15)选择本地化的视图和数据，一定要选Simplified Chinese，其它的根据项目需要进行选择16)设置Atrium SSO相关配置信息，如果暂时没有Atrium SSO，可以先不予理会17)设置AR服务器RMI端口及RPC端口，如果没有特殊要求，建议采用缺省即可18)设置Email Engine相关配置信息，如果没有，可以暂时不予理会19)配置AR系统服务器列表，如果需要通过Mid-Tier连接多个AR服务器，可以在此进行添加，本次安装的AR服务器缺省已经在列表中20)配置Web服务器相关信息，如果安装了Weblogic，Websphere等商业软件，可以在此选择，否则选择Other；21)选择JSP引擎，如果之前没有安装，可以选择Tomcat，AR服务器自身就带Tomcat22)对Tomcat进行配置，如没有特殊要求，保持缺省值即可23)设置AR系统的Preference Server，Home Page以及DVM Server，没有特殊要求，可以先保持缺省即可24)配置BO XI的位置：如果用户有BO企业级报表服务器，配置后，可以通过报表服务器对Remedy系统的报表进行管理和输出；25)选择系统维护，开发等客户端的安装位置26)选择客户端的语言27)配置完成后的安装清单，方便用户在正式安装前进行最后的确认28)启动安装后，系统进行安装进程，基本不需要人工干预，全部自动完成29)系统可以在安装完成后进行健康检查，以确定系统是否安装成功，建议用户选择Y es30)安装完成后，用户可以查看安装日志，看看安装过程中有没有错误3.3.2A tr ium C ore 7.6.04的安装1)启动BMC Atrium Core的安装文件“Setup.cmd”；2)输入AR Server的相关信息3)根据需求选择安装方式（建议选择Minimal Setup）4)配置CMDB插件服务器端口，没有特殊要求建议保持缺省值5)如果Atrium Core与ARS安装在一台服务器上，则直接选择相应的JRE安装路径，否则可以使用安装程序绑定的JRE。