Configuring NEOSYS Generally: Difference between revisions

From NEOSYS Technical Support Wiki
Jump to navigationJump to search
No edit summary
 
(27 intermediate revisions by 8 users not shown)
Line 1: Line 1:
== Clearing files in database ==
==System Configuration File==
 
See [http://userwiki.neosys.com/index.php/System_Configuration_File System Configuration File]
 
==Clearing files in database==


This is to be done if you want to clean an old database or clean a training database so that a client can enter fresh data.
This is to be done if you want to clean an old database or clean a training database so that a client can enter fresh data.
Line 5: Line 9:
These commands DO NOT reset the data to "factory settings" so for new installations you need to download a fresh BACKUP.ZIP file from the NEOSYS website.
These commands DO NOT reset the data to "factory settings" so for new installations you need to download a fresh BACKUP.ZIP file from the NEOSYS website.


*Clear transactions F5 CLEAROP (only clears transactions not reference files)
*Clear transactions F5 - CLEAROP (only clears transactions not reference files)


*Clear all F5 CLEARALL (rather nasty command because it clears all reference files as well)
*Clear all F5 - CLEARALL (rather nasty command because it clears all reference files as well)


== Clearing selected files in database ==
*Clear finance transactions F5 - CLEARACC


This can be done if you want to reimport selected files. The flush index command MUST be performed after doing any clearing.
REINDEXALL SHOULD be done after CLEAROP or CLEARACC in order to reduce the size of the index files to reflect the reduction in size of data, by rebuilding them from scratch, since index files don't reduce in size automatically when the data is cleared or reduced.
 
==Clearing selected files in database==
 
This can be done if you want to reimport selected files.


WARNING This procedure must not be used if there are any transaction in the system that might use the files being cleared.
WARNING This procedure must not be used if there are any transaction in the system that might use the files being cleared.
Line 19: Line 27:
WARNING The opportunity to create problems that have no solution and that may only surface when the system is in operation is endless unless you think through the implications very very very carefully.
WARNING The opportunity to create problems that have no solution and that may only surface when the system is in operation is endless unless you think through the implications very very very carefully.


*Flush Index F5 FLUSH.INDEX (this command MUST be performed immediately after any data clearing)
*Flush Index F5 FLUSH.INDEX (this command MUST be performed immediately after any data clearing, because CLEARFILE does not clear the related indexes immediately and it will be done later on access, causing random stopping later on)


*Clear suppliers F5 CLEARFILE SUPPLIERS
*Clear suppliers F5 CLEARFILE SUPPLIERS
Line 25: Line 33:
*Clear vehicles F5 CLEARFILE VEHICLES
*Clear vehicles F5 CLEARFILE VEHICLES


*Clear Payment Instruction F5    CLEARFIELD CLIENTS PAYMENT_INSTRUCTIONS (only clears the payment instruction from the client and brand file)
If a particular field needs to be cleared from a file then get the exact field name defined in the file.
 
To list the various fields in a file  F5 LD CLIENTS  (for Client and Brand file)
 
*Clear Payment Instruction from Client and Brand file F5    CLEARFIELD CLIENTS PAYMENT_INSTRUCTIONS (only clears the payment instruction defined in all the Client & Brand file)


== Configuring backup procedures ==
*Clear Agency fee % from Client & Brand file F5 CLEARFIELD CLIENTS FEE (only clears the agency fee defined for all Client & Brand flies)


See the System Configuration File on the NEOSYS Support Menu. More explanation is at [[Configuring_NEOSYS_automated_backup]]
==Mass updating database without data entry==


=== Non-Liability for Backup ===
Warning: It is advisable that you take the approval of NEOSYS DBA or programmers before doing any of the following procedures. There is no protection whatsoever from damaging the database if you do not appreciate all the implications of any particular update. Common sense and caution must be used. If you damage a database then it may be, or with operation become, irretrievably damaged and require reconstruction from a backup causing possibly extreme finance damages to the owner of the data and consequences for yourself. You have been warned.


{{Non-Liability For Backup}}
There are many commands in maintenance mode that allow you to amend the database directly and without any record and without any ability to reverse changes.


=== Backing up the Images folder ===
Normally, no record of the changes is made. All changes will appear to have been done by the last user at the time and date of the last normal user interface amendments.


The Images folder under the NEOSYS installation is used to upload images/artworks/files from the Job File section and hence needs to be backed up. NEOSYS will automatically backup this Images folder to the USB drive or other location (specified for the usual data backup) once a week. To configure this backup, RSYNC needs to have been installed during the initial installation.
===Available fields to clear or set===


In case we need to configure the Images folder backup at another location other than the usual daily backup location than we need to edit:
#Client & Brand File: CLIENTS MARKET_CODE
#Client & Brand File: BRANDS MARKET_CODE


line 12 - and specify the Drive of the location to be backed up to. eg. E or F
===How to clear a database field===


== Backup to other media (i.e. not to USB)==
Assuming that a particular database field may be blank (i.e. not required for data entry) then you may clear a field as follows.


If the backup is going to '''non-removable media''' (even if it is a shared folder on another computer) then the NEOSYS user/client/licensee (NOT the NEOSYS support team) can, at their own responsibility, arrange to '''move''' (NOT COPY) the NEOSYS backup files from that location to a backup location of their choice and avoid the WARNING message : "Backup media not changed. Overwriting last weeks backup"
Warning: There is nothing to stop you clearing a field that is mandatory and doing this may cause irrecoverable damage to the database.


=== Sample alternative response to client requests for additional backups ===
In the following example we wish to change all clients with market code “UAE to have market code blank.
 
First, if you don’t want to clear all records, “select” the required records.
 
SELECT CLIENTS WITH MARKET_CODE “UAE”
 
After a period of time, depending on the number of records in the file, it should briefly state the number of records selected and then return to the command prompt.
 
WARNING: If no records have been selected then ALL records will be updated by the following command!
 
CLEARFIELD CLIENTS MARKET_CODE
 
===How to set a database field===
 
In the following example we change all the clients where the market code is blank (has not been entered) to become “UAE”.
 
Warning: You can set the market code to a market code that does not exist. This will cause various problems in the operation of the system but is probably not irrecoverable.
 
First, if you don’t want to set all records, “select” the required records.
 
SELECT CLIENTS WITH MARKET_CODE “”
 
After a period of time, depending on the number of records in the file, it should briefly state the number of records selected and then return to the command prompt.
 
WARNING: If no records have been selected then ALL records will be updated by the following command!
CLEARFIELD CLIENTS MARKET_CODE/UAE


The existing NEOSYS backup must continue to take place for safety because it is the only well understood standard, controlled and checked procedure in use for all NEOSYS clients.
==Backup to other media (i.e. not to USB)==


You are free to setup and operate any additional backup procedure you like but NEOSYS cannot take any responsibility in setting up, monitoring or approving your additional backup procedure because it is beyond our sphere of control, expertise and trust.
[[Backup and Restore#Backup to other media (i.e. not to USB)|Backup to other media]]


What you can backup is the NEOSYS backups on the USB drive. These are readily available online at all times on the NEOSYS server for you to access and copy as you choose.
==Reordering databases in maintenance mode==


You can backup the usb anytime using anything you like, but you must not backup anything on any hard disk eg: C or D at any time.
#Open NEOSYS in maintenance mode
#General > Backup & data management > Reorder databases
#Press the Enter key to select/deselect the databases in the required order.
#Press F9 once and confirm that the databases are in the required order, if not go back to Step 3.
#Press F9 again and select Yes to save the reordered list.


== Copying a single record from one database to another ==
==Copying a single record from one database to another==
   
   
You need to know the file name and record key of the record to be copied.
You need to know the file name and record key of the record to be copied.
Line 79: Line 122:
The (N) option means only copy if the target already exists. It is advisable to use it when you know that the target already exists to avoid misspellings in the command. It must be omitted if the target doesnt exist.
The (N) option means only copy if the target already exists. It is advisable to use it when you know that the target already exists to avoid misspellings in the command. It must be omitted if the target doesnt exist.


== Allowing users temporary login as NEOSYS in maintenance mode ==
==Allowing users temporary login as NEOSYS in maintenance mode==
   
   
#Get them to login with any name even NEOSYS
#Get them to login with any name even NEOSYS
#Get the to enter "?" for the pass without the quotes
#Get them to enter "?" for the pass without the quotes
#NEOSYS will give them a lock like "NEOSYS 123456" which they must give you. You should not log out until the next step is completed
#NEOSYS will give them a lock like "NEOSYS 123456" which they must give you. You should not log out until the next step is completed
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
#Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name
(to allow access EXCEPT access to authorisation screen use a special number (not documented here) as the last number of the initial command)
(to allow access EXCEPT access to authorisation screen use a special number (not documented here) as the last number of the initial command)
#Give them the key and get them to enter and proceed
#Give them the key and get them to enter and proceed


== Configuring upload of photoshop "cs2" jpg files ==
==Configuring upload of photoshop "cs2" jpg files==


Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.
Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.
Line 106: Line 151:
#Restart IIS (Right click, All Tasks, Restart)
#Restart IIS (Right click, All Tasks, Restart)


== Enabling backup servers to access backed-up servers ==
==Configuring next Media Booking Order No.==
 
This relates to a common procedure used by NEOSYS to provide automatic nightly synchronisation/backups between servers for multi-office configurations. For more information see
http://itwiki.neosys.com/index.php/Setting_up_remote_backup
 
Αccording to this procedure, backup processes are actually initiated and run on a "backup server" using a "pull" concept. The "backed-up server" serves the data (usually using an rsync service) to the backup server on request. They do not use a "push" concept.
 
This means that backup servers need to be able to automatically login to the backed-up servers. On most backup servers a NEOSYS cygwin script called autologin.sh has been installed. This helps you configure the backup server and backed-up server.
 
Normally you only need to run autologin.sh once per pair of backup and backed-up servers but sometimes the configuration is lost (particularly when NEOSYS is upgraded) and it must be repeated.
 
=== Using autologin.sh ===
 
#Asks you for the username and hostname
#Copies an identity file from the backup server to the backed up server.<br><b>This requires you to enter the administrator or root password.</b>
#Logs you in to the backed up server's cygwin/bash command line.<br><b>This requires you to enter the password again.</b>
#YOU then type a series of commands to install the identity file and finally exit the command console.<br>The series of commands that you must type are shown on screen by autologin.sh
#Logs you in to the backed up server's cygwin/bash command line.<br><b>This time, you should NOT be required to enter a password.</b>
#YOU type "exit" to quit the backed up server's command line.
 
=== Running ./autologin.sh ===
 
In cygwin on the backup server, type
 
./autologin.sh
 
... and follow instructions on screen. The system will ask you once the password to the target server to transfer an identity file and once again to access the command line of the target server from where you must follow a set of instructions in order to load the identity file properly.
 
The username is usually administrator for windows server targets.
 
The hostname can be found in backup email logs or in the CONFIG.CMD file in the backup server.
 
There are often two alternative hostnames. Try the first one first. If you succeed with the first then there is no need to try the second.
 
Sometimes one of the host names is based on alternative network access methods like hamachi which uses ip addresses starting with "5." and requires hamachi service to be running in both servers and this sometimes is dependent on being logged in and correct setup of hamachi. You can ping the host names to discover the ip numbers of course.
 
Follow the instructions on the screen VERY carefully.
 
=== The edit step ===
 
The last step will enter the nano editor where you should do the following:


If present, delete the word neosys near the end of the last line of the file. The last bit of the last line will refer to some user and host that you are enabling access FROM
It is not possible to edit the next booking order number, as done with other document sequences, within the Invoice Number screen.


BE CAREFUL NOT TO TRIGGER THE AUTOMATIC LINE BREAKING IN NANO because line breaking into two or more lines is automatically triggered when you add characters to long lines. it is not triggered if you just delete characters. If you do cause a line break then quit the editor WITHOUT saving and try again or then use the editor to rejoin the two lines. Note that pressing Alt+L will turn long line breaking off and on which avoids the problem in the first place.
The CURRENT booking order number is defined in the below definitions record.


Press Ctrl+X to exit the editor
EXO_DATA=<dbcode> edir definitions BOOKING_ORDERS.SK

Latest revision as of 08:20, 20 May 2022

System Configuration File

See System Configuration File

Clearing files in database

This is to be done if you want to clean an old database or clean a training database so that a client can enter fresh data.

These commands DO NOT reset the data to "factory settings" so for new installations you need to download a fresh BACKUP.ZIP file from the NEOSYS website.

  • Clear transactions F5 - CLEAROP (only clears transactions not reference files)
  • Clear all F5 - CLEARALL (rather nasty command because it clears all reference files as well)
  • Clear finance transactions F5 - CLEARACC

REINDEXALL SHOULD be done after CLEAROP or CLEARACC in order to reduce the size of the index files to reflect the reduction in size of data, by rebuilding them from scratch, since index files don't reduce in size automatically when the data is cleared or reduced.

Clearing selected files in database

This can be done if you want to reimport selected files.

WARNING This procedure must not be used if there are any transaction in the system that might use the files being cleared.

WARNING Clearing individual files is error prone because other files might refer to the records you are clearing (referential integrity is not applied so dangling references may be created). For example, clearing suppliers without clearing vehicles in advance results in vehicles which have supplier codes that do not exist. Even if you reimport the suppliers, some supplier codes in the vehicles file may not be reimported leaving vehicles with problems.

WARNING The opportunity to create problems that have no solution and that may only surface when the system is in operation is endless unless you think through the implications very very very carefully.

  • Flush Index F5 FLUSH.INDEX (this command MUST be performed immediately after any data clearing, because CLEARFILE does not clear the related indexes immediately and it will be done later on access, causing random stopping later on)
  • Clear suppliers F5 CLEARFILE SUPPLIERS
  • Clear vehicles F5 CLEARFILE VEHICLES

If a particular field needs to be cleared from a file then get the exact field name defined in the file.

To list the various fields in a file F5 LD CLIENTS (for Client and Brand file)

  • Clear Payment Instruction from Client and Brand file F5 CLEARFIELD CLIENTS PAYMENT_INSTRUCTIONS (only clears the payment instruction defined in all the Client & Brand file)
  • Clear Agency fee % from Client & Brand file F5 CLEARFIELD CLIENTS FEE (only clears the agency fee defined for all Client & Brand flies)

Mass updating database without data entry

Warning: It is advisable that you take the approval of NEOSYS DBA or programmers before doing any of the following procedures. There is no protection whatsoever from damaging the database if you do not appreciate all the implications of any particular update. Common sense and caution must be used. If you damage a database then it may be, or with operation become, irretrievably damaged and require reconstruction from a backup causing possibly extreme finance damages to the owner of the data and consequences for yourself. You have been warned.

There are many commands in maintenance mode that allow you to amend the database directly and without any record and without any ability to reverse changes.

Normally, no record of the changes is made. All changes will appear to have been done by the last user at the time and date of the last normal user interface amendments.

Available fields to clear or set

  1. Client & Brand File: CLIENTS MARKET_CODE
  2. Client & Brand File: BRANDS MARKET_CODE

How to clear a database field

Assuming that a particular database field may be blank (i.e. not required for data entry) then you may clear a field as follows.

Warning: There is nothing to stop you clearing a field that is mandatory and doing this may cause irrecoverable damage to the database.

In the following example we wish to change all clients with market code “UAE to have market code blank.

First, if you don’t want to clear all records, “select” the required records.

SELECT CLIENTS WITH MARKET_CODE “UAE”

After a period of time, depending on the number of records in the file, it should briefly state the number of records selected and then return to the command prompt.

WARNING: If no records have been selected then ALL records will be updated by the following command!

CLEARFIELD CLIENTS MARKET_CODE

How to set a database field

In the following example we change all the clients where the market code is blank (has not been entered) to become “UAE”.

Warning: You can set the market code to a market code that does not exist. This will cause various problems in the operation of the system but is probably not irrecoverable.

First, if you don’t want to set all records, “select” the required records.

SELECT CLIENTS WITH MARKET_CODE “”

After a period of time, depending on the number of records in the file, it should briefly state the number of records selected and then return to the command prompt.

WARNING: If no records have been selected then ALL records will be updated by the following command!

CLEARFIELD CLIENTS MARKET_CODE/UAE

Backup to other media (i.e. not to USB)

Backup to other media

Reordering databases in maintenance mode

  1. Open NEOSYS in maintenance mode
  2. General > Backup & data management > Reorder databases
  3. Press the Enter key to select/deselect the databases in the required order.
  4. Press F9 once and confirm that the databases are in the required order, if not go back to Step 3.
  5. Press F9 again and select Yes to save the reordered list.

Copying a single record from one database to another

You need to know the file name and record key of the record to be copied.

In this case the file is DEFINITIONS and the key is AGENCY.PARAMS

You can invent any old style 8.3 filename instead of C:\AGP.DAT in the following example

On the source computer:

F5
COPY DEFINITIONS AGENCY.PARAMS TO: (DOS C:\AGP.DAT)

On the target computer:

F5
COPY DOS C:\AGP.DAT (ON) TO: (DEFINITIONS AGENCY.PARAMS)

The (O) option is required to force overwrite of the existing

The (N) option means only copy if the target already exists. It is advisable to use it when you know that the target already exists to avoid misspellings in the command. It must be omitted if the target doesnt exist.

Allowing users temporary login as NEOSYS in maintenance mode

  1. Get them to login with any name even NEOSYS
  2. Get them to enter "?" for the pass without the quotes
  3. NEOSYS will give them a lock like "NEOSYS 123456" which they must give you. You should not log out until the next step is completed
  4. Follow the NEOSYS lock/key procedure using the full contents of the lock including the user name

(to allow access EXCEPT access to authorisation screen use a special number (not documented here) as the last number of the initial command)

  1. Give them the key and get them to enter and proceed

Configuring upload of photoshop "cs2" jpg files

Photoshop version "cs2" produces jpg files that cannot be viewed in Internet Explorer.

A solution is to rename the files extension from .jpg to .psjpg before uploading.

"psjpg" files are an invention of NEOSYS and IIS must be configured to handle .psjpg files as follows:

Windows Server 2003 (doesnt work on XP)

  1. Computer Management, Internet Information Server, Properties
  2. Click MIME Types
  3. Click New
  4. Extension: psjpg
  5. MIME Type: application/photoshop
  6. Click OK,OK,OK
  7. Restart IIS (Right click, All Tasks, Restart)

Configuring next Media Booking Order No.

It is not possible to edit the next booking order number, as done with other document sequences, within the Invoice Number screen.

The CURRENT booking order number is defined in the below definitions record.

EXO_DATA=<dbcode> edir definitions BOOKING_ORDERS.SK