Unit_2_Installation_and_configuration(P55)

Teamcenter 10 安装操作手册一．系统环境 (2)1.硬件环境 (2)2.安装操作系统 (2)3.安装JAVA环境 (2)4.设置用户环境变量和系统环境变量 (4)二．安装ORACLE 11G (6)1.安装Oracle 数据库 (6)2.安装数据库实例 (11)三．安装LICENSE (27)1.复制修改License文件 (27)2.运行安装程序 (27)3.检查License服务 (30)四．安装TEAMCENTER (两层) (32)五．安装TEAMCENTER（四层） (45)1.安装Pool_manager (45)2.安装Webtier (51)3.安装Weblogic (64)4.安装Apache (80)5.下载客户端 (85)6.启动服务 (88)7.登录客户端 (88)一．系统环境1.硬件环境2.安装操作系统设置好计算机名和固定的IP地址，关闭防火墙；3.安装JAVA环境1)运行JDK安装程序jdk-7u45-windows-x64.exe，根据安装的操作系统类型选择相应的安装程序，如安装的系统为64位的，则安装64位的JDK；2)安装步骤4.设置用户环境变量和系统环境变量检测JAVA环境是否安装正确：如图所示，JAVA环境安装OK！二．安装Oracle 11g1.安装Oracle 数据库打开oracle安装包，运行setup.exe:选择【仅安装数据库软件】，选择【下一步】默认，选择【下一步】默认，选择【下一步】选择【企业版】，选择【下一步】根据需要选择路径，选择【下一步】检查安装的产品信息，选择【完成】安装完成！2.安装数据库实例1)配置监听打开【开始】→【所有程序】→【Oracle - OraDb11g_home1】→【配置和移植工具】→【Net Configuration Assistant】点选【监听程序配置】，选择【下一步】默认，选择【下一步】默认，选择【下一步】默认，选择【下一步】默认，选择【下一步】默认，选择【下一步】默认，选择【下一步】配置完成！2)复制配置文件将TC 10安装包下的文件：D:\tc\db_scripts\oracle\*，全部复制：到C:\app\Administrator\product\11.2.0\dbhome_1\assistants\dbca\t emplates\*下面：3)安装实例打开【开始】→【所有程序】→【Oracle - OraDb11g_home1】→【配置和移植工具】→【Database Configuration Assistant】点选【创建数据库】，选择【下一步】选择【Teamcenter Oracle11g】,如果前面没有复制系统配置文件则没有此选项给出数据库实例名，如：tc10给出用户密码，一般用：infodba作为系统所有用户密码此页面，在【调整大小】的进程根据需要，给出适合的值，如，300在【字符集】中选择【从字符集列表中选择】：ZHS16GBK-GBK 16位简体中文打开左侧【表空间】，选择需要的表空间，并且给出适合的文件大小，如图所示：选择TEMP，文件大小为100MB；检查配置资料，如过没有问题，点击【确定】开始创建实例创建完成，点击【退出】。

