Capinfo_Support_Tasks_v1_draft1.doc

658 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
658
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Capinfo_Support_Tasks_v1_draft1.doc

  1. 1. C O M M E R C I A L I N C O N F I D E N C E     Capinfo Support Tasks Detailed Documentation Issue 1, Draft 1 Page 1 of 28
  2. 2. C O M M E R C I A L I N C O N F I D E N C E Change Control Owner Mike Brockington Issue and Date Issue 1, Draft 1, 21/07/2003 Identity Capinfo Support Tasks - Detailed Documentation Location of electronic copy / mnt/temp/unoconv/20150129135449/capinfosupporttasksv1 draft1doc1443.doc Location of paper copy CEC Program Office Change Authority Neil Ferguson Distribution Syntegra (CEC Program) I&E Service Team, Delivery Team Issue Author Date Details of Change 1, Draft 1 Mike Brockington 21/07/2003 Initial version for circulation and comment. Syntegra Guidion House Harvest Crescent Ancells Park Fleet Hampshire GU51 2QP Tel: (01252) 777000 Fax: (01252) 777111 CEC Programme Office Telephone House 357 Gorgie Road Edinburgh EH11 2RP Page 2 of 28
  3. 3. C O M M E R C I A L I N C O N F I D E N C E Table of Contents 1. INTRODUCTION................................................................................................................................4 1.1. OBJECTIVES AND SCOPE.................................................................................................................4 2. BACKUPS.............................................................................................................................................5 2.1. ARCSERVE SETUP...........................................................................................................................5 3. SERVER MANAGEMENT................................................................................................................7 3.1. WEEKLY PUBLISH / INDEX.............................................................................................................7 3.2. WEEKLY SITE INDEX......................................................................................................................9 3.3. FTP SITE ACCESS.........................................................................................................................10 3.4. ‘SUPPORT FOLDER’.......................................................................................................................11 3.5. BRANDING....................................................................................................................................11 4. DATABASES......................................................................................................................................14 4.1. MYSQL........................................................................................................................................14 4.2. MICROSOFT ACCESS ‘97...............................................................................................................14 4.3. MICROSOFT SQL SERVER 2000 – DEVELOPERS EDITION............................................................14 4.4. SPECIAL CASES.............................................................................................................................14 4.4.1. A_to_Z.mdb – A to Z of Council Services............................................................................14 4.4.2. MembersData.mdb / Councillor.mdb –Councillor Details..................................................15 4.4.3. Councillor Details Database ..............................................................................................16 4.4.4. Recreation.mdb – Database of Recreational Sites...............................................................16 5. WEB APPLICATIONS.....................................................................................................................17 5.1. MANAGEMENT PAGES..................................................................................................................17 5.1.1. Committee Minutes..............................................................................................................17 5.1.2. Planning Weekly List / Decisions List..................................................................................19 5.2. HOME PAGE MANAGEMENT SYSTEM...........................................................................................21 5.2.1. News Flashes........................................................................................................................22 5.2.2. Features Boxes.....................................................................................................................22 5.2.3. Quick Links..........................................................................................................................22 5.2.4. Take Live..............................................................................................................................22 5.3. PARTIAL PUBLISH.........................................................................................................................22 6. LOG FILES........................................................................................................................................25 6.1. APACHE SERVER – ACCESS LOG..................................................................................................25 6.2. APACHE SERVER – ERROR LOG....................................................................................................25 6.3. SERVLETEXEC – ERROR LOGS.....................................................................................................25 6.4. PUBLISH PROCESS – GENERAL LOG.............................................................................................25 6.5. PUBLISH PROCESS – TAKE-LIVE LOG...........................................................................................25 6.6. PUBLISH PROCESS – HTDIG LOGS..............................................................................................25 6.7. INTERNET INFORMATION SERVER – WEB LOGS...........................................................................26 6.8. INTERNET INFORMATION SERVER – FTP LOGS............................................................................26 6.9. INTERNET INFORMATION SERVER – URLSCAN LOG...................................................................26 6.10. PARTIAL PUBLISH LOGS.............................................................................................................26 7. GLOSSARY........................................................................................................................................27 Page 3 of 28
  4. 4. C O M M E R C I A L I N C O N F I D E N C E 1. Introduction 1.1. Objectives and Scope The purpose of this document is to provide detailed instructions on completing normal operational support tasks relating to the Capinfo Web service. This will involve the machines known as AVANTI, Elton_John, Freddy, Omnicity_Server and CAPINFORW (ftp_relay). Detailed information regarding the configuration of these servers is provided individually, in the same location as this document. The first four servers are housed in the same rack unit at Chesser House. This rack also houses Web_Neo_Srv_1, which is not included in this documentation. CAPINFORW is a stand-alone machine in the North-East corner of the computer hall. This document's intended audience is the administrators of the Capinfo systems and all members of the service team. Page 4 of 28
  5. 5. C O M M E R C I A L I N C O N F I D E N C E 2. Backups 2.1. ArcServe Setup The two Proliant 1600’s1 are backed up to a common DLT-4 tape. This operation is carried out on Elton_John, using ArcServeIT 6.61 Advanced Edition. Every day a ‘DB Pruning’ job runs at 17:30. This is a system maintenance job, and should not need to be modified. This is timed to complete before any of the backup jobs start. Duration is usually in the order of 2 minutes. Weekday backups of Omnicity_server are carried out to four labelled tapes, at 20:00. Essentially all four drives on omnicity_server are backed up, plus the system state. The duration of this process is typically 20 hours. On Fridays both servers are backed up to a rotating set of four tapes. These backups start at 22:00 since there is more time available2 than during the week. This also helps to differentiate the Friday Jobs in the scheduler. Both drives on Elton_John, and all four drives on omnicity_server are backed up, plus the system state. The duration of this process is approximately 21 hours. The status of the backup jobs can be checked by using VNC to connect to 192.168.19.25 and then selecting: Start > Programs > ArcServerIT for Windows NT > ArcserveIT Manager Then choose the ‘Job Status’ button. This should reveal the screen shown below: Note the DB Pruning Job, marked 1 in white above, which should always show a ‘Last Result’ of ‘Finished’. Due to open files etc, the actual back-up jobs often show a ‘Last Result’ of ‘Incomplete’ as shown at 3, unlike those at 2 which have been entirely successful. A ‘Last Result’of ‘Failed’ (which will be accompanied by a red symbol) indicates a 1 Elton_John and Omnicity_Server 2 No backup is run on a Saturday / Sunday, so over-run is not an issue, unlike weekdays. Page 5 of 28
  6. 6. C O M M E R C I A L I N C O N F I D E N C E major issue which needs to be investigated. It does not necessarily mean that the entire backup is useless, since there may well have been some files backed up. If the job does not have a status of ‘Ready’ as shown at 4, then that shows that the job has been put on hold, presumably by another administrator. If any of the three green lights at 5 (top right) are showing red, then one of the services is stopped. The backups will not work unless all three services are running. To obtain more detailed information about problems, click on the ‘Activity Log’ 6 tab. This gives a detailed log of the operations carried out, accompanied by the same Blue, Yellow and Red icons seen at 2 & 3 above. Page 6 of 28
  7. 7. C O M M E R C I A L I N C O N F I D E N C E 3. Server Management 3.1. Weekly Publish / Index Every week a process is run on Omnicity_Server to synchronise the live content with the stored content/database. This is a relatively simple process to run, although this hides a rather complex and time-consuming combination of components. Note that because the majority of these components have some hard-coded drives / directory paths, it is not possible to run the publish process through a mapped drive from any other machine, so VNC must be used to get the proper context. The publish is normally only run once the Planning Weekly List has been uploaded. If however this is expected to be more than one day late then the publish is run regardless, and then repeated once the Planning Weekly List has been uploaded. If there is a Public Holiday on the Monday then the publish is postponed until Tuesday, which is also true of the Planning Weekly List. The publish is started by accessing omnicity_server via a VNC session, then opening emacs3 from the top of the Start Menu. Type <Alt>X shell<return> to open a command shell within emacs. This text will automatically appear in the ‘mini-buffer’ which is the small text area at the bottom of the screen, labelled 1 below . Note that the <Alt> character is displayed as a capital M followed by a hyphen. Then type go<return> in the area marked 2 above4 , to change to the ‘normal’ working folder: D:CapdmPublish If the file go.bat is missing then it will be necessary to do this manually by typing D: <return> followed by CD CapdmPublish <return> Depending on the circumstances the site index is sometimes run as a separate process, and sometimes combined directly with the publish. The latter is accomplished by typing webandindex<return> 3 If emacs is still open, then pressing <CTRL><up-arrow> repeatedly cycles through the previous commands. This significantly reduces the process described here. 4 The text shown here will now have been replaced with the default command prompt intro text, and the text focus will also have shifted, so that text will now appear in this main buffer window. Page 7 of 28
  8. 8. C O M M E R C I A L I N C O N F I D E N C E The former is accomplished by typing web<return> then index<return> once the publish is complete. All three of these processes are DOS batch files, used to amalgamate different processes: 1. Prior to the actual publish, a minor process is run to prepare the A-Z of Council Services content. This is held in C:cecA_to_ZA_to_z.mdb and is prepared by running Publish.exe which is held in the same folder. 2. Buildweb.pl is a PERL program which is in turn mainly a wrapper for a Java program; Publish.java. 3. D:capdmpublishwebmapmap.bat is created dynamically by BuildWeb.pl, and is the final stage of the take-live process. This copies the published files to the live Apache directories on both omnicity_server and Elton_John, simultaneously. 4. D:capdmpublishScheduled_jobsrunQuickLinks.bat runs a Java program which does a quick analysis of the Apache access log files, to provide a ‘top-ten’ list for the ‘Quick-Links’ section of the Capinfo home page. 5. D:capdmpublishsendFinalEmail.bat triggers a simple Java program whose sole job is to send out a confirmatory email message to several interested parties5 . This program is dependant on the SMTP sendMail process running on Freddy (192.168.19.24 port 25) 6. c:optwwwhtdigbinhtdig carries out a site index. 7. c:optwwwhtdigbinhtmerge does some house-keeping on the files generated by the site index. These are taken live manually, as documented below. 6 and 7 are controlled by C:optwwwhtdigconfweb.conf To aid problem solving, the output from the above processes appears in the following files:  F:ftpWeb_Publishresults.list – messages from BuildWeb.pl / Publish.Java / runQuickLinks.bat / sendFinalEmail.bat  F:ftpWeb_Publishtake_live-XXX_XX_XX.list – any errors reported by map.bat These are usually caused by ‘partial publishes’ carried out since the last full system publish, which have therefore changed the content. Note that this file is datestamped, which means that it is duplicated every week, and must be deleted by hand, when space requires. Since these are on the F: drive, there will be little impact if space does run out, but this should be avoided. The size of these files varies significantly. If, for example, a change is made to one of the site templates then this affects a large number of files, which inflates this file correspondingly. These files are the only way of recording what has been published, so should not be deleted until necessary.  F:ftpmikebrockingtonhtdig_output.list – results from the site index; the size of this file is dependant on the number of –v flags used in webindex.bat. –v gives minimal detail, while –vvvvv gives extremely verbose output, and significantly slows down the indexing process.  F:ftpmikebrockingtonhtmerge_output.list – errors and warnings from the database cleanup process. 5 Email Addresses = "sally.kerr@edinburgh.gov.uk", "mike.brockington@edinburgh.gov.uk", "ana.dragic@edinburgh.gov.uk", "Alison.Davies@edinburgh.gov.uk" Page 8 of 28
  9. 9. C O M M E R C I A L I N C O N F I D E N C E 3.2. Weekly Site Index An indexing process is run once a week, after the publish, to create a set of databases for use by many of the site search facilities6 . These then need to be checked and taken live as follows: 1. Within VNC7 , open the folder C:optwwwhtdigdbweb: There will be four files in there with a ‘.work’ extension, but otherwise the same name as the previous weeks file. Compare the file sizes, and ensure that they are reasonably consistent. Obviously changes in content will lead to small increases or decreases week-by-week, but these should not normally be greater than about 1%. 2. Double-click takelive.bat, 1 which will take about one second to run. This renames all of the existing files to filename.ext.old, then renames the new files by removing the .work extension. 3. Open a browser window and go to the Capinfo home page (http://www.edinburgh.gov.uk/) Enter an appropriate search term into the search box and check that there are a sensible number of results. I usually use the word ‘road’. By sticking to the same phrase you can immediately spot if the results change substantially, indicating a problem. Follow one of the links to ensure that the link has been written correctly. 4. Carry out step 3, but using a ‘restricted’ search8 , such as A-Z of Council Services. 5. When satisfied, go back to the folder C:optwwwhtdigdbweb and double-click remove_old.bat 2 This deletes the old copies of the indexes. 6. If there is a problem with the index, double-click on restore_live.bat This reverses the process of takelive.bat, renaming the new files to filename.ext.work and removing the .old extension from the old files. Note that the first time that the search is run with new indexes it takes slightly longer than normal, as there is some initialisation to be done. Subsequent searches will then be at normal speed, and therefore this testing of the databases has a dual role. 6 There are also a number of custom searches, which are dependant on IDC’s or JSP, not ht://dig. 7 This cannot be done with a mapped drive, (unless the batch files are duplicated and modified), since they rely on the drives/paths on the server, which will conflict with those on the remote workstation. 8 Some searches use the ‘Restrict’ parameter to tell ht://dig to only return results that match a certain pattern for their location, eg ‘/a2z/PAGES’ restricts results to only the A-Z of Council Services. Page 9 of 28
  10. 10. C O M M E R C I A L I N C O N F I D E N C E The ht://dig suite is dependant on portions of the Cygwin package. Specifically the file Cygwin1.dll must be present, in the correct version and location: The full Cygwin package will be needed if attempting to compile the suite from source. This has been attempted in the past, without success, which is why we are still using version 3.1.5, this being the most recent Windows binary available. Ht://dig has an active support mailing list, plus a fairly useful set of documentation at http://www.htdig.org For many problems it will be worth using the mail archives, since the documentation rarely gives examples of complicated usage, and therefore is not very good at explaining the finer points of the configuration. Most of the mail archives are taken up with problems in compiling the package, but concrete examples of usage can be found with care. 3.3. FTP Site Access A number of mini-sites on Capinfo are maintained independently by Council staff. This requires FTP access to be set up on the users’ machine, pointed at 192.9.240.133 This is a Windows NT Server, running on a Compaq EP in the computer room at Chesser House. IIS 4 was installed from the Option Pack, and the www publishing service was disabled. Like the PC’s belonging to the Capinfo support team, this machine has explicit access through the firewall to the DMZ. This allows shares on Omnicity_Server, or any of the other machines to be mapped, and used as the root of various FTP virtual Page 10 of 28
  11. 11. C O M M E R C I A L I N C O N F I D E N C E directories. This effectively relays the FTP access into the server, without actually running FTP within the DMZ. FTP access is limited to specific IP addresses by IIS security, which requires that the users’ machine be made static within DHCP. Current virtual directories/sites are:  ftp://192.9.240.133/Licensing - linked to htdocs/licensing  ftp://192.9.240.133/Licensing - linked to htdocs/licensing 3.4. ‘Support Folder’ Several important sections of Capinfo have backup copies stored at D:Capdmsupportwebhtml… The files in these folders are automatically copied into D:apachehtdocs… as part of the ‘take live’ process of the publish routine. This means that changes made to the live files will be overwritten without warning unless the backup copies are also updated. Normal practise is to modify the live file, check with the user, and only then overwrite the ‘Support’ copy, which then acts as a useful backup. These files are mainly static content, such as re-directs, using the same directory structure as the Publish, and extra pieces, such as form handling pages, which were developed separately to the associated ERL. 3.5. Branding The Capinfo system differentiates between different sections of the site by the use of ‘Branding’. This mostly involves a common template, with different colours and logos applied, but in some cases involves a completely separate template, such as the Libraries pages. To update the details: 1. Use VNC to access Omnicity_Server. Double-click on ‘Shortcut to myAdmin.exe’ on the desktop. This will launch a graphical front-end to the MySQL databases. 2. A window similar to the following should appear: Click on the word ‘localhost’, then on the ‘connect’ icon (labelled 2), then the icon at 3 should change to show ‘connected’. 3. The window should now look like: Click on the ‘plus’ sign next to the ‘capdm’ database symbol. Page 11 of 28
  12. 12. C O M M E R C I A L I N C O N F I D E N C E This will expand the view to display all tables: 4. The main features of this window are the drop down box 4, which allows you to re-select previous queries, the ‘execute’ button 5, which runs the query currently displayed in the query editing area 6. The results of a query will be displayed in the area beneath this section of the window. At the very bottom, on the left side, is the ‘status bar’ which is used to indicate that a query is running, has failed due to a syntax error, or the number of results returned. 5. Type the following string into the query editing area 6: SELECT * FROM brands then press the ‘execute button’ 5. 6. This will return all entries in the brands table. To change the colour of a brand: 1. Identify the correct brand from the list, and note the ID. 2. Type the following string into the query editing area 6: update brands set lighttint = concat(left(colour, 1), "ffCCcc") where id=7 Ensure that the colour code is set appropriately, and that the id is the one noted in step 2. 3. Now type: update brands set colour = concat(left(lighttint, 1), "ff3333") where id=7 Again ensuring that the colour and ID are correct. 4. The name of the brand can be changed by typing: update brands set name = “[New Name]” where id=7 5. Note that the lighttint, darktint and image fields are not currently used, but may be re-used in the future, and may still be referenced by the management system. In addition to changing these database entries it will be necessary to ‘register’ any new brands with the Management Pages: 1. Identify the correct brand from the MySQL table as described above, and note the ID. 2. Open D:Apachehtdocsmanageerls.php3 in a text editor. 3. Find “print trLabelData(“ (currently line 47) 4. Duplicate one of the existing lines immediately below, and edit the details appropriately. The number quoted is the ID noted in step 1. Page 12 of 28
  13. 13. C O M M E R C I A L I N C O N F I D E N C E 5. Note that the last line of this group MUST not have a comma at its end, while all preceding lines MUST be terminated with a comma. 6. Save and close the file. 7. Any existing ERLs that are to use the new branding must be changed over, either with the management system, or by update queries run directly on the database. Page 13 of 28
  14. 14. C O M M E R C I A L I N C O N F I D E N C E 4. Databases There are three different kinds of database currently in use by Capinfo. 4.1. MySQL These are primarily used in connection with managing the site content. They record files uploaded, authenticate user access etc. All tables are held within C:mysqldatacapdm The largest of these is now over 50MB in size. 4.2. Microsoft Access ‘97 These are the primary storage solution for dynamic content on the site. There are a number of variations in use, documented below. The majority of Access databases are held within C:ci2kdb These are all then linked9 through either ci2k.mdb or others.mdb to provide a consistant interface. This was a required part of the operation of the systems when the Touch-Screens were in operation, but also keeps the set-up simple. These databases are documented by two copies of DB_Notes.txt, one in each folder, which should be annotated with any relevant changes as the first priority. 4.3. Microsoft SQL Server 2000 – Developers Edition SQL Server is currently being used to replace the existing MS-Access’97 databases on Capinfo, with the data transferring to AVANTI. Further details can be found in the build document for that server. Database structures are not being changed as part of this migration, but syntactic differences between the two systems inevitably result in code changes for JSP and IDC pages. Of particular note is that it appears that the JDBC/ODBC bridge requires that fields be accessed in the order that they are returned by the query. Where an attempt is made to access a field that is ‘to the left of’ a field that has already been accessed the attempt fails silently, returning a NULL value. This means that IDC pages in particular may display blank fields even though data is present. 4.4. Special Cases 4.4.1. A_to_Z.mdb – A to Z of Council Services This is held in C:cecA_to_ZA_to_Z.mdb along with publish.exe The latter is a small Visual Basic 6 program, which is used simply to initiate a routine within A_to_Z.mdb. This program does not do any work itself, but allows the VBA code within A_to_Z.mdb to be triggered from the same DOS batch file that later starts the system publish. Assuming that the form named frmRun is always used as the start point, there will never be a need to change this application. 9 To refresh these links, open MS-Access, open Ci2k.mdb or others.mdb, open the ‘File’ Menu > Get External Data > Link Tables then choose the appropriate database / tables. If the tables chosen already exist in this database, then Access will append a digit to the end of the name, e.g. table1 Page 14 of 28
  15. 15. C O M M E R C I A L I N C O N F I D E N C E There are 27 ERL’s registered on Capinfo for the A-Z system: This is one for each letter of the alphabet, plus one index/entry page. When the system is published, the database code attempts10 to work out which is the most recent file to be uploaded to these ERL’s, then overwrites them with a new XML file for the index, and 26 HTML files as appropriate. The XML file contains links only to those sub-ERL’s that actually contain content – typically one or two will not. There are approximately 700 database entries at present, which are written out so that each entry appears, in alphabetical order, on the correct page. The same process also writes out a series of HTML pages to D:ApachehtdocsSearchA2ZPAGES<Letter>page<id>.html, a series of 26 HTML menu pages to D:ApachehtdocsSearchA2Zlist_<Letter>.html, and a single HTML menu page to D:ApachehtdocsSearchA2Zlist.html This then gives a three level hierarchy, which allows Ht://dig to index individual records, while ignoring the rest of the content, which tends to obscure the data within the ‘composite’ pages produced through the management system. These pages are set up so that Ht://dig does not record these menu pages, so that they are not visible to the public. For this reason only the individual records are ‘properly’ formatted for screen. All links within these pages lead back to the ERL-based long format version of the A- Z, which is easier to browse. These individual record pages do not pass through the normal Publish procedure, unlike the long-format pages. 4.4.2. MembersData.mdb / Councillor.mdb –Councillor Details This is held in C:Ci2kdb, but is just a copy of one held by Frances Lynch locally. Updates consist of Frances emailing her copy to us, which is then renamed from MembersData.mdb to Councillor.mdb. This happens infrequently, usually only when an election, or bye-election, has recently occurred. There is also a complimentary database on Frances’ computer, called Members.mdb. This does not hold any data, but does hold all of the interface code and forms to update the database. If these databases are moved11 it may be neccesary to re-associate them. This is done by opening Members.mdb, opening the Tables tab, and deleting all tables. Then go to File > Get External Data > Link Tables and select MembersData.mdb, ensuring that all tables are imported. 10 This is NOT done by using the MySQL databases. Instead the ERL paths are hard-coded into the database, which reads the filenames, sorting them in such a way as to pick the most recent based on the timestamp that forms the filename. 11 For example, if the code is changed to include a new field, or new report. Page 15 of 28
  16. 16. C O M M E R C I A L I N C O N F I D E N C E NB: This database is not linked with any of the ‘Elections’ databases / systems. 4.4.3. Councillor Details Database This is now held in SQL Server as ‘Councillors’. This is updated through a dedicated management system under Apps on OMNICITY. 4.4.4. Recreation.mdb – Database of Recreational Sites This is another database that is resident on the machine of one of the members of Sally Kerr’s team at CIS. The database contains details of Museums, Halls, Parks and Libraries amongst others. The details can then be saved to XML menu files, and individual HTML data files, which are then uploaded to standard ERL’s by the user. A preview facility is provided that applies an (outdated) copy of the site template so that the user can check the HTML data files before they are uploaded. Since these files go through the normal publish process there is no need to modify the database when changes are made to the standard site template, although changes to the XML menus may require synchronisation. Page 16 of 28
  17. 17. C O M M E R C I A L I N C O N F I D E N C E 5. Web Applications 5.1. Management Pages These are the primary method of adding/editing/deleting content from the site. They are used by users with a wide range of abilities, and can be accessed from http://www.edinburgh.gov.uk/manage/manage.php3 5.1.1. Committee Minutes There are special mechanisms in place to handle Committee Minutes, and a few other sections of the site. This is known as the ‘DateLink’ mechanism. It allows the user to upload multiple documents to the same ERL, and, by identifying them by date, the system will generate list of hyperlinks, sorted by date, to each copy. This is in contrast to the normal upload mechanism, which replaces existing content whenever a new file is uploaded. This mechanism is dependant on the user filling in the date field correctly when uploading the file. Note the ‘Date Stamp’ field in the upload screen (shown below). The format for this field must be 07/11/2003 Note that leading zeroes are required, as is a four-digit year. If this field is entered incorrectly, or not at all, or if the wrong file is uploaded, it will be necessary to delete the file from the management system. (If this happens with a ‘normal’ ERL it is only necessary for the user to upload a new file, thus overwriting the error, which should not require the intervention of support staff.) 8. Fully identify the file in question. If a publish has occurred, write down the name of the file that has been generated, eg FB210303_doc.html In this example the original file name would have been FB210303.doc indicating a file that refers to the Fire Board of 21/03/2003. 9. Use VNC to access Omnicity_Server. Double-click on ‘Shortcut to myAdmin.exe’ on the desktop. This will launch a graphical front-end to the MySQL databases. Page 17 of 28
  18. 18. C O M M E R C I A L I N C O N F I D E N C E 10. A window similar to the following should appear: Click on the word ‘localhost’, then on the ‘connect’ icon (labelled 2), then the icon at 3 should change to show ‘connected’. 11. The window should now look like: Click on the ‘plus’ sign next to the ‘capdm’ database symbol. This will expand the view to display all tables: 12. The main features of this window are the drop down box 4, which allows you to re-select previous queries, the ‘execute’ button 5, which runs the query currently displayed in the query editing area 6. The results of a query will be displayed in the area beneath this section of the window. At the very bottom, on the left side, is the ‘status bar’ which is used to indicate that a query is running, has failed due to a syntax error, or the number of results returned. 13. Type the following string into the query editing area 6: SELECT * FROM erls WHERE erl LIKE ‘%fire board%’ Modify the ‘%fire board%’ portion to reflect the ERL that you need to find, then press the ‘execute button’ 5. 14. In this example four rows were returned. Note the value shown in the ‘id’ column for the ERL that you need to work with. In this case it was 337. 15. Now type the following string into the query editing area 6: SELECT * FROM files WHERE erlid = 337 AND TYPE=”raw” ORDER BY id desc Page 18 of 28
  19. 19. C O M M E R C I A L I N C O N F I D E N C E Enter the id just noted, in place of ‘337’, then press the ‘execute button’ 5. Note that myAdmin highlights the syntax of the SQL statements that are entered, so will often give feedback on potential syntax errors before the query is run. The ‘ORDER BY’ clause ensures that the most recently uploaded files appear at the top of the results. The ‘TYPE=”raw”’ clause restricts the results. Without this clause, 2795 rows would have been returned. This includes one row for every Word’97 file that has been uploaded, plus one for each of the HTML files that were generated. This will vary according to the complexity of the document, but will typically be between a dozen and one hundred. 16. Drag the bar that divides the results area from the query area upwards slightly. This will automatically adjust the width of the results columns so that they all fit onto the screen. 17. The ‘Uploadtag’ field is a time-stamped filename, of the form ‘f yyyy mm dd hh mm ss’ and obviously this should match the date/time that the user uploaded the file incorrectly. The ‘origfilename’ field should have an entry that matches the filename that was recorded in step 1 above. If these two fields do not agree then you should double check with the user, as it can be hard to re-instate a minute if you delete the wrong one. 18. Take note of the ‘uploadtag’, and note the year, month and day portion. 19. Enter the following query: SELECT * FROM files WHERE erlid = 337 AND uploadtag like "%f20030711%" 20. Check that the results only includes one file of type ‘raw’ and one of type ‘tar’. If not you will need to refine the query above to include: ‘AND id < 123456 AND id > 345678’ or similar. 21. When you are satisfied that you have selected only one ‘set’ of files, change the query from ‘SELECT * FROM…’ to ‘DELETE FROM…’ Note that the * is now superfluous. This will permanently delete all record of these files from the system. This cannot sensibly be restored from backup tape, since many other records in the database will likely have changed since the backup. Note also that this merely removes the entries from the database, it does not remove the physical files, which are located in the folder D:capdmdb Beyond space considerations, which are minor, there is no need to also remove the physical files. 5.1.2. Planning Weekly List / Decisions List These two sections of the web site also use the ‘DateLink’ mechanism. This allows the user to upload successive documents to the same ERL, and, by identifying them by date, the system will then generate a list of hyperlinks, sorted by date. This is in contrast to the normal upload mechanism, which replaces existing content whenever a new file is uploaded. This mechanism is dependant on the user filling in the date field correctly when uploading the file. Note the ‘Date Stamp’ field in the upload screen: Page 19 of 28
  20. 20. C O M M E R C I A L I N C O N F I D E N C E The format for this field must be 07/11/2003 Note that leading zeroes are required, as is a four-digit year. The content of the Planning Weekly List and the Planning Decisions List are emailed to the Internet and eMail Team on a weekly basis, usually on Mondays, unless there is a Public Holiday. The process is as follows: 1. Save the two attachments to your local hard disc. 2. Open both files. Check that the format is correct12 and ascertain which one is the Applications list and which is the Decisions List: file naming is done manually, and is therefore not always consistant. 3. Open http://www.edinburgh.gov.uk/manage/manage.php3 4. Login in as Admin:cryptag 5. Click on ‘ERLs’ (item 1 below) 6. Enter the word ‘weekly’ into the ERL search box, 2 above. 7. Click ‘Find’ 3 or hit <return> 12 Capinfo uses a different format from the printed version, which is produced at the same time. The printed version orients the tables vertically, while the Capinfo template has repeated horizontal tables. Page 20 of 28
  21. 21. C O M M E R C I A L I N C O N F I D E N C E 8. This will bring up a list of containing a few results, currently four: 9. Ensure that item 4 is listed, and click on the corresponding ‘Upload’ button, 5. 10. This will display the upload form shown above. Ensure that today’s date (or Monday’s date if this is later in the week,) is entered into the ‘DateStamp’ field, in the format dd/mm/yyyy, with leading zeroes where applicable. 11. Click the ‘Browse…’ button and select the Applications list that you saved to disc in step 1. 12. Click ‘Upload Main File Now…’ 13. When the upload is complete, click on the ERL field at the bottom, and move to the end. Delete the last word ‘ List’ and the word ‘Weekly ‘ then hit <return> or press ‘Find’. This should return a list similar to the one above, but probably with only one entry13 , as below: 14. Click the ‘Upload’ button and follow steps 10 to 12 above. 15. Choose the ‘Logout’ link to end the session. 5.2. Home Page Management System The Capinfo Home Page consists of several independent sections, which are handled under the umbrella of the Home Page Management System. This in turn is accessed from within the Partial Publish system. Access is limited to certain hard-coded users. Those users who are not authorised will not be shown the ‘Home Page’ link at the right hand end of the menu bar, (marked 6 below:) 13 This is dependant on system usage. If a new ERL is defined or deleted, then the list will change. Page 21 of 28
  22. 22. C O M M E R C I A L I N C O N F I D E N C E 5.2.1. News Flashes This section predates the remainder of this system, and is therefore held separately, at: http://www.edinburgh.gov.uk/apps/newsflash though links to it are provided from the main menu page. 5.2.2. Features Boxes To be completed. 5.2.3. Quick Links To be completed. 5.2.4. Take Live To be completed. 5.3. Partial Publish In addition to the regular weekly publish, it is possible for users to publish sections of the site on demand. This is done by accessing http://www.edinburgh.gov.uk/partial which is an alias to htdocs/apps/partial/ Once the user has logged in using their management system password14 , they are presented with the screen below: Link 1: ‘Publish an ERL’ brings the user back to this point from anywhere within the system. Entering any text into the search box, 7 above, and then pressing ‘Find’ or hitting <return> then attempts to match the text against all current ERLs, returning a page similar to this: 14 As with many similar systems, the ‘Admin’ password is not valid – a ‘user’ login must be used. Page 22 of 28
  23. 23. C O M M E R C I A L I N C O N F I D E N C E The user may then choose an ERL from the list, or carry out another search. Options are given to ignore links to other ERL’s, (default), or to also publish linked documents. Changing this option may significantly increase the load on the server, and the time taken to complete the publish. The option to ignore Committee Minutes etc. is a further extension of this idea, so that if the first option is changed, the three largest parts of the publish are ignored, even if links to them are found. Clicking on the appropriate ‘Publish’ button will return a page similar to: Page 23 of 28
  24. 24. C O M M E R C I A L I N C O N F I D E N C E The results page is designed to start returning data immediately, so if the publish is large, the ‘Finished’ message 3 may not appear for some time. The single entry shown at location 2 is normally a long list of all ERLs visited, and may include some warning messages, if the option to publish linked ERLs was set. The reference to ‘BACKUP SERVER’ at location 4 is a hangover from a previous configuration of the two Proliant 1600’s, which then had different configurations for the Partial Publish. The final stage is to click on ‘Take Files Live’, which will reveal a page similar to: Click on any of the filename hyperlinks, (underlined, in blue) to open a copy of the file in a preview window. Click on a box such as that at 5 above to select all files in that folder. Click on any of the boxes at 6 to select/deselect individual files. Once the selection has been finalised, click the ‘Take Files Live’ button to copy the files from the holding area15 onto the live system. 15 D:Apachehtdocspartialtemp username Page 24 of 28
  25. 25. C O M M E R C I A L I N C O N F I D E N C E 6. Log Files There are numerous log files kept on the system, produced by the various processes, applications and web applications: 6.1. Apache server – Access Log Location: E:logs Size: < 500MB Changed: Semi-automatically, using rotate.bat, every month Apache often fails to relinquish its lock on the log files, even when repeatedly stopped and started. In this case it is necessary to reboot the entire computer. 6.2. Apache server – Error Log Location: E:logs Size: < 500MB Changed: Semi-automatically, using rotate.bat, every month As with the Access log, it is necessary to stop Apache when dealing with this file. 6.3. ServletExec – Error Logs Locations: C:Program FilesUnifyServletExec ASse-omnicity_serverServletExec.log C:Program FilesUnifyServletExec ASse-protected_serverServletExec.log Size: < 500KB Changed: Automatically, whenever the file is full, or whenever the Servlet is restarted. Previous copies are renamed as ServletExec.log.1 … ServletExec.log.9, where .9 is the oldest copy. 6.4. Publish Process – General Log Location: F:ftpNew_Publishresults.list Size: < 500MB Changed: Automatically overwritten, every week 6.5. Publish Process – Take-Live Log Location: F:/FTP/Web_Publish/takeLive-<timestamp>.list Size: 100KB < 1.5MB Changed: Automatic timestamp, every week. Periodic manual removal required. 6.6. Publish Process – HTDIG Logs Location: F:ftpNew_Publishhtdightdig_output.list Size: < 50MB Page 25 of 28
  26. 26. C O M M E R C I A L I N C O N F I D E N C E F:ftpNew_Publishhtdightmerge_output.list Size: < 5MB Changed: Automatically overwritten, every week 6.7. Internet Information Server – Web Logs Locations: E:logsIIShttpdownloads E:logsIIShttpSocialWorkCatalogue Size: < 10MB Changed: Automatically, every month 6.8. Internet Information Server – FTP Logs Locations: E:logsIISftpdefault E:logsIISftpdownloads E:logsIISftpLectures Size: < 1MB Changed: Automatically, every month 6.9. Internet Information Server – URLScan Log Location: E:logsurlscan Size: < 10KB Changed: Automatically, every day Logs potential exploits against IIS – these request were not passed to IIS itself. Typically these are the result of viruses such as Nimda. 6.10. Partial Publish Logs Location: D:Apachehtdocsappspartialpartial.log Size: c. 1 MB per month Changed: Manually Page 26 of 28
  27. 27. C O M M E R C I A L I N C O N F I D E N C E 7. Glossary AIS Artificial Intelligence Solutions ltd., developers of the Capinfo publishing routines. AVANTI Capinfo CEC’s public facing web site. CEC The City of Edinburgh Council. CIS The Community Information Service. Based in the Central Library, they are responsible for updating Capinfo menus, and are the main council contacts for the system as a whole. DMZ De-Militarised Zone – a portion of the Council network segregated from both the Internet and from the internal network. Security for this zone is as tight as possible, but cannot be considered as secure as the internal network, therefore traffic in any direction is subject to filtering. ERL Enterprise Resource Locator – similar in concept to a URL, this is a unique identifier on the Capinfo system. Where the ERL refers to a MS-Word’97 document it refers to a single document. Where an HTML document is used, there may be a significant number of ‘support’ documents, such as other HTML pages, stylesheets or image files. IDC Internet Database Connector – obsolete Microsoft technology. Simplified by AIS for use with Capinfo, it provides a simple, template-based method for combining database content with HTML to create dynamic web pages. It is similar in concept to ASP or JSP. ASP Active Server Pages – Microsoft’s proprietary database connection software; replaced the less powerful IDC JSP Java Server Pages – Sun’s Java based solution to integrating database content with web pages; far more powerful than IDC, but correspondingly more complex. VNC Virtual Network Computing – open source equivalent to MS Terminal Services or PCAnywhere, allows remote control of a computer over a TCP-IP network. YABB Yet Another Bulletin Board – open source bulletin board. XML Extensible Markup Language – special language, similar in appearance to HTML, used to manage the menus on Capinfo. Page 27 of 28
  28. 28. C O M M E R C I A L I N C O N F I D E N C E This document is the copyright property of British Telecommunications plc and shall not be published or disclosed to any other party without prior written permission being granted by British Telecommunications plc. The document shall be held in safe custody and used only for the purposes of the contract. All rights reserved. No part of this document may be reproduced or transmitted in any form or means, including photocopying and recording, without the prior written permission of British Telecommunications plc. Such permission must also be obtained before any part of this document is stored in a retrieval system of any nature. Overseas offices in Africa, the Americas, Australasia, the Middle East, the Far East and Europe. ©British Telecommunications plc 2001 Registered office: 81 Newgate Street, London, EC1A 7AJ Registered in England No. 1800000. Printed in England. Page 28 of 28

×