Configuring NEOSYS Generally

Clearing files in database (done when you want to clean an old database)

This is to be done incase you want to clean an old database or clean a training database so that a client can enter fresh data. These commands DO NOT clear down the whole database and hence for new installations you need to download a fresh BACKUP.ZIP file from the NEOSYS website.

Clear data F5 CLEAROP (only clears transactions not reference files)

Clear suppliers F5 CLEARFILE SUPPLIERS

Clear Vehicles F5 CLEARFILE VEHICLES

Flush Index F5 FLUSH.INDEX

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

Configuring backup procedures

See the System Configuration File on the NEOSYS Support Menu.

Non-Liability for Backup

If a NEOSYS client has not signed the standard NEOSYS contract which excludes liability then NEOSYS needs a specific agreement to the following:

Dear xxxxxxxx, 

NEOSYS has offered to setup a nightly backup of your NEOSYS data. 

We can only do this on condition that you will not hold NEOSYS liable for damages of any kind in the case that our backup procedure fails to 

meet its essential purpose in an emergency. 

You may make your own alternate parallel arrangements to ensure that the whole of the contents of the NEOSYS server are backed up sometime 

between 3am and 6am at night when NEOSYS system is shutdown. 

Please confirm your agreement. 

Best Regards, 
xxxx xxxx 
NEOSYS

Backing up the Images folder

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.

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:

line 12 - and specify the Drive of the location to be backed up to. eg. E or F

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 the 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)

Enabling backup servers to access backed-up servers

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

1. Asks you for the username and hostname
2. Copies an identity file from the backup server to the backed up server.
   This requires you to enter the administrator or root password.
3. Logs you in to the backed up server's cygwin/bash command line.
   This requires you to enter the password again.
4. YOU then type a series of commands to install the identity file and finally exit the command console.
   The series of commands that you must type are shown on screen by autologin.sh
5. Logs you in to the backed up server's cygwin/bash command line.
   This time, you should NOT be required to enter a password.
6. 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

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.

Press Ctrl+X to exit the editor