GuideVersion6.2FORTINET DOCUMENT LIBRARYhttps://FORTINET VIDEO GUIDEhttps://FORTINET BLOGhttps://CUSTOMER SERVICE&SUPPORThttps://FORTINET TRAINING&CERTIFICATION PROGRAM https:///support-and-training/training.htmlNSE INSTITUTEhttps://FORTIGUARD CENTERhttps:///END USER LICENSE AGREEMENThttps:///doc/legal/EULA.pdfFEEDBACKEmail:********************June07,2019FortiGate/FortiManager6.2Communications Protocol Guide 01-620-282493-20190607TABLE OF CONTENTSChange Log4 Overview5 Exceptions5 Protocol components6 FGFM header6 Keep-Alive messages6 Customizing the Keep-Alive settings6FortiManager passive mode7 FortiGate to FortiManager authentication8 Tunneling9 Tunnel setup details9 Communication hardening10 Protocol operation on FortiGate11 Security concerns11 Protocol operation on FortiManager12 Topology scenarios13 Scenario1:FortiGate has public IP address,FortiManager is behind NAT13 Scenario2:FortiManager on a routable public IP address/FortiGate behind NAT14 Scenario3:Both FortiManager and FortiGate have public IP addresses14 Scenario4:Mixed topology15 Scenario5:Both devices behind NAT15 FGFM built-in recovery16 Making changes to the FortiGate management IP address16 FGFM recovery logic16 Example17Change Log2019-06-07Initial release.OverviewThe fgfm protocol implements a secure communication protocol with the following functions:1.FortiGate reachability status(from FortiManager)2.FortiManager reachability status(from FortiGate)3.Configuration installation and retrieval4.Script push5.JSON monitoring via RTMExceptionsThe following communications between FortiGate and FortiManager units are handled outside of the fgfm protocol and are managed by the FortiGuard protocol:1.FortiGuard package downloads(AV,IPS,Virus Scan,etc.)2.FortiGuard query(WF,AS)3.Firmware DownloadsProtocol componentsThe fgfm protocol runs over SSL(Secure Sockets Layer)using TCP port541under IPv4.FortiManager6.2supports the use of IPv6.Both FortiGate and FortiManager units have a fgfm daemon running exclusively for FortiGate to FortiManagercommunication.The FortiManager unit listens on TCP port541for an incoming session request.The FortiGate unit establishes an SSL session with the FortiManager.Both units use TCP port541for sending and receiving messages.The fgfm daemon handles all FortiGate to FortiManager(and vice versa)authentication,keep-alive messages and actions resulting from them(such as instructing another daemon on a FortiGate device to update its configuration or various database files).FGFM headerThe fgfm header is a simple header that indicates the purpose of the message,such as keep-alive,authentication and packet forwarding.Keep-Alive messagesThe FortiGate unit sends keep-alive messages to the FortiManager every120seconds or2minutes.If theFortiManager unit does not receive3consecutive messages(360seconds or6minutes),it considers that specific FortiGate unit to be unreachable,disabled or otherwise offline.When that unit comes back online,it must re-establish an SSL connection with the FortiManager before management functions can continue.It will attempt to do so using the last-known IP address and serial number of the FortiManager device.The FortiManager will do the same.The keep-alive message contains information that assists the FortiManager in managing the FortiGate unit,such as current OS version,platform,configuration checksum and versions of the unit’s AV and IPS databases.Customizing the Keep-Alive settingsYou can customize how quickly the FortiManager can detect an issue or failure of a managed FortiGate device.Keep in mind that shortening the interval between the units will let the FortiManager find a device failure more quickly,it can also generate a substantial amount of processing overhead to the FortiManager system when the unit is managing many devices.To change the keep-alive interval(default values are listed):get system dm.......fgfm-sock-timeout:360Protocol components7 fgfm_keepalive_itvl:120.......endPlease note the difference between the two above commands(dash versus underscore).FortiManager passive modeAfter a FortiGate unit receives a keep-alive message from a FortiManager unit containing the unit’s OS version,AV and IPS database versions and configuration information,it compares that information with its local versions.If theFortiManager unit has a newer version of any of the above and the FortiGate is configured to receive automaticupdates,the fgfm daemon running on the FortiGate will then notify the FortiGuard daemon running.The FortiGuard daemon will then issue an update request to the FortiManager unit.The information sent by the FortiManager is notsent via the SSL connection on TCP port541;FortiManager uses UDP port9443to send this information.The keep-alive message is the de facto‘push’action for delivering update notifications.The FortiManager unit willnever send updates to the FortiGate unit;the FortiGate unit instead downloads updates from the FortiManager.FortiGate to FortiManager authenticationOnce a FortiManager has accepted an incoming connection from a FortiGate unit,the FortiManager will send its certificate to the FortiGate unit via SSL.The FortiGate unit then authenticates the certificate as follows:1.It compares the serial number provided in the authentication message against the one in the certificate;2.It verifies that the serial number is in its local allowed serial number table;3.It then verifies the validity of the certificate.If any of the above steps fail,authentication fails and the FortiGate unit will not accept management from theFortiManager.This authentication process occurs at the start of any new SSL session.Communication sequence for authenticationEach FortiGate unit maintains a local trusted list containing up to ten unique entries.This contains a list ofFortiManager serial numbers that the FortiGate is willing to yield management rights to.If a FortiManager unit with a serial number not on that FortiGate’s trust list attempts to connect to the FortiGate,the unit will immediately terminate the connection and refuse to be managed.The local trusted list on the FortiGate is not configurable and the serial number of the managing FortiManager is added to the device’s trusted list when added to the FortiManager’s list of managed devices.TunnelingAll other management traffic,which at this point will only be RTM traffic,is tunneled through the SSL connection with an fgfm header identifying the packet data as an IP packet to be extracted and passed to the device over a tunnel interface (see next section for more details).Tunnel setup detailsThe following settings are sent from FortiManager to the FortiGate unit during the setup of the fgfm tunnel:To enable the following viewing,you must log in to the FortiGate CLI with the administrativeaccount and enter the following debug commands:#diagnose debug enable#diagnose debug application fgfmd255After entering the above commands,you will see the following log printed out on the FortiGate CLI during fgfm tunnel setup:......FGFMs:Set managment id247331677OK.FGFMs:[__chg_by_fgfm_msg]set keepalive_interval:300FGFMs:[__chg_by_fgfm_msg]set channel buffer/window size to32768bytesFGFMs:[__chg_by_fgfm_msg]set sock timeout:900FGFMs:[fgfm_msg_put_tuninfo]vdom=’root’,physical_intf=,intf=’wan1’FGFMs:client:send:get ipfirst_fmgid=probe_mode=yesvdom=rootintf=wan1FGFMs:client:reply200overwrite_fmgid=1request=ipip=169.254.0.2mgmtid=247331677register_status=1fmg_ip=192.168.48.46keepalive_interval=300chan_window_sz=32768sock_timeout=900FGFMs:[__chg_by_fgfm_msg]set keepalive_interval:300FGFMs:[__chg_by_fgfm_msg]set channel buffer/window size to32768bytesFGFMs:[__chg_by_fgfm_msg]set sock timeout:900......Communication hardeningFortiManager allows you to customize the level of security and the encryption algorithms used to securely communicate with managed FortiGate devices.FortiManager allows you to limit the cipher suites used by the device to prevent the possibility of a crypto downgrade attack such as that found in the Logjam vulnerability or other protocol downgrade attacks.In the FortiManager CLI,you can change the supported cipher suites with the following command: config system globalset enc-algorithm{high|medium|low}endThe default value is high.The following cipher suites are used for each level:l LOW:EDH-RSA-DES-CDBC-SHA,DES-CBC-SHA,DES-CBC-MD5l MEDIUM:RC4-SHA,RC4-MD5,RC4-MDl HIGH:ECDHE-RSA-AES256-GCM-SHA384,DHE-RSA-AES256-GCM-SHA384,ECDHE-RSA-AES128-GCM-SHA256For the certificate used to encrypt communications,the FortiManager uses the BIOS certificate burned into the unit at time of manufacture in order to prevent tampering of the certificate.Protocol operation on FortiGateIn order to isolate management traffic on the FortiGate unit and to prevent decrypted traffic from being routed to an external device,all management traffic is routed through an isolated virtual domain on the FortiGate unit.This contains only a single tunnel network device,TUN.The fgfm daemon owns a file descriptor,FD,which is linked directly to TUN.These steps are transparent to the user,and occur to segregate management traffic from all other traffic that may be passing through the FortiGate unit.On the FortiGate unit,the fgfm daemon routes fgfm-encapsulated traffic from FortiManager through FD.Thesepackets are received by their respective local daemons via the TUN device and respond via the TUN device.Therefore, their responses are always received by the fgfm daemon over FD and sent over the SSL connection to the FortiManager unit.Protocol operation on FortiGateSecurity concernsUsing the old IPSec tunneling method,packets can be routed anywhere by a FortiGate unit after decryption,which is a potential security issue.The fgfm protocol performs tunneling/detunneling exclusively in the fgfm daemon,sending packets to the FortiGate’s TUN device and no other network devices.Packets are unable to leak out of the FortiGate and incoming data is dropped if it cannot be delivered to daemons via the local stack.Protocol operation on FortiManagerMuch like how a TUN device is created on the FortiGate side of the connection,the FortiManager unit also creates a similar TUN device.This device is configured to have the same IP address as the physical interface through which the FortiManager communicates with the FortiGate unit.The FortiManager will have a daemon receiving fgfm messages and upon reception of a message compares theFortiGate’s declared IP address to the actual remote IP address to determine if the FortiGate unit is behind a NAT device.A routing table is maintained for TUN such that traffic destined for any FortiGate behind NAT will be routed through theTUN based on each FortiGate’s unique serial number and IP address.The the fgfm daemon running on theFortiManager assigns unique internal-use IP addresses to each FortiGate behind NAT so that it can distinguish between each unit and route traffic to the appropriate device via SSL.Initially,the FortiGate’s virtual TUN device has no IP address.If the FortiManager detects that the FortiGate is behind NAT,it allocates a unique internal IP address and notifies the FortiGate of this address.Command line output of FortiManager tunnelingRegardless whether or not the FortiGate unit is behind NAT,the FortiManager always sends management traffic via the secure tunnel.The FortiGate unit assigns the address provided by the FortiManager to its TUN device so that traffic sent to the FortiManager appears to have come from that address.Conversely,the FortiManager sends any traffic destined for the FortiGate to the same address,routing it over the FortiManager’s TUN device via SSL back to the FortiGate.Topology scenariosThe fgfm protocol supports four basic scenarios:l FortiManager on a routable public IP address/FortiGate behind NATl FortiManager is behind NAT/FortiGate on routable public IP addressl Both units have routable public IP addressesl Mixed topologyScenario1:FortiGate has public IP address,FortiManager is behind NATIn this scenario,the FortiManager administrator must configure the FortiGate’s IP address of hostname during the Add Device operation.Once complete,the FortiManager will initiate a connection to the FortiGate to performauthentication.Once authentication is successful,the FortiGate is immediately registered on the FortiManager and the unit can begin management functions on the FortiGate.Scenario2:FortiManager on a routable public IP address/FortiGate behind NATIn this scenario,the FortiGate administrator must configure the IP address(or hostname)of the FortiManager on the FortiGate or via a virtual IP address mapped to the FortiGate unit.After this is configured,the FortiGate willautomatically attempt to connect to the FortiManager because it is directly routable.Once the connection is active, authentication will be attempted and if successful,the FortiGate and FortiManager can begin communication.After this occurs,the FortiGate will show up on the FortiManager as an unregistered device.Once the FortiManager administrator registers the FortiGate,the FortiManager can begin performing management functions.Scenario3:Both FortiManager and FortiGate have public IP addressesIn this scenario,the FortiManager administrator can use either method indicated in scenarios1or2to complete device registration.Scenario4:Mixed topologyIn this scenario,a FortiManager may be on a private network and is able to manage FortiGate units with publicly available IP addresses.It will also be able to manage FortiGate units located on its own private network.For FortiGate units residing behind NAT on another network,the FortiManager will be able to manage them once properly configured as described in the previous scenarios.Scenario5:Both devices behind NATIn this case,the FortiManager and FortiGates are on different private networks.In order to configure the devices to allow management traffic to pass between them,a Virtual IP must be set up and configured on one side.FGFM built-in recoveryWhen a connection between a managed FortiGate unit and a FortiManager is broken,the protocol has a built-in failsafe recovery.Making changes to the FortiGate management IP addressOccasionally a FortiGate device will need to make a change to its IP address.If the IP address change allows the FortiGate to recreate its path to the FortiManager unit,functionality will remain unchanged.However,if that change breaks connectivity,after15minutes the FortiGate unit will revert to its last known good configuration in an attempt to restore connectivity.The15minute timer is hardcoded and cannot be configured or disabled.FGFM recovery logicFor each install:l The FortiManager sends the following to the FortiGate:l a listing of the set commands needed to apply the configurations changesl a listing of the unset commands that would revert the configuration changesl The FortiGate uses the following logic when applying changes:l apply the set commands,using memory only,nothing written to a configuration filel test the fgfm connection to the FortiManagerl if the connection goes down,it applies the unset commandsl retest the fgfm connectionl if connection remains down,the FortiGate unit reboots to recover the previous configuration from its config file The final step above is optional and can be enabled and disabled via the CLI using the following command: config system dmset rollback-allow-reboot{enable|disable}endFGFM built-in recovery17 ExampleThe following scenario is an example of an installation configuration from a FortiManager400E unit to a FortiGate60E device that tries to change the FortiGate’s management IP(WAN1)and causes the fgfm connection to break down.The original configuration on the FortiGate:config system interfaceedit“wan1”set vdom“root”set ip192.168.48.81255.255.255.0set allowaccess ping https ssh snmp http telnet fgfmset type physicalnextendIf you were to change the FortiGate WAN1interface's IP address to192.168.49.81/24and then attempt to install the configuration change,the fgfm connection would break.To enable the following viewing,you must log in to the FortiGate CLI with the administrativeaccount and enter the following debug commands:#diagnose debug enable#diagnose debug cli8You will see the following log on the FortiGate CLI during install:0:get sys status0:get system mgmt-csum0:config system interface0:edit“wan1”0:set ip192.168.49.81255.255.255.00:next0:endThe configuration change will break the fgfm connection,causing the FortiGate unit to attempt to reconnect for900seconds.If the FortiGate cannot reconnect,it will rollback to its previous configuration.You will see the following log when the FortiGate performs the rollback:0:config system interface0:edit“wan1”0:set ip192.168.48.81255.255.255.00:next0:end0:config system interface0:edit“modem”-23:unset type0:next0:end0:config system central-management0:endCopyright©2019Fortinet,Inc.All rights reserved.Fortinet®,FortiGate®,FortiCare®and FortiGuard®,and certain other marks are registered trademarks of Fortinet,Inc.,in the U.S.and other jurisdictions,and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet.All other product or company names may be trademarks of their respective owners.Performance and other metrics contained herein were attained in internal lab tests under ideal conditions,and actual performance and other results may work variables,different network environments and other conditions may affect performance results.Nothing herein represents any binding commitment by Fortinet,and Fortinet disclaims all warranties,whether express or implied,except to the extent Fortinet enters a binding written contract,signed by Fortinet’s General Counsel,with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and,in suchevent,only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet.For absolute clarity,any such warranty will be。

