Commit 033f0431 authored by Liuxiaohong123's avatar Liuxiaohong123

3.0快速上手

parent c4cc5da5
......@@ -224,6 +224,7 @@ class Header extends React.Component {
<NavItem linkTo="/solutions/" title="解决方案" isActive={ pathname.indexOf('/solutions/') > -1}>解决方案</NavItem>
<NavItem linkTo="/free/" title="完全免费" isActive={ pathname.indexOf('/free/') > -1}>完全免费</NavItem>
<NavItem linkTo="/quick-start/" title="快速上手" isActive={ pathname.indexOf('/quick-start/') > -1}>快速上手</NavItem>
<NavItem linkTo="/quick-start3/" title="3.0快速上手" isActive={ pathname.indexOf('/quick-start3/') > -1}>3.0快速上手</NavItem>
<NavItem linkTo="/online/" title="在线体验" isActive={ pathname.indexOf('/online/') > -1}>在线体验</NavItem>
<NavItem linkTo="/download/" title="软件下载" isActive={ pathname.indexOf('/download/') > -1}>软件下载</NavItem>
{/* <NavItem linkTo="/price/" title="报价体系" isActive={ pathname.indexOf('/price/') > -1}>报价体系</NavItem> */}
......
- title: 3.0快速上手
link: /quick-start3/step-0/bs/
- title: 下载、安装和部署
items:
- title: 安装部署前准备工作
link: /quick-start3/step-0/bs/
- title: Windows系统下全新安装
link: /quick-start3/step-0/wininstall/
- title: Windows系统下重新安装或升级安装
link: /quick-start3/step-0/winupdate/
- title: Linux系统下全新安装
link: /quick-start3/step-0/linuxinstall/
- title: linux系统下升级安装
link: /quick-start3/step-0/linuxupdate/
- title: 简易判断安装出错的方法
link: /quick-start3/step-0/installerror/
- title: 一:系统登录注销
link: /quick-start3/step-01/
- title: 二:整体界面说明
link: /quick-start3/step-02/
- title: 三:添加组和编辑组
link: /quick-start3/step-03/
- title: 四:添加资源
link: /quick-start3/step-04/
- title: 五:添加监测器
link: /quick-start3/step-05/
- title: 六:添加报警
link: /quick-start3/step-06/
- title: 七:添加报表
link: /quick-start3/step-07/
- title: 八:立体拓扑图
link: /quick-start3/step-08/
- title: 九:状态巴图
link: /quick-start3/step-09/
- title: 十:矩阵树图
link: /quick-start3/step-10/
- title: 十一:微信小程序
link: /quick-start3/step-11/
- title: 十二:用户角色管理
link: /quick-start3/step-12/
- title: 十三:资源监测设置
link: /quick-start3/step-13/
- title: 十四:数据管理
link: /quick-start3/step-14/
- title: 十五:系统运行时管理
link: /quick-start3/step-15/
- title: 十六:系统检测
link: /quick-start3/step-16/
- title: 十七:操作审计
link: /quick-start3/step-17/
- title: 十八:软件许可
link: /quick-start3/step-18/
- title: 十九:资源图标库
link: /quick-start3/step-19/
- title: 二十:设备信息维护
link: /quick-start3/step-20/
# - title: Step 21:添加visio视图
# link: /quick-start3/step-21/
# - title: Step 22:拓扑扫描
# link: /quick-start3/step-22/
# - title: Step 23:设备管理
# link: /quick-start3/step-23/
# - title: Step 24:设备信息查询
# link: /quick-start3/step-24/
# - title: Step 25:IP管理
# link: /quick-start3/step-25/
# - title: Step 26:诊断工具
# link: /quick-start3/step-26/
# - title: Step 27:运维管理操作步骤
# link: /quick-start3/step-27/
# - title: Step 28:资产管理操作步骤
# link: /quick-start3/step-28/
# - title: Step 29:资源拓扑
# link: /quick-start3/step-29/
# - title: Step 30:资源面板
# link: /quick-start3/step-30/
- title: 高级功能一:资源扫描发现
link: /quick-start3/adv-01/
- title: 高级功能二:数据库替换
link: /quick-start3/adv-02/
- title: 高级功能三:ECC性能优化
link: /quick-start3/adv-03/
- title: 高级功能四:ECC守护进程
link: /quick-start3/adv-04/
- title: 高级功能五:系统自检
link: /quick-start3/adv-05/
- title: 高级功能六:远程桌面
link: /quick-start3/adv-06/
- title: 监测器仪表板一:整体说明
link: /quick-start3/dashboard-01/
- title: 监测器仪表板二:配置
link: /quick-start3/dashboard-02/
- title: 监测器仪表板三:部件配置
link: /quick-start3/dashboard-03/
- title: 监测器仪表板四:高级配置
link: /quick-start3/dashboard-04/
- title: MySQL数据库下载安装使用
link: /quick-start3/step-31/
......@@ -5,20 +5,8 @@ type: tutorial
### 登录
打开浏览器输入安装时设置的服务器地址,可以是物理网卡地址(例如:http://192.168.9.127:8080/);
如连接了虚拟网络,也可用虚拟网卡地址(例如:http://10.1.1.97:8080);
本机也可以用http://localhost:8080/ ,即可打开WeADMIN 启动界面,输入用户名和密码进行登录。默认的管理员帐户为<font color=red>admin</font>,默认密码为<font color=red>manage</font>,字母都是小写。
**<center>新版物理网卡地址登录:</center>**
![img](img/3login.png)
**<center>新版虚拟地址登录:</center>**
![img](img/vlogin.png)
**<center>点击“访问旧界面”显示旧版登录界面:</center>**
![img](img/2login.png)
### 注销
......
---
title: 资源扫描自动发现
type: tutorial
---
IT资源自动扫描发现,用于扫描IP地址范围,密码,端口,设备类型等信息的设置,在设置范围内可网管的设备,可扫描出符合条件的硬件和软件资源。发现后可以查看网络发现的服务器、网络设备和软件应用,通过批量添加添加到[网络设备管理],同时自动添加监测器到监测树中。能够帮助用户在10-15分钟实现对全部IT资源的自动发现和添加,大幅减轻初始添加IT资源和设置监测器的工作量。
<font color=red>注意</font>:被扫描的设备如要实现自动添加需要对应的设备开启了snmp、ssh(linux系统开启ssh方式,请自行搜索)等哦。
具体操作:
1. 点击“IT资源管理”下“资源发现”中的“网络发现”菜单项,进入网络发现界面,如下图所示:
![](img/1.jpg)
2. 在网络发现界面上,设置扫描所需信息,如IP地址类型,扫描范围,所需密码,端口,扫描间隔,及资源类型等,点击“发现”按钮开始扫描,如下图所示:
![](img/2.jpg)
3. 稍等片刻后,界面上显示扫描出的设备信息,点击“批量添加”按钮,即可把设备添加到相应的组,如下图所示:
![](img/3.jpg)
<font color=red>注意</font>:如没有自动添加任何资源,请确认snmp是否开启,且snmp、ssh等设备的共同体、账号密码是否添加到扫描配置页面的密码中哦。
4. 自动批量添加到[IT资源管理]功能模块后的效果,如下图所示:
![](img/4.jpg)
5. IT资源自动发现和描需要安装NMap工具,执行命令:yum install nmap (Redhat)or sudo apt-get install nmap (Ubuntu), Windows下载安装 nmap.org,如下图所示
![](img/5.jpg)
---
title: 数据库替换
type: tutorial
anchorMenu:
- id: step1
title: 1. 创建数据库
- id: step2
title: 2. 下载MSYQL数据库初始文件
- id: step3
title: 3. 数据库配置
- id: step4
title: 4. 数据导入
- id: step5
title: 5. 替换数据库
- id: step6
title: 官网数据库配置注意
---
ECC 默认使用内嵌Mysql数据库,数据库支持 MYSQL ,H2,SQL ,ORACLE,HADOOP等。如需使用企业自己的Mysql数据库,请参考如下配置方式:
**MYSQL数据库替换方法**
<font color=red>注意</font>:凡是使用自建数据(推荐mysql版本使用5.5版本及以上),建议数据库引擎都是用InnoDB,因为它具体有更好的安全性和兼容性;
1. <div id="step1" class="anchor-point">创建数据库: </div>
登录到mysql数据库中,执行<font color=red>`create database ECC DEFAULT CHARACTER SET gbk COLLATE gbk_chinese_ci`</font>; 创建ECC数据库
- linux系统登录mysql:mysql -uroot -p账户密码
- windows系统登录方式:开始-程序-MySQL 5.5 Command Line Client 登录
2. <div id="step2" class="anchor-point">下载MSYQL数据库初始文件:</div>
[点击免费下载](/download)即可获得,该文件根据个人习惯存放即可。
Windows系统下直接解压<font color=red>ECCdb\_mysql.zip</font>数据库文件。
Linux系统下通过执行命令<font color=red>unzip ECCdb\_mysql.zip</font>解压数据库文件。
3. <div id="step3" class="anchor-point">数据库配置</div>
<font color=red>注意</font>:执行数据导入前,请登录mysql数据库,执行如下语句:
`mysql> set global max_allowed_packet=1024*1024*64`;
`mysql> FLUSH PRIVILEGES`;
`mysql> show global variables like 'max_allowed_packet'`;
如上三条语句为一次性,下次重启系统则mysql配置文件还原为原始配置,如想要配置永久生效,可按照如下方式修改:
- linux系统:在/etc下找到my.cnf文件,如果没有,则在/usr/share/mysql中复制任一一个后缀为.cnf的配置文件到/etc目录下,并改名为my.cnf,进入到/etc目录下,执行 vi my.cnf 修改配置文件,配置项添加到[mysqld]下即可。
- windows系统:进入到mysql安装目录下,找到my.ini文件,在[mysqld]下面添加对应配置项即可
![](img/3.jpg)
4. <div id="step4" class="anchor-point">数据导入: </div>
执行命令,需进入到数据库初始化文件目录下执行(下载的更新数据库sql文件存放在什么位置,则cmd窗口需进入到对应盘符执行对应命令) <font color=red>mysql -uroot -p数据库密码 --default-character-set=utf8 ECC < ECC-mysql-2015-11-03.sql</font>
![](img/1.jpg)
5. <div id="step5" class="anchor-point">替换数据库</div>
- 登录系统,点击[系统设置][数据源管理]中的[数据源配置]
- 选择配置数据源
![](img/2.png)
- 新建“mysql数据库”并设置服务器地址,数据库名称,用户名和密码,点击“测试连接”,待提示测试成功后点击“确定”
![](img/4.png)
- 修改数据库连接配置后需要从新启动ECC程序
<div id="step6" class="anchor-point">官网数据库配置注意:</div>
官网数据库配置,mysql需要开启访问权限。如果没开启,登陆到mysql,执行如下命令
第一条`GRANT ALL PRIVILEGES ON *.* TO root@"%" IDENTIFIED BY "mysql的密码"`;
第二条`FLUSH PRIVILEGES`;
连接不上的情况下, 将mysql目录下my.cnf文件中bind-address = 127.0.0.1 这一行前面加上#号(注释)
即:#bind-address = 127.0.0.1
\ No newline at end of file
---
title: ECC性能优化详解
type: tutorial
anchorMenu:
- id: step1
title: 一、Java内存优化
- id: step2
title: 二、监测器刷新时间
- id: step3
title: 三、ELASTICSEARCH内存配置
---
#### <div id="step1" class="anchor-point">**一、Java内存优化**</div>
在安装目录下Windows通过修改start.bat,Linux 通过修改start.sh文件实现对WEB端口修改以及内存使用设置。
JDK需要1.8及以上,推荐使用JDK1.8版本;
- 硬件配置:
监控点数|CPU|内存|磁盘|操作系统
:-----:|:-:|:--:|:--:|:-----:
1-100|普通双核 CPU2.0HZ|2G及以上|30G-40G|Windows2008/2012,CentOS,RedHat,Ubuntu
100-200|普通双核 CPU2.5HZ|4G及以上|60G-80G|Windows2008/2012,CentOS,RedHat,Ubuntu
200-500|Intel4核 CPU3.0HZ|8G及以上|150-200G|Windows2008/2012,CentOS,RedHat,Ubuntu
500-1000|Intel4核 CPU3.0HZ|16G及以上|200G-300G|Windows2008/2012,CentOS,RedHat,Ubuntu
1000-2000|Intel8核 CPU3.0HZ|32G及以上|300G-500G|Windows2008/2012,CentOS,RedHat,Ubuntu
1. Windows
端口修改:将 <font color=red>`Dorg.osgi.service.http.port= 8080`</font> ^ 中的 8080替换成所需端口即可。
内存修改:将 <font color=red>`-Xms, -Xmx,-Xmn,-XX:PermSize,-XX:MaxPermSize`</font> 修改成所需分配内存即可,其中-Xms, -Xmx配置为服务器内存的1/2或以上,而且-Xms和-Xmx值需一样;-Xmn配置为-Xms值得1/2;-XX:PermSize和-XX:MaxPermSize配置为服务器内存的1/4。
监控点数|内存配置|JDK版本|数据库
:-----:|:-----:|:-----:|:---:
1-100|2G|JDK1.8及以上,推荐JDK1.8|H2,MYSQL,SQL
100-200|4G|JDK1.8及以上,推荐JDK1.8|MYSQL,SQL
200-500|8G|JDK1.8及以上,推荐JDK1.8|MYSQL,SQL
500-1000|16G|JDK1.8及以上,推荐JDK1.8|MYSQL,SQL
1000-2000|32G|JDK1.8及以上,推荐JDK1.8|MYSQL,SQL
2000-5000|32G|JDK1.8|MYSQL
5000+|分布式解决
![](img/23-1.jpg)
2. Linux
端口修改:将<font color=red>`Dorg.osgi.service.http.port= 8080`</font> ^ 中的 8080替换成所需端口即可。
内存修改:将 <font color=red>`-Xms, -Xmx, -Xmn, -XX:PermSize, -XX:MaxPermSize`</font> 修改成所需分配内存即可,其中-Xms, -Xmx配置为服务器内存的1/2或以上,而且-Xms和-Xmx值需一样;-Xmn配置为-Xms值得1/2;-XX:PermSize和-XX:MaxPermSize配置为服务器内存的1/4。
监控点数|内存配置|JDK版本|数据库
:-----:|:-----:|:-----:|:---:
1-100|2G|JDK1.8及以上,推荐JDK1.8|H2,MYSQL,SQL
100-200|4G|JDK1.8及以上,推荐JDK1.8|MYSQL,SQL
200-500|8G|JDK1.8及以上,推荐JDK1.8|MYSQL,SQL
500-1000|16G|JDK1.8及以上,推荐JDK1.8|MYSQL,SQL
1000-2000|32G|JDK1.8及以上,推荐JDK1.8|MYSQL,SQL
2000-5000|32G|JDK1.8|MYSQL
5000+|分布式解决
![](img/23-2.jpg)
<font color=red>注意</font>:如果是通过守护进程方式启动ECC,则需要修改安装目录下\yajsw\conf下的wrapper.conf配置文件。
#### <div id="step2" class="anchor-point">**二、监测器刷新时间**</div>
1. CPU使用率过高,建议您先将检测器刷新频率设置,如果您所有监测器全部频率均为10分钟,则在同一时间所有监测器均在刷新取值中,则该时间段CPU使用率肯定是过高状态,建议您不同的监测器设置不同的刷新频率,如磁盘等可以设置刷新时间为半天或者一天哦。
<font color=red>注意</font>:监测器刷新时间,按本地系统时钟更新,例如:设置5分钟更新,则系统时钟在5、10、15、20分钟的时刻....类推,自动刷新,如设置10分钟更新,则系统时钟在10、20、30分钟的时刻...类推上刷新,大家可以按照这个例子设置监测器自身需求刷新时间,或者错开高峰刷新时间,如您设置的是11分钟刷新一次,则按11,22,33,44,55刷新,60分钟后,又重回至11,22,33......。
#### <div id="step3" class="anchor-point">**三、ELASTICSEARCH内存配置**</div>
**Linux系统优化配置**
1. 默认ELASTICSEARCH内存最大为1G,您可以根据您的实际情况,进行调整,具体修改文件为ECC安装目录下elasticsearch-2.3.2\bin\elasticsearch.in.sh(LINUX系统)。
![](img/23-3.png)
2. 如WeADMIN ECC服务器内存空间比较大,给ES分配超过4G的(ES分配内存不可超过32G),需要将 elasticsearch.in.sh(Linux系统) 文件中做调整(G1配置法)。
Linux系统配置增加如下语句
`ES_GC_OPTS="$ES_GC_OPTS -XX:+UseG1GC"`
`ES_GC_OPTS="$ES_GC_OPTS -XX:MaxGCPauseMillis=500"`
![](img/23-4.png)
<center>
Linux系统配置参考
</center>
**Windows系统优化配置**
1.2.7版本前,es优化只需要修改bin目录下的elasticsearch.in.bat文件即可,现1.2.7版本后优化ES方式如下:
1. 启动ECC服务;
2. cmd窗口进入到\elasticsearch-2.3.2\bin目录下,执行“service manager”,配置如下:
![](img/23-5.png)
3. 如上图,如Es分配超过4G(ES分配内存不可超过32G),需要将ES进行调优,在“JAVA Options”中追加如下图语句:
![](img/23-6.png)
-XX:+UseG1GC
-XX:MaxGCPauseMillis=500
对应1.2.7版本前的如下配置:
![](img/23-7.png)
\ No newline at end of file
---
title: ECC守护进程介绍
type: tutorial
anchorMenu:
- id: step1
title: Windows ECC守护进程配置文件说明
- id: step2
title: 一、WeADMIN ECC 守护进程安装:
- id: step3
title: 二、WeADMIN ECC守护进程使用:
- id: step4
title: Linux系统WeADMIN ECC守护进程使用说明
- id: step5
title: 一、WeADMIN ECC 守护进程安装:
- id: step6
title: 二、WeADMIN ECC守护进程使用:
---
ECC守护进程在软件系统的应用过程中,会遇到这样的情况,当服务端设备关机或者重启之后,都需要手动启动软件程序而不能实现软件自启动的功能;守护进程能够有效地解决此问题,安装好守护进程功能后,将软件注册成开机自启动的服务,当服务端设备重启后软件能够实现自启动的功能;守护进程也能够解决内存溢出的问题,当遇到内存溢出的时候会将软件进程重新启动,从而保障软件能够正常运行。
ECC守护进程下载地址:
[点击官网下载](ftp://ftp.WeADMIN.com/ECC/WeADMIN_sh.zip)
注意:最新版本V1.2.0程序已内嵌默认安装了守护进程,无需您再次安装,V1.2.0以下版本则需手动部署,建议您升级到V1.2.0哦。
#### <div id="step1" class="anchor-point">**Windows ECC守护进程配置文件说明**</div>
1. 守护进程的配置文件wrapper.conf在\yajsw\conf目录下,打开此配置文件可以对WEB访问端口、JAVA内存进行配置,如下图所示:
![](img/1.png)
Windows系统WeADMIN ECC守护进程使用说明
<font color=red>注意</font>:最新V1.2以上程序版本已默认安装了守护进程,无需您再次安装,只需要执行第二大步骤即可。
#### <div id="step2" class="anchor-point">**一、WeADMIN ECC 守护进程安装:**</div>
1. 将下载下来的守护进程安装包解压,再将如图1解压后的文件和文件夹拷贝到软件安装目录下,如图:
![](img/2.png)
![](img/3.png)
2. 打开cmd窗口,进入到软件的安装目录下,运行service.bat install,待提示Service ECC installed,表示守护进程安装成功,如下图所示:
![](img/4.png)
#### <div id="step3" class="anchor-point">**二、WeADMIN ECC守护进程使用:**</div>
1. 回到ECC的安装目录下,运行service.bat start,待提示Service ECC started,如下图所示;表示守护进程服务已经开启,后台在下载更新安装包,待守护进程目录下新增的文件夹bundle-cache,topo.db,toposet,weadminserver1-tcp1921689611883,workspace都出现之后,如下图所示,表示安装包更新完成,可以打开浏览器访问`http://localhost:8080`登录软件系统。
![](img/5.png)
![](img/6.png)
2. 打开任务管理器,在进程列表中可以查看得到有两个java.exe进程,如下图所示:
![](img/7.png)
3. 当程序遇到内存溢出时守护进程功能会将软件自动重启,从而保证软件的正常运行;守护进程服务关闭功能,运行service.bat stop,待提示Service ECC stop之后,表示守护进程服务已关闭,如下图所示:
![](img/8.png)
### <div id="step4" class="anchor-point">**Linux系统WeADMIN ECC守护进程使用说明**</div>
<font color=red>注意</font>:最新V1.2以上程序版本已默认安装了守护进程,无需您再次安装,只需要执行第二大步骤即可。
#### <div id="step5" class="anchor-point">**一、WeADMIN ECC守护进程安装:**</div>
1. 将下载下来的守护进程安装包解压,再将解压后的文件和文件夹拷贝到软件安装目录下,如图:
![](img/9.png)
2. 在WeADMINECC目录下执行chmod 777 *命令,对WeADMINECC目录下所有文件赋予可执行权限;
3. 在WeADMINECC目录下执行chmod -R 777 yajsw命令,对文件夹yajsw下所有文件赋予可执行权限。
4. 在软件安装目录WeADMINECC下运行./service.sh install,待提示Service ECC installed,表示守护进程服务安装成功,如图所示。
![](img/10.png)
#### <div id="step6" class="anchor-point">**二、WeADMIN ECC守护进程使用:**</div>
1. 在软件安装目录WeADMINECC下运行./service.sh start,待提示Service ECC started,表示守护进程服务开启成功,如图所示;后台在下载更新安装包,待守护进程目录下新增的文件夹bundle-cache,topo.db,toposet,weadminserver1-tcp1921689611883,workspace,home都出现之后,如图所示,表示安装包更新完成,可以打开浏览器访问`http://localhost:8080`登录软件系统。
![](img/11.png)
![](img/12.png)
2. 将软件设置成开机自启动功能,执行命令:ln -s /usr/java/bin/java /usr/bin,如图所示
![](img/13.png)
<font color=red>注意</font>:创建完成后,在usr/bin目录下执行ls -l java,如下所示,则表示您软连接创建成功。
![](img/14.png)
如不是如上显示,则需要先删除原连接后,重新创建,命令为 rm -rf 目标文件或目录
3. 运行ps –ef|grep java,可以查看得到有两个java.exe进程,如图所示;
![](img/15.png)
4. 当程序遇到内存溢出时守护进程功能会将软件自动重启,从而保证软件的正常运行;守护进程服务关闭功能,运行service stop,待提示Service ECC stop之后,表示守护进程服务已关闭,如图所示:
![](img/016.png)
5. Linux系统配置完成守护进程后,建议您将hostname 127.0.0.1这条命令加到/etc/rc.d/rc.local中,可防止配置守护进程后无法获取数据问题
\ No newline at end of file
---
title: 系统自检
type: tutorial
---
系统自检是WeADMIN ECC一体化IT运营支撑系统针对系统部署的环境、运行状态、硬件资源情况,系统数据库配置运行情况,系统插件模块运行情况,系统仪表板运行情况的自检与自恢复的过程,方便用户简单快速了解掌握系统自运行健康状态,系统自身发生故障会以颜色告警显示,也方便用户精确定位系统自身运行问题并对系统运行维护,迅速恢复正常,保障系统持续健康运营。
1. 系统自检不依赖于产品任何功能,可独立即时运行。即系统无法登陆、故障、报错等问题发生时,将访问登录系统地址栏中的webloader改成selfcheck查看即可。打开方式:IP地址:8080/selfcheck(IP地址为WeADMIN ECC部署的服务器IP地址)。
2. 登录系统后,点击“系统设置”下的“系统监测”查看也可。
![](img/1.png)
\ No newline at end of file
---
title: Linux系统安装Docker操作说明-作用远程桌面连接功能
type: tutorial
---
WeADMIN ECC1.2.6支持远程连接,如需使用,需要安装Docker,Docker并不要求要和ECC安装在同一台设备上,比如示例中的WeADMIN ECC安装在192.168.9.84(win7),Docker是安装在192.168.9.177(centos7)上(注意:两者之前的网络需能够互通),安装好Docker后,只要修改WeADMIN ECC下的start.bat(前台启动)或wrapper.conf(守护进程)中的配置内容,启动WeADMIN ECC即可使用远程连接功能,具体操作如下:
1. 准备系统
举例以CentOS7的环境为说明,如图所示:(安装Docker要求必须是CentOS7或者以上版本):
![](img/1.png)
2. 确认内核版本
检查当前内核版本:`uname -r`,注Docker都要求64位并且当CentOS7时你的内核必须不小于3.10,如图所示:
![](img/2.png)
<center>yum安装</center>
3. 使用root权限登陆系统
4. 确认yum为最新的
执行 `yum -y update` 命令,如图所示:
![](img/3.png)
执行完成如下图所示:
![](img/4.png)
5. 移除非官方的docker相关包
命令:
`yum -y remove docker docker-common container-selinux`
![](img/5.png)
`yum -y remove docker-selinux`
![](img/6.png)
6. 设置仓库
执行命令:`yum install -y yum-utils`,结果如下所示:
![](img/7.png)
然后执行命令:
- `sudo yum-config-manager \`
- `--add-repo \`
- `https://download.docker.com/linux/centos/docker-ce.repo`
执行命令后如下图所示:(注意:这个下载链接地址不一定永久有效,如果失效请具体参考docker的官方网站进行修改)
![](img/8.png)
7. 执行命令:
`sudo yum makecache fast`,如下图所示:
![](img/9.png)
8. 执行命令安装docker:
`sudo yum install docker-ce`,如下图所示表示尚未成功,则继续执行下面步骤,如安装成功了,则可直接从第11步开始执行:
![](img/10.png)
9. 执行命令:`yum list docker-ce.x86_64 --showduplicates |sort -r`
![](img/11.png)
10. 执行命令:`sudo yum install docker-ce-<VERSION>`,如下图所示:
![](img/12.png)
执行完成结果如下所示:
![](img/13.png)
11. 启动docker,执行命令:`systemctl start docker`,并执行命令:`docker ps`查看是否启动成功,如下所示:
![](img/14.png)
12. 执行 `docker load < guacd.tar.gz`命令安装镜像文件(<font color=red>注意</font>:该例子中的guacd.tar.gz放在/root下),如图所示:
![](img/15.png)
13. 执行命令:`docker images`可以确认镜像文件是否安装成功,如下图所示则表示成功:
![](img/16.png)
14. 执行:
![](img/17.png)
15. 执行命令:`docker ps -l`,可以查看到已经执行的最新的docker容器,如图所示:
![](img/18.png)
16. 把WeADMIN ECC中配置的 -DECC.tunnel.host=IP地址改成这台cetos7机器的IP地址即可,如图所示:
![](img/19.png)
17. 启动WeADMIN ECC软件,验证WeADMIN ECC是否能够进行远程连接,如图所示:
![](img/20.png)
18. 如重启Docker服务器后,无法正常使用,可参考如下解决方案:
**方式一:**
- 重启服务器后需要启动docker,命令为`systemctl start docker`,`docker ps -l`命令查询状态。
![](img/21.png)
- 启动容器,输入`Docker start` 容器id,然后`docker ps -l` 查看,如图:
![](img/22.png)
**方式二:**
- 重新装镜像,“docker rm 容器id”、“docker rmi 镜像名称”,如图:
![](img/023.png)
- 然后重新安装guacd(参照docker安装中12步骤),执行 docker load < guacd.tar.gz命令安装镜像文件。
\ No newline at end of file
---
title: 监测器仪表板整体说明
type: tutorial
---
#### **一、整体说明**
监测器仪表板为用户提供方便、醒目、直观的监测器仪表板。用户通过简单几步可视化定义,即可得到炫酷的监测器图形化界面,一目了然地查看监测设备各指标信息以及趋势情况,并且能够通过在时间轴上选择实时查看各年,月,日,小时等关心的数据信息。具体操作如下:
1. 选中任一资源,点击界面上方栏中“历史曲线”按钮,如下图所示:
![](img/1.png)
2. 点击按钮后,点击界面菜单栏中“视图”,如下图所示:
![](img/2.png)
3. 进入如图界面:
![](img/7.png)
右上角快捷按钮:
- 刷新:<span class="img-auto">![](img/3.png)<span>为“刷新”按钮;
4. 在窗口中点击编辑,即可编辑,如图:
![](img/4.png)
5. 此外:
![](img/1.png)
界面按钮介绍:
- 左侧绿色图标<span class="img-auto">![](img/5.png)<span>(鼠标放到上面弹出,鼠标点击可展开操作)对行操作的按钮;
- 右下角紫色的图标<span class="img-auto">![](img/6.png)<span>,可实现添加行。
---
title: 监测器仪表板配置
type: tutorial
---
#### **二、仪表板配置**
1. 点击到仪表板,鼠标放到左侧绿色隐藏的图标上点击,即可看到折叠行、增加部件、设置高度、移动、编辑行、删除行 按钮,如下图:
![](img/1.png)
- 折叠行:针对选中的行进行折叠;
- 增加部件:可增加图表、单一统计、文本;
- 设置高度:选中后在右侧可以选择弹出的高度,对图表设置需要的高度;
- 移动:针对选中的行进行上移或下移操作;
- 编辑行:点击编辑行可对行进行常规设置和面板设置;
- 删除行:删除行操作。
2. 编辑行,如下图:
![](img/02.png)
\ No newline at end of file
---
title: 监测器仪表板部件配置
type: tutorial
---
#### **三、仪表板部件配置**
1. 选择[添加部件]--->[图表],即可在所在行新增一个图标,如下图:
![](img/1.png)
2. 点击左侧第一个图表的标题,选择“编辑”按钮,如下图:
![](img/2.png)
3. 编辑后,可弹出新的界面,如下图:
![](img/3.png)
4. 在 新界面中 “指标”中选择组名、设备名、监测器名、监测指标,可以添加查询,在同一个图表中可以显示同一监测器的不同指标。
<font color=red>注意:只有当ECC产品中已添加了组、设备、监测器,在该界面中才有可选项,如未添加则选项中为空。</font>
ECC软件中添加设备如图:
![](img/4.png)
编辑图标选择组、设备、监测器、监测指标,如图:
![](img/5.png)
右侧按钮:可以通过右侧按钮,添加多个查询条件(多个参数)
- 指标:鼠标点击到组选择需要查看的组,选择设备名,选择监测器,监测指标(数据同步,可选择组、设备、监测器等)。例如:选择服务器组,192.168.0.218设备名,选择CPU监测器,选择监测指标。会出现如下图所示:
![](img/6.png)
- 轴&表格: 在“轴&表格”中,可设置图标X轴和Y轴,设置图例等,如图红框中所示:
![](img/7.png)
- 显示样式:可以设置显示样式,包括柱状图、线、点、线宽度、空值模式、阶梯线、层积、百分比、渲染、提示等。
![](img/8.png)
- 时间段:设置覆盖相对时间和添加时移等。
![](img/9.png)
- 配置后的效果,返回“仪表边”查看,如下图:
![](img/10.png)
\ No newline at end of file
---
title: 监测器仪表板高级配置
type: tutorial
---
#### **四、仪表板高级配置**
1. 添加多个查询条件,点击图标“编辑”图标,在“指标”选项卡中,可以添加“添加查询”按钮,查询同一个监测器多个参数,具体如图:
![](img/1.png)
2. 设置图表参数中线路颜色,点击图标“编辑”,在“常规”选项卡中,点击参数中“颜色”,如下图所示,可以设置线路颜色,参数靠左靠右显示
![](img/2.png)
3. 设置单个指标特殊显示效果,点击图标“编辑”,在“显示样式”中,点击添加系列覆盖规则,选择特例的样式和格式。如:选择[]--->[true]
![](img/3.png)
选择后的效果图:
![](img/4.png)
4. 设置完成后,点击右上角“返回仪表板”按钮,查看效果,如图:
![](img/5.png)
点击图表下方单个参数,可以展现单个参数图形,如下图:
![](img/6.png)
单个参数的字体颜色会加深,再次点击展现所有参数。
5. 设置多个监测器和参数的效果图:
![](img/7.png)
![](img/8.jpg)
\ No newline at end of file
This diff is collapsed.
---
title: 安装部署前准备工作
type: tutorial
anchorMenu:
- id: step1
title: 第一步:准备安装系统所需的服务器
- id: step2
title: 第二步:安装操作系统
- id: step3
title: 第三步:安装浏览器
- id: step4
title: 第四步:下载JDK并配置
- id: step5
title: 第五步:下载WeADMIN ITOSS系统
---
#### <div id="step1" class="anchor-point">第一步:准备安装系统所需的服务器</div>
推荐配置为:CPU 4核以上 / 内存 8G以上 / 硬盘 50G以上
确保服务器与被监测的IT资源网络是互通的,在服务器上采用PING命令PING被监测IT资源的IP地址.
可以用ping检测方式,例如:
ping 192.168.9.127
![img](img/ping.png)
#### <div id="step2" class="anchor-point">第二步:安装操作系统</div>
推荐使用:Windows Server 2008 / 2012 / 2013 /2019或是 Linux操作系统 Ubuntu / Centos
#### <div id="step3" class="anchor-point">第三步:安装浏览器</div>
推荐使用:IE9+ / Google Chrome 29+ / Firefox 23+ / Safari 6+ / Microsoft Edge 1.0+ / Opera 15+
#### <div id="step4" class="anchor-point">第四步:下载JDK并配置</div>
1. 下载JDK
ITOSS2.0及以下系统推荐JDK 1.8,暂不支持JDK1.9以上版本,建议安装JDK1.8的用户在系统推荐更新时不要升级到JDK1.9以上版本)。
**JDK 8** 下载:
|名称|操作系统|版本|下载|
|:--:|:-------:|:--:|:--:|
|JDK|Windows x64|8u45|[百度云下载](https://pan.baidu.com/s/1c130c2O)|
|JDK|Mac OS X x64|8u45|[百度云下载](https://pan.baidu.com/s/1pJl4kgb)|
|JDK|Linux x64|8u40|[百度云下载](https://pan.baidu.com/s/1ntL8ZPJ)|
  <font color=red>ITOSS3.0系统需要安装JDK11</font>
  **JDK11**下载:[点击下载](http://download.weadmin.com/jdk/jdk-11.0.11_windows-x64_bin.exe)
2. JDK安装配置配置
</font>[点击可直接跳转至JDK安装配置说明页面。](../../../FAQ/sl/faq5/)
3. </font>执行<font color=red>java -version</font>确认JDK版本
LINUX系统下在确认JDK版本的时候,需要注意OPNEJDK版本是有问题的,如下图所示,因为OPENJDK版本是精简版本,存在缺失某些功能的情况,需安装全功能版本。
![img](img/0-1.png)
#### <div id="step5" class="anchor-point">第五步:下载WeADMIN ITOSS系统</div>
[WeADMIN ITOSS 绿包安装包下载](/download/),安装包文件为完整绿色版,可以在企业内网和外网(有互联网)环境下使用。
[建议安装部署ECC前,先看下关于部署ECC的环境要求。](/product/ecc-it/#demand)
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment