Database:
- Oracle versions 7 and up, or SQL Server 2012 and up.
- Database disk space requirements vary depending on company size. The users will want several years’ data available to them. We have found disk space requirements generally vary from 10 Megabytes to 1 Gigabyte but may require more space depending on the volume of data being imported.
- Basic Oracle objects are used such as tables, indexes, functions, and stored procedures. Security is handled using Oracle roles. All EDI Viewer Objects are included in the EDIVIEW schema. Data is stored in 2 tablespaces: EDI_DATA and EDI_INDX. SQL Server data will exist in a distinct ‘EDI Viewer’ database. Logins will be created for users which is mapped to this database.
Desktop Requirements:
- EDI Viewer is a 32-bit application written in Powerbuilder and can be run on any version of windows. Disk space requirements are 100-200 megabytes. Typically, the application and its runtime files will exist on a shared network apps drive, with a shortcut to the executable on user desktops.
- To access your database, your desktop needs to have the database drivers installed that you will be using. (Oracle SQL NET or Oracle client, ODBC drivers, SQL Server Native Client 10 or 11, etc.).
EDI Viewer Installation and Setup:
- Copy all EDI Viewer files (Application, .ini file, .pbd files, .dll files, .bmp files, and icons) into a folder.
- Open the ediview.ini file and change the first 3 sections as appropriate:
- Create a shortcut of the EDI Viewer Application (ediview.exe) and move it to the user’s desktop.
EDI Viewer Configuration:
- The system can be installed on a network drive. If so, no EDI Viewer files aside from Application shortcuts are needed on individual desktops and maintenance is minimal. There are 7 different modules available in EDI Viewer, but they are all in one executable file making it easier to maintain new releases and updates.
- There are several different configurations to put EDI Viewer on the desktop for performance enhancements, but this requires additional maintenance for updates or new versions of EDI Viewer. None of our existing clients have installed EDI Viewer this way.
- There are registry settings used on each user’s desktop which save their preferences for how they use the system (e.g.: window sizes, most recently used reporting parameters, etc.).
- Aside from the initial set-up, the ediview.ini file offers options to change several editable column names within the EDI Viewer application.
Updating EDI Viewer:
- EDI Viewer is updated in 2 separate steps:
- Any database update scripts must be processed through SQL Plus, or an alternative application like Toad. The SQL Server Management studio can be used for a SQL Server setup. If database changes are required in an update, they must be done first.
- Copy any new Powerbuilder (.pbd) files into the directory EDI Viewer runs from. This can be checked by right-clicking on an EDI Viewer shortcut, choosing Properties, and looking at the directory in the Target: section
