SPEX for Windows Client Server Version 8.3. Pre-Requisite Document V th August 2006 SPEX CS 8.3

Transcription

1 SPEX for Windows Client Server Version 8.3 Pre-Requisite Document V th August 2006 Please read carefully and take note of the applicable pre-requisites contained within this document. It is important that these pre-requisites are met and confirmed to your Kewill Project Manager prior to any on site implementation. Any on site visit that is unsuccessful or aborted due to failure to meet these pre-requisites may result in the charge for the visit being made and further costs being applicable for any subsequent visits required as a result thereof. Page 1 of 15

2 Table of Contents 1. SPEX Hardware/Software Requirements (Application) Server / Stand Alone installations Client PC requirements Use of facility Using customs electronic messaging modules Further note regarding NES module (UK Customs) Further note regarding SAGITTA module (NL Customs) Further note regarding AES module (US Customs) Further note regarding CAED module (Canadian customs) SPEX Database Requirements AS/ Oracle Progress, SQL Server, DB SPEX XML Processor Sub-System & XML Interface Requirements Printers ERP Integration GEAC System/21 or Aurora JD Edwards IFS Interface SAP Interface ORACLE Applications Interface Other ERP Systems Appendix Internet Explorer details Digital Certificates requirements for NES users Cipher Strength Security Updates IBM iseries Information for AS/400 customers...15 Page 2 of 15

3 1. SPEX Hardware/Software Requirements (Application) 1.1. Server / Stand Alone installations If you plan to use the SPEX system on a server for clients to connect to or to install the SPEX application locally on individual PC s the requirements are as follows; Minimum : Processor: Pentium GHz or above Memory: 512 MB RAM or more Disk Space: 2 GB Free HD Space (the installation, excluding the database, requires 350 MB of space) Operating System: Windows 2000 Server SP4 or above, Windows 2003 Server or Windows XP Pro SP2 or above (for stand alone) Other: Suitable Network card / connection, Internet Explorer V6 or above (Please see note within appendix regarding Internet Explorer), suitable internet connection and software required if you plan to use distribution of docs via or any of the customs electronic messaging modules, Adobe Acrobat Reader for viewing PDF files. Note: that during the installation of the SPEX system the machine being installed onto may need to be rebooted in order to register software for use (as per standard Microsoft installations). This should be planned for regarding any servers that may be affected during implementation Client PC requirements The following hardware requirements exist for client installations of the SPEX software. Minimum : Processor: Pentium GHz or above Memory: 256 MB Ram or more Disk Space: 1 GB Free HD Space or more Operating System: Windows 2000 Pro SP4 or above, Windows XP Pro SP2 or above Other: Suitable Network card / connection, Internet Explorer V6 or above (Please see note within appendix regarding Internet Explorer), suitable internet connection and software required if you plan to use distribution of docs via or any of the customs electronic messaging modules, Adobe Acrobat Reader for viewing PDF files NOTE: Please note that the performance and speed of your network can have a dramatic impact on the performance of the SPEX system. In some circumstances whereby the network is slow or already has large amounts of network traffic it is best to install the application locally with network access for the database and printer(s) for SPEX. Page 3 of 15

4 1.3. Use of facility If you require the use of the SPEX auto distribution system for ing documents automatically then the SPEX machines will also need access to an appropriate system. We can support MAPI or SMTP based systems (Outlook/Exchange or Lotus Notes). Should you have any other system in place this will need to be tested and may/may not function as required. If you are using Outlook and intend to use MAPI as the basis of sending s from SPEX, you have a choice of using CDO (an extended MAPI function with Outlook). This is a setting within the SPEX configuration menu. To allow this functionality to work you must install CDO as an option within the Microsoft Office install program. CDO allows sending of s with attachments from Outlook for correct receipt by recipients who use Lotus Notes. Without the CDO option we have found that the delivery method for with attachments will cause the attachment to be part of the body. This of course does not work when the attachment is a PDF file. (This does not have any impact on Outlook based recipients). If you do not have CDO as an option available within your office version, you can still send s via the non CDO MAPI route but need to consider recipients with Lotus notes. If you use the SMTP route we have found no issues with attachments for s between Outlook/Exchange users and Lotus Notes Using customs electronic messaging modules If you plan to use any of the customs electronic messaging modules available with the SPEX product you will need to make sure that the machines hosting the SPEX software have appropriate internet connections Further note regarding NES module (UK Customs) If you are planning on using the NES module with SPEX you will need to use a digital certificate. Further information regarding this can be found within the appendix Further note regarding SAGITTA module (NL Customs) Before commencing installation, check that connection can be made to the Seagha site from the PC that will act as the bridge server. Test this by making a Telnet connection to (aka connect1.seagha.com 9162 ). If Telnet is unsuccessful, port 9162 must be opened for external communication (outgoing only) through the Firewall. Page 4 of 15

5 Further note regarding AES module (US Customs) You will need to have a functioning connection to the Internet. The AES Direct VPN Utility can be downloaded from the following link You will need to: Select the link About AESDirect VPN Select the link Click here to convert your AESDirect EDI to a two way VPN connection You will be asked to enter your AES Direct User Name and Password, then, on the following screen, your Admin code Follow the instructions on the screen to download EDIInstall.exe Run EDIInstall.exe Configure the AES Direct VPN Utility o Run AESVPNConfigtool.exe which will be located in the directory where the AES VPN Utility is installed o Create directories for download, upload, log files and back up o Enter the names of these directories in the corresponding boxes on the screen o Check the Logging and Backup check boxes o Enter OUT in the upload extension box ( the AES Direct files produced from SPEX have.out extension) o Enter the required polling interval in seconds o Press the Register button, enter your AES Direct user name, password and admin code and press OK o Press OK to exit from the AES VPN Configuration Further note regarding CAED module (Canadian customs) To use CAED you need to contact Statistique Canada via their Web Site Here you need to: Register with Statistique Canada to use CAED and obtain; o License Number o Authorization Id o Service Provider No o Download and install the CAED and DLM (Data Loading Module) software. You also need to note that the CAED software requires the AES validation tables to be downloaded and installed into the SPEX look up tables for CAED validation purposes. Page 5 of 15

6 2. SPEX Database Requirements The SPEX system can install the Tables/Files required onto the following database platforms; AS/400 Oracle RDBMS Progress SQL Server DB2 If you do not have a database listed above and have a SPEX license for 5 users or less, you may install and use the SPEX provided MSDE database/license. This is provided with the SPEX media for installation if required. Please note the following pre-requisites for using database platforms specified above; 2.1. AS/400 If you plan to store the SPEX database on the AS/400 then the following pre-requisites apply also; The AS/400 must support TCP/IP protocol The AS/400 that you wish to use must have TCP/IP Services installed and enabled The PC s (Server & Clients) must have access to the AS/400 on the network they are connected to (TCP/IP connection). This can be confirmed by using the PING Command from the PC s in question OS/400 Level must be V5R2M0 or above You must have iseries Access for Windows with the.net provider option installed onto the PC s that will use SPEX (iseries for Windows v5r3m0 or above with extra.net data provider option taken from within the installation option menu). Please see the appendix for further information regarding the iseries software requirements. Please note that if you will be using an AS/400 for the SPEX tables a small fee is required for the licence for part of the AS/400 communications software used by SPEX. This fee is AS/400 model/processor based so if you require the SPEX system to connect to more than one AS/400 then you will need to buy a licence for each AS/400 in question. Please speak to your Kewill Project Manager regarding this. NOTE : Using SPEX on the AS/400 requires the use of 3rd party software supplied by Kewill. This software installs a module onto the AS/400 to be used as well as the SPEX Client PC s to be used. The module on the AS/400 installs one library (CO405) to include all objects required for use. It also contains a subsystem (CO405TCP) that needs to be active. This is the subsystem that the SPEX connections run through. Page 6 of 15

7 2.2. Oracle If you plan to store the SPEX database on the Oracle RDBMS System then the following prerequisites apply also; The Oracle database / database server on which you plan to install the SPEX tables must be installed / configured and running. A Database instance that you wish to install SPEX tables into must be set-up and configured with a user profile for access with full rights (to allow SPEX to create the tables within the table space). The PC s (Server & Clients) must have the appropriate Oracle Client software installed and connection to the database in question verified. If you are not using Oracle Clients and wish to use ODBC from SPEX to Oracle then the appropriate Oracle driver must be installed, configured and tested as required. The Oracle RDBMS must be at release 8 or above. The Oracle Client software installed must be at release or above, including ODP.NET (Oracle Data Provider) Progress, SQL Server, DB2 If you plan to store the SPEX database on any of these database types then all of the PC s (Server & Clients) must have a suitable ODBC Driver installed, configured and tested against an appropriate database instance that will be used. You should check with your Kewill representative about supported ODBC drivers before proceeding. For ALL instances above we strongly recommend that you have someone available with appropriate knowledge of your set up / environment and user / password knowledge at the administrator level for any visit. Page 7 of 15

8 3. SPEX XML Processor Sub-System & XML Interface Requirements If you will be using an interface with SPEX that will utilize XML as it s feed (or a KEWILL provided XML Adapter) then you will be using the SPEX XML Processor Sub-System. This system will sit and run, processing XML requests to input data to SPEX and to automate SPEX functions available to it. It is required that this sub-system runs on a Server or a dedicated PC. The hardware requirements are as above. A dedicated server/pc may be the best approach to gain the best performance however this is all subject to the number of shipments you will be transferring to SPEX within a given period. NOTE : You can not run this sub-system on a pc that will also be used as a client / locally installed pc for a user Page 8 of 15

9 4. Printers SPEX requires a printer to be available on the machines that will use SPEX in order to print documents to hard copy. The printer can be any laser printer that has an appropriate set of drivers for the Operating System(s) that will be used by the server and client PC s. It is recommended that you use a HP LaserJet series or compatible printer for best results. If you plan to use pre-printed stationary for documents (some documents require this) then SPEX can also support dot matrix printers if you have continuous stationary (or you can acquire laser copies of these documents for use with your laser printer). SPEX will function with either method. If you are planning to use a Dot Matrix printer you MUST have an appropriate Printer Manufacturers Supplied driver for the printer / Operating system(s) you will be using. The Windows supplied DEFAULT Dot Matrix printer will generally NOT provide the desired results with our software. Page 9 of 15

10 5. ERP Integration 5.1. GEAC System/21 or Aurora In order to integrate SPEX as standard to System/21 using the System/21 standard interface method you will need to adhere to the following additional pre-requisites; GEAC World Trade module Installed and pre-configured to minimum level of SP4 Level B (recommend SP5). Test Company profile or test environment configured and set up for World Trade Appropriate user connection for Sys/21 access and administrator access available for visit Ability to pass through test orders / invoices to test the integration between Sys/21 and SPEX In order to use the SPEX 8.2 latest features we will also provide an extra library with our system. This library will contain extra tables and an RPG interface program to bolt on to the GEAC World Trade Interface programs for new field population. Therefore we will need to have access to the AS/400 command line and programming authority. You will also need to have an RPG compiler available on your system. Any queries regarding this please contact your KEWILL Project Manager. If you have any custom modifications to System/21 please speak to your KEWILL project manager first. Please also refer to the important pre-requisites for the AS/400 database option section JD Edwards If you are planning to interface with the Oracle Applications system you should contact your Kewill Project Manager to discuss options. We have several clients who have interfaced from Oracle Applications to SPEX and various options are available for discussion. Page 10 of 15

11 5.3. IFS Interface If you are planning to interface SPEX with the IFS System you will need to adhere to the following pre-requisites also; You will need to use the IFS module and triggers that provide the data to the SPEX XML Adapter. This must be obtained from your IFS representative and be installed / configured prior to installation of SPEX The SPEX XML Adapter and XML Processing Sub-System must be installed onto a server that has access to the file path and files created by the IFS module above. If the IFS system to be used is running on a UNIX platform rather than Windows, you will also need a suitable tool to allow the Windows server containing the SPEX XML processor and XML adapter to view the appropriate UNIX located folder (such as SAMBA). This must be installed and configured prior to installation of the SPEX system. Please contact your Kewill Project Manager for further information 5.4. SAP Interface If you are planning to interface with the SAP system then you will need to be able to output the required SAP IDOC type for us to pick up and translate with our XML Adapter software. Usually customers feed the delivery IDOC and/or the Invoice IDOC for use with SPEX, however others have been used subject to customers specific requirements. You should contact your Kewill Project Manager to discuss mapping requirements before proceeding further ORACLE Applications Interface If you are planning to interface with the Oracle Applications system you should contact your Kewill Project Manager to discuss options. We have several clients who have interfaced from Oracle Applications to SPEX and various options are available for discussion. Page 11 of 15

12 5.6. Other ERP Systems If you plan to integrate SPEX with another ERP system not listed here or your own in house written system this is fine. We currently have hundreds of customers interfacing many different products to SPEX the list above are simply the most common ones we come across in today s marketplace. We can utilise the XML Adapter software to get at the data as required. Please contact your Kewill Project Manager to discuss the requirements and any impact this may have on the pre-requisites for implementation. Page 12 of 15

13 6. Appendix 6.1. Internet Explorer details You must have VB Scripting Support installed and enabled for IE. To help you verify that you've met the minimum browser requirement take the following steps: Start Internet Explorer Select "Help" from the Menu bar and select "About Internet Explorer" from the drop down menu. An Information window should appear (see over page). Version: If the version number is 5.01 or below, we recommend you upgrade your browser. Page 13 of 15

14 6.2. Digital Certificates requirements for NES users If you will be using the NES (UK customs electronic messaging) module, you will need to use a digital certificate. As a result the following extra information is important for IE. The Digital signature requires the correct version of Internet Explorer (I.E.) to be installed on any PC operating the NES module. Clearly access to the Internet is a pre-requisite and a broadband type connection is preferred to ensure adequate performance Cipher Strength If your cipher strength is less than 128-bit, and your browser is version 5.01 or above, this should be changed to 128-bit go to Microsoft support web site and search for Internet Explorer and Cipher Strength to locate details. From version 5.5 Cipher strength is 128-bit by default. We recommend for security purposes the latest version of I.E. is installed (which at the time of writing is 6.0 SP2) Security Updates You should ensure that you have the appropriate security updates for Windows installed in order to be able to begin the enrolment process for a digital certificate. At the time of writing Microsoft had recently released a new security update for all of its operating systems to allow this. Please follow the link below to find out more information and download the appropriate update for your operating system. US;Q323172& Any changes required to meet the minimum requirements must be completed before you begin your enrolment In order to use Equifax SecureMark certificates for retrieval and submission of forms through the Government Gateway. Page 14 of 15

15 6.3. IBM iseries Information for AS/400 customers The IBM DB2 UDB for iseries.net data provider allows Windows applications to use the Microsoft.NET Framework to access DB2 UDB for iseries databases. It requires iseries Access for Windows V5.3. OS/400 V5R3 customers iseries Access for Windows (5722-XE1), V5R3 is part of the standard set. OS/400 V5R2 customers using iseries Access Family (5722-XW1). If you have a software maintenance contract for your V5R2 system, you can acquire the V5R3 iseries Access Family products but keep your OS/400 at V5R2 by ordering the 5722XW1 (iseries Access Family) refresh. The refresh feature is The IBM link is below: OS/400 V5R1 customers You will need to update your OS/400 software prior to installing/upgrading to this release of the SPEX software. You can continue to use SPEX v8.1 if you are a current SPEX customer until such a time. This information is as provided by IBM as of 13 th October You should check with your IBM representative for up to date information. Page 15 of 15