NoticeGrounding InstructionsIn the event of a malfunction or breakdown, grounding provides a path of least resistance for electrical current to reduce the risk of electric shock. This tool is equipped with an electrical cord having an equipment grounding conductor and a grounding plug. The plug must be plugged into a matching outlet that is properly installed and grounded in accordance with all local codes and ordinances.Step 1: Hardware Installation GuideStep 2: Software Installation GuideContentsSectionPageWARNING: To Ensure Safe Use4 - 51. Installation Environment62. Included Items73. Hardware Install8 3.1 Mounting Bracket 9 3.2 Slide Sensor 10 3.3 Connection3.4 Connection Status 11 125. Software Install13 - 206. Club Sticker Guide21 - 2728To Ensure Safe UseImproper handling or operation of this machine may result in injury or damage to property. Points which must be observed to prevent injury or damage are described as follows.WARNING Used for instructions intended to alert the user to therisk of severe injury should the unit be usedimproperly.Used for instructions intended to alert the user to the Cautionrisk of injury or material damage should the unit beused improperly. Material damage refers to damageto home, furnishing, or anything within the unit’svicinity.NEVER This symbol alerts the user to items that should neverbe carried out.To Ensure Safe Use - ContinuedInstall in a level and stable location. Failure to do so may result in falling of the machine, leading to injury.Never attempt to disassemble, repair, or modifyshock, or injury. Entrust repairs to a trained technician.Never use outside or in any location where exposure to water or high humidity may occur. Do not touch the power cord or electrical outlet with wet or dirty hands.Doing so may result in electrical shock.Conduct play in a clean and brightly lit location. Operating in a dark or cluttered space may lead toaccidents.Be aware of your surroundings and use cautiously with children around. Swinging the club during playwithout being aware will result in serious injury or death.WARNINGThis is a heavy machine.Installation EnvironmentPC Specifications:Category RequirementCPU Intel i5 8400 or higher*RAM8 GBGraphics Card GeForceGTX 1060 or higherOperating System Windows 10 (64bit) Version 1803 or higher Resolution1920 x 1080Connectivity Ethernet Port Required* AMD: 3rd gen Ryzen or higher and AMD Ryzen 3600 or higher (AMD 2700 is not compatible).Installation Environment 9’-Included ItemsThe following items are included with the sensor. Make sure they are all present and accounted for.EYEXO2 Sensor BarBracketEmail – Software InstallerCalibration ChartPower CablePower Adapter Power Connector USB Ethernet AdapterEthernet LAN CableLevelClub StickersM4 32mm screwsM6 15mm screws M6 15mm high screws M6 15mm low screwsIncluded ItemsHardware InstallWARNINGSection 1 “Installation Requirements,” and outlinebracket location on ceiling.Consult with building manager or landlord aboutbefore installation. The sensor and bracket are approximately 30 lbs and 9 M4 32mm screws are required to screw in the bracket and hold the sensor. Failure to do so may result in serious injury or damage toproperty.CAUTIONTwo or more persons are recommended for mounting the bracket on the ceiling and extreme caution is required while on the ladder. Failure may result in serious injury ordamage to property.LadderPhillips Screwdriver M4 32mmScrew x9 BracketSensor BarNecessary ToolNecessary Part(s)HardwareWARNINGStep 1: Mount BracketThe EYE XO2 Sensor and bracket come attached together in the box. Slightly loosen the black M6 15 mm screws that are holding the sensor to the bracket so you can remove it. Please make sure you have measured 3.5 feet from the front and middle of the sensor to your tee position. Do NOT align to the bracket.Place the ladder under the location on the ceiling where the bracket will be mounted. Place the bracket flat against the ceiling with the hinges facing down toward the ground. The longer side of the hinges must be closet towards theimpact screen.With the bracket in position, grab the 10 silver M4 32mm screws and screw them in the locations below in the diagram.M9 32mm (5)M9 32mm (5)132HardwareStep 2: Slide SensorAfter the bracket has been firmly mounted to the ceiling, you will install the sensorbar.The sensor bar comes with 6 black M6 15mm screws already inserted; 3 screws in the front and 3 screws in the back. Make sure all 6 screws are about halfway into the bar and even in length.Slide the sensor bar with the 6 screws up and over through the bracket hinges. Make sure the screws are secured in the hook part of the hinges. Once the sensor is secured in the bracket hinges, tighten the 6 screws to the bracket.The tilt of the sensor can be adjusted with the high and low M6 15mm screws. The regular M6 15mm screws are already screwed into the sensor. You can change this outwith the M6 155 High or Low screws to adjust the angle/ tilt.M6 15mmM6 Low 15mmM6 High 15mm Hardware3123.3Hardware Install - Continued Step 3: ConnectionEthernet LANCable Power Cord Power AdapterPowerConnectorNecessary PartsTake out the Ethernet LANcable from the box. Connectthe end with the tag that reads“Connect this side of LAN cableto Sensor ONLY” to the sensor.Connect the other endDIRECTLY to your PC ethernetport and NOT the USB adapter.Take out all 3 components ofthe power source: powercable, power adapter, andpower connector. Connect all3 accordingly and connect the“Power Connector” enddirectly to the sensor asshown below. Turn on redswitch.Note: The plug must be plugged into a matching outlet that is properly installed andgrounded in accordance with all local codes and ordinances.An extra green grounding wire is provided on the end of the power connector in caseyour outlet is not grounded.Hardware 12EYE XO2 INSTALLATION GUIDE113.4Hardware Install – ContinuedStep 4: Connection StatusMake sure to check the connection status before you start thesoftware installation process.Check and see if the power is on. You will see a bright red light on the switch of the sensor.Check and see if your EYE XO2 Sensor and PC are paired through the network.Hardware12Please refer to our “Network Setup Guide” below to set the IPaddress.NETWORK GUIDEEYE XO2 INSTALLATION GUIDE12Software Install WARNINGPlease make sure PC requirements are met from section1 “Installation Environment,” before the installationprocess. Failure to do will result in installation issues and slow gameplay .WARNINGPlease make sure the connection statuses are clear and everything is paired. Failure to do will result in installation issues.SoftwareSoftware Install – Continued EYE XO2 InstallationYou will receive an email with a license codefrom your retailer which looks like this:Please download it and save it to the UneekorFolderClick here: EYE XO2 Installer LinkCtrl + Click the EYE XO2 Installer link above to begin EYE XO2 Installation or manually enter the URL: https:///dist/EYEXO2/Uneekor_EYEXO2_Setup.exeUnder downloads you will see,“Uneekor_EYEXO2_Setup.exe” Clickopen file.“Uneekor EYE XO2 (2.10.0.0)Setup” will open. Click “Next.” Software23 41EYEXO2_30000XXXXX.license.3.5 Software Install – ContinuedEYE XO2 Software InstallationKeep the destination folder as“C:\Uneekor” and click Install.Please wait while installercompletes installation.5 6Software3.6 Software Install – ContinuedEYE XO2 Software Installation**If these two pop-ups occur, please hit ok for both.The “Run Uneekor EYE XO2” is checked. Uncheck it and click finish .7Software3.7 S oftware Install - ContinuedEYE XO2 Sensor ActivationGo to the C: Drive-> Uneekor Folder -> Device -> Launch Monitor -> EYEXOFind and double click “EYEXO2_Check”In the “EYEXO” folder click on “EYEXO2_Activation”Click “Browse” to find the license key saved from step 1 above.Then click “Activation” After adding the license please click “Activate.”The EYE XO2 Sensor installation is now complete.2If you don’t get the Sensor LAN connection, please refer to our “Network Settings Guide.”Make sure the Sensor LAN connection is good before the software installation process.1EYEXO2_40000XXXXX.licenseSoftware3.8 Software Install - ContinuedEYE XO2 Network Config1Once the sensor has been activated,you will have a screen like the oneon the right. Click Set NetworkParam & Firewall to continue2After the selection, you will be askedto restart the PC. Click Yes to restartto finish the Sensor installation3.8 Software installation - ContinuedEYE XO2 CalibrationTo complete the installation of the EYE XO2.Follow the calibration guide linked below:EYE XO2 Calibration Guide3.9Software Install – ContinuedVIEW Software InstallationClick here: VIEW Installer Ctrl + click on the VIEW Installer above or enter the URL manually: https:///dist/View/VIEW_Setup.exeOpen downloads on the right.If you receive this warning, follow the steps below.3.8.1Hover over the download,click the 3 dots on the rightside, and click keep.3.8.2Click the “Show more” dropdown and click “Keep anyway.”3.8.3Then click “Open file” underdownloads.“VIEW_SETUP 20220721 Setup” will open. Click “Next.”Software125.6 Software Install – ContinuedVIEW Software InstallationKeep the Destination Folder as “C:\VIEW” and click “Install.”Check the “I agree” box and click “Install.”If a error pops up, click close and continue to VIEW Setup.Click “Start setup”34SoftwareIf the C++ files are already installedon your PC, you may receivethe error on the rightClick Close and then nextto continueOptional :5.7 Software Install – ContinuedVIEW Software InstallationMake sure all boxes are checked and the Directory matches the picture on the right, then Click “Next.”Click “Finish”Click “browse” and select the license file you saved in the Uneekor folder from the earlier steps, and click “Activation. Then click “Activate” VIEW Software installation isnow complete.567SoftwareThe speed of the club before impact.The amount of energy transferred from the club head to the golf ball.The angle difference between Face Angle and Club Path.angle is measured relative to the horizon.The in to out or out to in movement of the club head’s geometric center atthe time of impact. Club Path is the directon (right or left) the club head ismoving at impact and is measured relative to the target line.The direction (right or left) the club face is pointed at impact. It ismeasured relative to the target line.GUIDE22The amount of loft of the club face at the center point of impact.Where you strike the ball on the club face.FPOFPO2-2.4 inches13Driver 48 groove1. Bar StickerAlign the middle of the Bar Sticker to the horizontal center line or the 7th groove.2. Dot StickerAlign to the middle of the bar sticker andparallel between the grooves.15 61Center Groove*In the case where you do have to raise the horizontal line beyond the center to fit all 4 corners of the Bar Sticker, the data will be calculated higher.262277.1 SpecificationsEYE XO2 INSTALLATION GUIDE 28Items Contents Components 3 High Speed Cameras 4Infrared LED Boards1 Control Board1 Power BoardData Interface Ethernet (CAT6 and above) Communication Speed 1 GbpsSpin Data Total Spin ±12,000 rpmMeasurement Range Ball Speed Putter: 0.1 m/s ~ 30 m/s Ball Speed Driver/Iron: 5 m/s ~ 100 m/sSensing Angle Driver: -5 ~ 50 DegreeIron: 0.1 ~ 80 Degree (shots over 60° can damage the unit)***************** *******************。

Accidental full scan proliferation by a build server farm..................................................................... 25 Solution......................................................................................................................................25
3. Troubleshooting scanning issues........................................................25
Accidental full scan proliferation by folder paths which include build or commit ID............................ 25 Solution......................................................................................................................................25
Contents
Contents
Preface....................................................................................................5
1. Scanning best practices......................................................................... 8