曝光臺 注意防騙 網(wǎng)曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

property rights are granted by the delivery of this document or the disclosure of its content. This document shall not be reproduced or disclosed to a third party without the express written
consent of AIRBUS S.A.S. This document and its content shall not be used for any purpose other than that for which it is supplied
Replace the data directory in your installation directory with the one you’ve backed up before. If you’ve chose to run Flight Ops Doc Manager with HSQLDB, do the same with the hsql_files one.
If you’ve chosen a different DB engine than HSQLDB, please have a look to its documentation in order to perform a database restore.
You can restart Flight Ops Doc Manager server from the service monitor.
4.1.4.2.3
Backup/restore process
The following diagram sums up the process: FOSP Server Frequent backupFOSP ServerFiles and data corruption Files File and database restore directories Data and HsqldbFile Hsqldb UsersconnexionsUsersconnexionsUsersconnectionsUsersconnectionsFrequent backupDirectories:
Figure 7: Backup/Restore process
4.1.5
Monitoring of the application
All the operations performed by the application are logged into several files. There are several kinds of log:
􀂾
Client logs: those logs report events that occur on the client application. In case of a standalone mode those files store the whole event that may occur on the software. Those logs are located in c:\document and settings\Application Data\Airbus\Log\fosp.
􀂾
Server logs: those logs report events that occur on the server side. Those logs are located in your <Flight Ops Doc Manager install dir>\Log.
Within these directories, the logs are divided into two categories:
􀂾
Log: they are located in the fosp-log.txt file. It stores every event which is of info or error level. This file is displayed in the Flight Ops Doc Manager HMI under the console tab. It does not give a detailed description of each event.
􀂾
Trace: they are located in the fosp-trace.txt file
« Flight Ops Doc
Manager »
Administration Guide
Reference: UG0601141
Issue: 7.1
PAGE 16/32
© AIRBUS S.A.S 2009. All rights reserved. Confidential and proprietary document. This document and all information contained herein is the sole property of AIRBUS S.A.S. No intellectual
property rights are granted by the delivery of this document or the disclosure of its content. This document shall not be reproduced or disclosed to a third party without the express written
consent of AIRBUS S.A.S. This document and its content shall not be used for any purpose other than that for which it is supplied
Note that Flight Ops Doc Manager logs are stored into rolling files of 1024kb.
On the Flight Ops Doc Manager, the Console tab (a tool of Manual Explorer) allows to see the logs of fosp-log.txt (click on refresh button to refresh this console tab).
4.2
Business Administration tasks
Business administration tasks are detailed in the User Guide [RD4]. The administration tasks correspond to all functionalities accessible to the Root user:
􀂾
Activate / De-activate user
􀂾
Cancel Check out on a document unit, it’s also manual explorer action.
« Flight Ops Doc
Manager »
Administration Guide
Reference: UG0601141
Issue: 7.1
PAGE 17/32
© AIRBUS S.A.S 2009. All rights reserved. Confidential and proprietary document. This document and all information contained herein is the sole property of AIRBUS S.A.S. No intellectual
property rights are granted by the delivery of this document or the disclosure of its content. This document shall not be reproduced or disclosed to a third party without the express written
consent of AIRBUS S.A.S. This document and its content shall not be used for any purpose other than that for which it is supplied
5.
TROUBLESHOOTING PROCEDURES (FAQ)
5.1
Installation troubleshooting procedures
Symptom
Cause
Solution
The following error message is displayed: ”InstallerException … IOException: jarsigner.exe …”
The path environment variable is not correctly set
Delete the installation dir, update the environment variable with JAVA_HOME/bin and restart the installation process
See annexe 5.3.5 Flight Ops Doc Manager server error client JWS cannot load
Installer crashes during file process
Database engine wrongly configured, or not started
Verify the settings entered in database panel
Installer didn’t finished its process
Error during installation process
Clean the installation:
Run INSTALL_DIR/bin/Uninstaller/ UninstallFlight Ops Doc Manager.jar
Delete INSTALL_DIR
Delete APACHEROOT/htdocs/fosp directory
　
中國航空網(wǎng) m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：“Flight Ops Doc Manager”Administration Guide(6)