System Requirements Astro 7.1

DOCUMENT NAME 

System Requirements Astro 7.1 

REVISION 

1.0 

ADDRESS 

Porfyrvägen 14 

SE-224 78 Lund 

Sweden 

DOCUMENT NUMBER 

- 

REPLACES 

DATE 

2008-12-22 

TEL +46 46 280 04 00 

FAX +46 46 15 10 74 

www.consafelogistics.com 

Astro 

System Requirements Astro 7.1

Astro System Requirements Astro 7.1 

Document No. - 

Revision 1.0 

2008-12-22 

Created 

Date Rev Responsible Comment Approved 

2008-12-15 0.9 Kristian Sassersson 

Revisions 

Date Rev Responsible Comment Approved 

2008-12-15 0.91 Kristian Sassersson Info that the database client and manager tools 

must be installed on the Astro server if Astro is 

not installed on the database server. 

2008-12-17 0.95 Kristian Sassersson Server requirements adjusted. Oracle 9 not 

supported for Astro 7.1. End of service dates 

from IBM and Oracle added. 

2008-12-22 1.0 Kristian Sassersson Version changed to 1.0 

System_Requirements_Astro_7.1.doc 2 (37)



Revision 1.0 

2008-12-22 

Table of Contents 

1 This Document.........................................................................................................5 

2 Maintenance Availability Map.................................................................................6 

3 System Requirements.............................................................................................7 

3.1 Server Requirements................................................................................................ 7 

3.1.1 Database Environment ................................................................................. 7 

3.1.2 IBM UNIX Environment................................................................................. 7 

3.1.3 Windows Environment ................................................................................ 12 

3.1.4 Disk Configuration....................................................................................... 14 

3.1.5 Disk Space Needed for Upgrade ................................................................ 17 

3.2 Network Requirements........................................................................................... 18 

3.2.1 WAN – Wide Area Network......................................................................... 18 

3.2.2 LAN – Local Area Network.......................................................................... 18 

3.2.3 WLAN - Wireless Local Area Network ........................................................ 18 

3.2.4 Using DNS.................................................................................................. 19 

3.3 Requirements for the Different Types of Clients.................................................. 20 

3.3.1 Java Telnet Client type MAtelnet2 .............................................................. 20 

3.3.2 Java Telnet Client type MAtelnet3 .............................................................. 21 

3.3.3 Telnet Client (emulator) .............................................................................. 22 

3.3.4 Mobile Unit Terminals ................................................................................. 22 

3.3.5 Astro M2 Client ........................................................................................... 23 

3.3.6 Astro O2 Client ........................................................................................... 24 

3.3.7 Astro M1 (Astro Windows Client) ................................................................ 25 

3.3.8 Handheld Computer Client.......................................................................... 25 

3.4 Web setup................................................................................................................ 26 

3.4.1 IIS hosting................................................................................................... 26 

3.4.2 Encryption between the server and the browser client................................ 26 

3.4.3 Internal encryption ...................................................................................... 26 

3.5 Other Client Requirements..................................................................................... 27 

3.5.1 Support for Printouts................................................................................... 27 

3.6 Printers .................................................................................................................... 27 

3.7 Scanners.................................................................................................................. 27 

3.8 RetroSpect............................................................................................................... 28 

3.8.1 Web Server Sizing ...................................................................................... 28 

3.8.2 Astro ........................................................................................................... 29 

4 Examples of Hardware Configurations ...............................................................30 

4.1 Windows .................................................................................................................. 30 

4.1.1 Single configuration .................................................................................... 30 

4.1.2 Cold standby............................................................................................... 31 




Revision 1.0 

2008-12-22 

4.2 Unix .......................................................................................................................... 32 

4.2.1 Single server............................................................................................... 32 

4.2.2 Cold standby............................................................................................... 32 

4.2.3 Cluster – SCSI ............................................................................................ 33 

4.2.4 Cluster – SAN ............................................................................................. 34 

5 Installation scenarios............................................................................................35 

5.1 Scenario A ............................................................................................................... 36 

5.2 Scenario B ............................................................................................................... 37 




Revision 1.0 

2008-12-22 

1 This Document 

This document describes the general system requirements for Astro and 

Connect release 7.1. Connect are limited to run on Windows platform only. 

Specified hardware components are under constant development and 

specifications are changing rapidly. When in doubt, please contact Consafe 

Logistics. 




Revision 1.0 

2008-12-22 

2 Maintenance Availability Map 

Astro Version Service Level 

≤ 6.4 

Not supported 

6.5 Error corrections 

6.6 – 6.8, 7.1 Error corrections and 

minor development 




Revision 1.0 

2008-12-22 

3 System Requirements 

3.1 Server Requirements 

3.1.1 Database Environment 

Oracle and SQL server can be defined inside the Astro server or in any 

database machine in the customer network as long as the network can take 

the load between the Astro server and the database. 

In the figures for sizing of machines further down in the document, the 

consideration is that the database is inside the Astro server. 

Regarding supported and tested databases, see the IBM UNIX Environment 

(3.1.2) and the Windows Environment (3.1.3) respectively. 

3.1.1.1 Software Components 

If Astro is not installed on the database server, the database client and 

manager tools must be installed on the Astro server. 

Minimum requirements for Oracle to be installed on the Astro server: 

• Oracle Client 

• SQL*Plus (sqlplus), which is normally included in the Oracle Client. 

• SQL*Loader (sqlldr), which is normally included in the Oracle Client. 

Minimum requirements for Microsoft SQL Server to be installed on the 

Astro server: 

• ODBC (usually included with the OS) 

• sqlcmd (or osql for older versions of SQL Server) 

• bcp (the bulkcopy tool) 

3.1.2 IBM UNIX Environment 

Regarding requirements for running Astro on IBM pSeries machines with 

UNIX operating system (AIX), Astro supports all versions of platforms and 

platform software still supported by the original vendor. 

Any other combination of software versions or platforms may cause error or 

disturbances which are not under Consafe Logistics control. 

Consafe Logistics cannot take the responsibility for errors in products from 

other software vendors. 

More information about the AIX software and the pSeries machines (former 

known as R/S 6000) may be found at http://www.ibm.com. 




Revision 1.0 

2008-12-22 

3.1.2.1 Hardware Recommendations 

The table below shows thumbs of role for sizing an IBM pSeries machine 

running Astro on Oracle. 

Hardware Object Recommendation 

Memory AIX 512M 

Memory Database 25 Mbyte/connection* and 500 Mbyte/ 

database instance 

The M2 interface needs about 40 Mbyte per 

user session. 

Disks AIX One pair of mirrored disks 

Disks Application 

and Data 

10 disks mirrored 2 and 2 (5 pair) 

Disk size, minimum 72 Gbyte each. ** 

Processor Connections 

and order 

lines 

Needed rPerf*** is: 

number of connections*0.015*MAX (1, 

number of order lines/15 000) 

Se examples below 

Max memory handled per processor is 

recommended to 8 Gbyte 

* All figures apply to 64bits hardware. 

A connection is a user interfaces or background services accessing the Astro 

database. 

Multiple sites may use multiple database instances depending on the 

operating requirements. 

Operative data must not be stored more than 7 days. This figure may affect 

the amount of disk cache needed in memory. 

A not active session is swapped out by the operating system but still it needs 

5 Mbyte to be kept alive. 

** Not including a pair of mirrored AIX disks. 

Application disks may be SCSI or SAN disks depending of the installation. 

Disk access has to be spread over pair of physical disks with mirrored filesystems. 

Operative data must not be stored more than 7 days. This figure affects the 

amount of disk usage and disk I/O. 

Sizing applies to “normal” size of data (2-5 Gbyte Oracle) and a backup 

stop every 24-hour. Otherwise, maybe, some of the disks have to be larger. 

Multiple sites on the same machine may require other configurations. 

*** Connection as above. rPerf as defined by IBM on pseries machines. 




Revision 1.0 

2008-12-22 

3.1.2.1.1 Examples 

Small configuration 

Conditions: 

• The installation has 50 users and 20 services in background; in total 70 

connections to the database. All are simultaneously active. 

• 5000 order lines are handled per 24 hour 

Requirements: 

• Needed memory is 512M+500M+70*25M = 2800Mbyte 

• Needed processor is 70*0.015*1 = 1.05 rPerf 

Large configuration 

Conditions: 

• 500 connections in total to the database. 350 are active simultaneously 

and 50 of them are M2 interfaces. 

• 45 000 order lines are handled per 24 hour 

Requirements: 

• Needed memory is 

o 512M+500M+ (AIX and Database) 

o 300*25M+ (Mobile users and services) 

o 50*40M+ (M2 users) 

o 150*5M = (not active) 

o 11500 Mbyte. 

• Needed processor is 350*0.015*3 = 15.75 rPerf or at least 2 processors 

according to the memory needed. 




Revision 1.0 

2008-12-22 

3.1.2.2 AIX (IBM) 

Supported versions: 

Version Level End of service*** 

6.1* TL1, SP1 No end date 

5.3** TL7, SP3 No end date 

5.2 2009-Apr-30 

* Test in progress. If this version is considered, please contact the R&D 

department at Consafe Logistics. 

** Release test on this version 

*** IBM availability map 2008-12-17. 

3.1.2.3 XL C/C++ Enterprise for AIX (IBM) 

XL C/C++ Enterprise for AIX is the compiler used for Astro and XML 

components; Former known as Visual Age C++. 

Standard installation must be used. This makes both the C++ and the C 

compiler to be installed. 


Version AIX 6.1 AIX 5.3 AIX 5.2 

9.x* Yes Yes No 

8.x** Yes Yes No 

7.x No Yes Yes 

* Not tested by Consafe Logistics 

** Release test on this version using AIX 5.3 




Revision 1.0 

2008-12-22 

3.1.2.4 Oracle 

Oracle is distributed in several editions; Oracle one, Standard Edition, 

Enterprise Edition. The need for Astro is Oracle One or Oracle Standard 

Edition. 


Version AIX 6.1 AIX 5.x End of service*** 

11.1* Yes Yes Premier support Aug 2012, 

extended support Aug 2015 

10.2.0.3** Yes Yes Premier support Jul 2010, 

extended support Jul 2013 

* Test in progress. If this version is considered, please contact the R&D 


** Release test on this version using AIX 5.3. 

*** Oracle availability map 2008-12-17. 

More notes! 

• Note that Astro does not support Oracle 10.1. 




Revision 1.0 

2008-12-22 

3.1.3 Windows Environment 

More information about the Windows software may be found at 

http://www.microsoft.com. 

Note! The Astro application should not be installed on a server being a 

Domain Controller. The reason is that Astro always is doing a local login 

of the user. To log in on a Domain Controller you must be member of 

Domain Administrators and it’s not preferable to give all users that 

authority. 

3.1.3.1 Hardware Recommendations 

Servers should be 64 bit. Recommendations based on both application and 

database in the same server. For larger installations, a separation between 

application server and database server is recommended. 

Hardware Connections* Recommendation 

Processor Up to 30 1 Dual core processor > 3 GHz 

Processor Up to 60 1 Quad core processor > 2.0 Ghz 

Processor Up to 150 2 Quad core processors > 2.0 Ghz 

Memory SQL Server At least 1 Gbyte per processor core 

Disks SQL Server Minimum 6 disks, 72 Gbyte, mirrored in pairs 

(3 disk pairs) 

Disks Oracle Minimum 8 disks, 72 Gbyte, mirrored in pairs 

(4 disk pairs) 

* Connections to SQL server (or Oracle). This implies both connections 

from user clients and background services. 

3.1.3.2 Windows Server 

Preferred version: 

• Microsoft Windows 2008 Server Standard 64 bit edition with latest SP. 

Other supported versions: 

• Microsoft Windows 2008 Server Standard 32 bit with latest SP. 

• Microsoft Windows 2003 Server Standard 64 bit edition with latest SP. 

• Microsoft Windows 2003 R2 Server Standard 64 bit edition with latest SP. 

• Microsoft Windows 2003 Server Standard 32 bit with latest SP. 

• Microsoft Windows 2003 R2 Server Standard 32 bit with latest SP. 

• Microsoft Windows 2003 Server Enterprise Edition 32 bit with latest SP. 

• Microsoft Windows 2003 R2 Server Enterprise Edition 32 bit with latest SP. 

Note! 

If a 32 bits server is configured with more than 4 Gbyte of RAM, then 

the Windows Server Enterprise Edition is needed to take full advantage 

of the memory. 




Revision 1.0 

2008-12-22 

3.1.3.3 HTTP server / FTP server 

Microsoft Internet Information services (IIS) version as installed from 

windows operating media with FTP server active. The FTP server can be 

replaced with software from other vendors, e.g. BulletProof FTP Server or 

VShell. The HTTP server (a.k.a Web server or WWW server) can be 

replaced with software from other vendors, e.g. Apache. 

Note! Astro has not been verified with other servers on the Windows 

platform, though in theory it should not be a problem. 

3.1.3.4 Database 

3.1.3.4.1 SQL server 

Supported versions of Microsoft SQL Server: 

• SQL server 2008 Standard Edition 64 bit with latest service pack. 

• SQL server 2008 Standard Edition 32 bit with latest service pack. 

• SQL server 2005 Standard Edition 64 bit with latest service pack 

• SQL server 2005 Standard Edition 32 bit with latest service pack 

Note! The 64 bit editions are recommended. This requires 64 bit Windows 

Server. 

3.1.3.4.2 Oracle 

3.1.3.5 Telnet 

Oracle exists in a Standard Edition and in an Enterprise Edition. The need 

for Astro is Oracle Standard Edition. 


Version Win2008 Win2003 End of service*** 

11* Yes Yes Premier support Aug 2012, 

extended support Aug 2015 

10.2.0.3** Yes Yes Premier support Jul 2010, 

extended support Jul 2013 

* Test is in progress. If this version is considered, please contact the R&D 


** Note that Astro does not support Oracle 10.1. 

*** Oracle availability map 2008-12-17. 

The included Astro Telnet Server must be used. 

Pragma System’s telnet server not supported any more. 




Revision 1.0 

2008-12-22 

3.1.4 Disk Configuration 

3.1.4.1 Oracle 

Astro uses several physical disks due to both performance reasons and 

database recovery demands. Disks are mirrored in pair to get high 

availability in the solution. 

Oracle has specific demands to be sure that a recovery procedure will 

succeed. The control files must reside on separate drives or controllers, data 

files, archive files and redo-log files must reside on separate physical drives 

or controllers. Otherwise it is not possible to do recover until the last 

transaction in case of disk or controller failure. 

The recommended Oracle configuration is designed to at least 100-150 

Astro users. Configuration example is attended for IBM pSeries (AIX) but 

may be attached to Windows as well, but with a total of 4 disk pairs only. 

Astro standard disk configuration, Oracle 

rootvg 

vg01 

AIX 

/Oracle 

/usr1 

Oracle product 

Astro 

Mirroring 

/usr2 

/usr3 

Data & index files 

Control file no1 

Archive files 

Control file no 2 

Archive copy 

Database copy 

/usr4 

/backup 

Control file no 3 

Redolog files 

Mirroring 

The spreading over physical disk makes it easy to monitor I/O load. 

Experiences show that the first bottleneck is the very high intensity on the 

Redo files. Next bottleneck is the data files. 

In smaller configurations the rollback segments may be moved to /usr3. 




Revision 1.0 

2008-12-22 

3.1.4.2 Mirroring on AIX 

In an AIX environment, mirroring (RAID1+0) is achieved by the operation 

system. No separate controllers or devices need to be used. If data is stored 

in a SAN device mirroring or RAID controlling take place locally in the 

SAN device 

3.1.4.3 Using RAID Controllers 

Other systems like Windows 2008 need a raid controller to achieve RAID 

setups. If raid is used the recommended raid configuration is RAID1+0. 

RAID0 gives striping over several disks. This will reduce the I/O per disk. 

RAID1 is mirroring of the involved disk for safety reasons. Note the 

demand of spreading critical files over several controllers. 

3.1.4.4 Windows/SQL Server 

The disks are configured as mirrored in pairs, in total 3 pairs. This means 

that Windows 2008 “sees” 3 physical disks. The disks are connected to the 

raid controller. The disks are partitioned into several logical drives, see 

picture below: 




Revision 1.0 

2008-12-22 

The disk partitions are used like this: 

C: Used for Windows 2008 

D: A second Windows 2008 system is installed here for emergency 

situations 

E: Here we store the online database disk-to-disk backups 

F: Other server products than Win 2008 

G: SQL Server database files 

K: Astro application 

L: SQL Server database transaction log(s) 




Revision 1.0 

2008-12-22 

3.1.5 Disk Space Needed for Upgrade 

Normal Astro upgrades consist of some operations that may consume disk 

space. The recommended amount of space is: 

• 1.5 Gbyte for a total copy of the old Astro version 

• Equal amount of space as current database size. 

• E.g. if the database files need 2.5 Gbyte, there is a need for another 

2.5 Gbyte when updating the database tables. 

If Oracle or SQL server is upgraded, another 2.5 Gbyte of disk space is 

needed. 

If physical disk space is present it is recommended to allocate a separate file 

system for the upgrade use only. 

Normally it is not necessary to include this file system in the backup. When 

in doubt contact your application responsible at Consafe Logistics. 




Revision 1.0 

2008-12-22 

3.2 Network Requirements 

3.2.1 WAN – Wide Area Network 

When the warehouse and the Astro server are located in different parts of a 

network and there is a public network involved in the communication, the 

following requirements should be taken into consideration. 

Bandwidth • Experience tells us that 2 Mbits/sec is sufficient for 

the Java/Telnet clients, but the requirements depend 

on the number of clients, the number of printers, 

types of clients, etc. 

• Introducing the M2 and O2 clients with graphical 

interfaces raises the bandwidth requirements to a 

minimum of 8 Mbits/sec. Again the requirement 

depends on the number of clients etc. 

Transmission A round trip of a TCP/IP ping should be maximum 50 

time 

ms. For exceptional cases, up to 100 ms is accepted. 

Redundancy Due to that all updating in Astro occurs in real time, the 

network must have sufficient redundancy. This is 

especially important when there are connections to 

automation equipment like cranes and label equipment. 

Prioritizing of 

traffic 

3.2.2 LAN – Local Area Network 

There must be possibilities to prioritize certain kinds of 

traffic, for example the telnet protocol. 

When the Astro server and the clients are located in the same plant, network 

capacity problems are more unusual. 

3.2.3 WLAN - Wireless Local Area Network 

Bandwidth 

Transmission 

time 

Roaming 

A graphical client needs about 250 kbit and a character 

based about 19 kbit. Thus the performances depends on 

the number of clients and the types of clients, also the 

number of printouts and other circumstances impacts 

the performance. The O2 client is designed to operate in 

a WLAN with 2 Mbits/s at the weakest point. 

The requirements are different for different 

installations. Note that long distance to access point 

impacts the transmission time negative. 

For the Java/Telnet client the access points and LAN 

backbone must have good roaming ability suitable for 

the telnet protocol. 




Revision 1.0 

2008-12-22 

3.2.4 Using DNS 

Astro and its clients can work with DNS servers. Both lookup and reversed 

lookup techniques are used. The response time from the DNS server is 

critical for the behavior in Astro. A local DNS is always recommended and 

the functionality must be secured and supervised up to at least the same 

level as the Astro server. 

3.2.4.1 Client connect the Astro Server 

Astro has a Java Telnet Client (a.k.a. MAtelnet), executed in a Web 

Browser (e.g. Internet Explorer) on a Client Computer (e.g. Windows XP). 

The connect information is stored on the Astro Server, usually as an IP 

address. If a hostname is used, all clients using the Java Telnet Client must 

be able to resolve the hostname. 

Clients using other telnet clients (e.g. Reflection) and Astro Windows 

Clients (e.g. M2, O2) must individually set the IP address in their setting 

files. If a hostname is used, the client must be able to resolve the hostname. 

Test this with e.g. "nslookup " on the client. 

3.2.4.2 Astro Server resolving a Client address 

The Astro server must be able to know the peer name of the connected 

client. 

Astro will use the output from the "who am i" command for telnet sessions. 

Astro will use the C subroutine getpeername for AWC (M2 etc) sessions. 

Test this with command "who" for logged in telnet sessions from mobile 

units. 

Testing can also be done with "nslookup" on the Astro server. 

3.2.4.3 Screen and Keyboard mapping 

In Astro there are setup screens for telnet clients that use the client name to 

match a setup of screen and keyboard types. See Astro manuals for this. 

3.2.4.4 Converting /etc/hosts to DNS 

It is recommended that a few pilot entries are remarked in the host file and 

added to the DNS to ensure that it works all the way. 




Revision 1.0 

2008-12-22 

3.3 Requirements for the Different Types of Clients 

3.3.1 Java Telnet Client type MAtelnet2 

The client is normally used for mobile unit terminals. 

MAtelnet2 is a terminal emulator from Consafe Logistics which is 

optimized for MSJVM (Microsoft Java Virtual Machine). For this a Java 

compatible web browser is needed. 

Requirements 

• OS = Windows 

• Web browser = IE 4.0 or higher with MSJVM 

• Terminal emulator = MAtelnet2 

• Bandwidth ≈ 250 kbit during load, 25 kbit running 

• Local printer 

o LPD 

o Windows printing 

Note! Regarding Java virtual machine for IE versions the following apply: 

Up to The Microsoft Java Virtual Machine is included. 

IE 5.5 

IE 5.5 Unattended or typical setup does not install Microsoft VM for 

Java. You must select “Minimal” or “Custom” in the installation 

program and make sure you have checked the Microsoft VM for 

Java checkbox. 

IE 6.0 No virtual machine is included. You can download 

and up Microsoft Java Virtual Machine from: 

http://www.consafelogistics.com/ 

Customer login 

General Documents 

Note! Username and password required. 

Note! The Java Virtual Machine from Sun is suitable only for 

MAtelnet3 (see next paragraph). 




Revision 1.0 

2008-12-22 

3.3.1.1 Trafficom Resolution Standard 

All Astro screens which are intended to be displayed in terminals on 

forklifts or trucks are designed with a width of 77 positions. However in 

some applications there is a need to display also screens designed with a 

width of 80 positions in such terminals, and then Trafficom terminals 

should be of the type SVGA in order to not get too small characters. 

Trafficom requirements: 

Width in No. of positions in the Resolution standard of Trafficom 

Astro screens displayed 

80 SVGA 

77 SVGA or VGA 

3.3.2 Java Telnet Client type MAtelnet3 

The client is normally used for office PCs. 

MAtelnet3 is a terminal emulator from Consafe Logistics which is 

optimized for Sun JVM (Sun Microsystems Java Virtual Machine). For this 

a Java compatible web browser is needed. 


• OS = Windows 

• Web browser = IE 5.5 or higher with Sun JVM version 1.6 or higher. 

• Terminal emulator = MAtelnet3 

• Bandwidth ≈ 250 kbit during load, 25 kbit running 


o LPD 

o Windows printing 

Note! Regarding Java virtual machine from Sun Microsystems you can 

download it from: 

http://java.com/en/download/download_the_latest.jsp 




Revision 1.0 

2008-12-22 

3.3.3 Telnet Client (emulator) 


• OS = Free of choice 

• VT emulator 

• Bandwidth ≈ 20 kbit 


o Local terminal printing 

o LPD 

Above this, PC requirements which depend on the terminal emulator can 

exist. Examples of terminal emulators are Reflection and Glink. 

3.3.4 Mobile Unit Terminals 

See the requirements for the different types of clients in the sections 3.3.1, 

3.3.3, 3.3.6 and 3.5. 




Revision 1.0 

2008-12-22 

3.3.5 Astro M2 Client 

The client is developed for office PCs. 

Astro M2 is developed in the .NET Framework. The hardware requirements 

are less than the minimum required by the operating system. 

PC requirements for the client and its installation: 

Software: 

Approved OS: Windows Vista32 and 64, WinXP32 and 64, Win2003, 

Win2000 

Needed components: 

1) MS .Net Framework 2.0 with service pack 

2) Database drivers: 

Db = SQL-server: 

• MDAC 2.8 service pack 1 

Db = Oracle: 

• OraDirect which is installed with the M2 client. 

3) Internet explorer 5.0 or later 

4) Windows installer v 2.0 or later 

5) Optional: MS Excel 2002 or later 

Hardware: 

• P4, 1 GB internal memory 

• 200 MB free disk space besides the need for the components above 

• Screen resolution: 1024 x 768 minimum 

• Screen colors: At least 4096 

3.3.5.1 Additional Requirements for Crystal Reports 

• OracleNet 9.1 




Revision 1.0 

2008-12-22 

3.3.6 Astro O2 Client 

The client is developed for mobile unit terminals. 

Platform 

SW components 

Processor 

Memory 

Disk space 

.NET 

Screen 

Write access to 

disk 

Astro version 

Keyboard 

Requirements and recommendations 

Possible OS are 

• Windows XP embedded SP2 

• Windows Vista32 and 64 

• WinXP32 and 64 

• Win2003 

• Win2000 

• Windows installer v 2.0 or later 

• MS .Net Framework 2.0 with service pack 

800 MHz Celeron or better 

512 MB or higher 

200 MB free disk space required to install O2 

The total need of disk space is depending on OS 

MS .Net Framework 2.0 with service pack 

• Resolution 800 x 600 or higher 

• Colors 4096 or more 

• Touch screen recommended. 

Write access to the installation folder and subfolders. 

Astro 6.8 which in turn requires the DB versions SQL 

Server 2005 or Oracle 10.2.0.3 or higher version. 

Consafe keyboard with O2 setup or PC keyboard 




Revision 1.0 

2008-12-22 

3.3.7 Astro M1 (Astro Windows Client) 

To Astro versions later than Astro 6.1, the M1 client is superseded with the 

Astro M2 Client. 

3.3.8 Handheld Computer Client 

Software: 

Platform, possible OS MS Windows CE 5.0 

MS Windows Mobile 5.0 

MS Pocket PC 2003 

Software Components MS .Net Compact Framework 2.0 

Note! Different download files depending on OS, 

see table below. 

Supported Vendors* Symbol** 

Intermec** 

Denso** 

* Regarding other vendors, the scanner interface is not compatible. Making 

a vendor compatible require a new download file, thus programming. 

** All models from supported vendors are not tested. For details about 

different models, please contact Consafe Logistics. 

Download files for MS .Net Compact Framework 2.0: 

OS 

Download File 

MS Windows CE 5.0 NETCFv2.wce5.armv4i.cab 

MS Windows Mobile 5.0 NETCFv2.vm.armv4i.cab 

MS Pocket PC 2003 NETCFv2.ppc.armv4i.cab 

Hardware 

Screen: ¼ VGA (QVGA) and variant of this format (240 x 320 pixels) 

Colors: At least 4096 




Revision 1.0 

2008-12-22 

3.4 Web setup 

This section describes the requirements of the application on the web server. 

For further information the document Astro Web Client Technical 

Specification is recommended 

3.4.1 IIS hosting 

The Application runs as its own webb application under Internet 

Information Services (IIS). 

This is done by adding a new virtual directory to the existing web site. 

Configure to use .NET Framework 2.0. 

The IIS must also be configured to allow ASP.NET v2.0 to run. This is done 

under: 

IIS -> Web Service exntesions -> ASP.NET v2.0. 

Status for the ASP.NET v2.0 extension is supposed to be “Allow”! 

3.4.2 Encryption between the server and the browser client 

The encryption used in this communication is standard SSL. 

This means the webb application requires a certificate to be installed. 

Either this certificate can be issued by the customers own Certificate 

Authority (CA) or the client buys a certificate from a certificate vendor such 

as VeriSign. 

3.4.3 Internal encryption 

The web server is situated inside of the client firewall. This means that there 

is no need for encrypting traffic between the web server and the Astro 

server. 




Revision 1.0 

2008-12-22 

3.5 Other Client Requirements 

3.5.1 Support for Printouts 

To make it possible to connect a printer to a client there must be support for 

any of the following: 

Type of Print 

Support 

Local terminal 

printing 

IP printing 

Windows 

printing 

Remark 

Used in character based telnet clients, for example when 

the terminal emulator is Reflection or Glink. 

For Trafficom terminals, ‘Print services for UNIX’ is 

used together with Windows XP and MALPD together 

with Windows 95. (MALPD = MA-system Line Printer 

Daemon). 

The print queue must be placed on a Windows server 

(just the print queue, not the Astro code). 

3.6 Printers 

A number of filters are developed for different printer languages. Please 

contact Consafe Logistics for information if filter exists for a specific 

product. Regarding label printers to new customers, we recommend the 

following three products: 

• Imaje Compact4 (former Markpoint Labelprint) 

• Zebra ZPL 

• Intermec 

3.7 Scanners 

The requirements arise from which type of bar code that is used and from 

which distance it will be read. 

Connecting methods: 

Method Description 

Keyboard wedge Means connect in series with the ordinary keyboard. 

Serial 

A program that takes charge of read data and sends it 

to the application. 

Programs available from Consafe Logistics: 

• maWedge 

• ma2com 




Revision 1.0 

2008-12-22 

3.8 RetroSpect 

3.8.1 Web Server Sizing 

RetroSpect uses QlikView Server. QlikView Server 8.5 is the latest version 

tested for RetroSpect. 

3.8.1.1 QlikView Server 

The following requirements are taken from the home page 

www.qlikview.com the 6 th of October 2008. 

The disks are recommended to be one pair of mirrored disks type Raid01. 




Revision 1.0 

2008-12-22 

3.8.1.2 QlikView Publisher 

For RetroSpect, QlikView Publisher is used only for loading the RetroSpect 

applications, KPI, Order and Tracker with data. QlikView Publisher is also 

a scheduler for the loading. 

The license number for QlikView Publisher is the same as for QlikView 

Server. 

The following requirements are taken from the home page 

www.qlikview.com the 6 th of October 2008. 

3.8.2 Astro 

Current version of RetroSpect Order Tracker requires Astro 6.6. On earlier 

versions of Astro you must run a RetroSpect version earlier than RetroSpect 

6.6. 




Revision 1.0 

2008-12-22 

4 Examples of Hardware Configurations 

4.1 Windows 

Below some recommended hardware configurations for windows. 

4.1.1 Single configuration 

Configuration showing a single machine solution 

Windows 2000/2003 

Mirroring 

CD/DVD 

Tape 

OS 

Oracle 

SQL Server 




Revision 1.0 

2008-12-22 

4.1.2 Cold standby 

This configuration gives the opportunity to have a hardware backup in case 

of server failure. The standby server may as well be used for test purposes. 

Windows 2000/2003 

Mirroring 

CD/DVD 

Tape 

Applikation 

machine 

OS 

Oracle 

SQL Server 

Windows 2000/2003 

Mirroring 

CD/DVD 

Testapplication/ 

standby 

Testinstallation 

The application machine and the cold standby machine must be exactly 

similar. Disk devices must be of hot swap type. 

The idea is just to change the disks from the application machine to the cold 

standby machine in case of hardware failure on the application machine. 

It is recommended to intentionally shift the machines on a regular base to 

secure the routine and the functionality. 

Cluster configurations 

There are several software solutions on the market for building a windows 

cluster. There should be no problem running Astro in a Windows cluster. 




Revision 1.0 

2008-12-22 

4.2 Unix 

4.2.1 Single server 

• No hardware backup 

• Needs high level of service agreement 

• Some redundancy is possible in the hardware – disks, power, etc. 

4.2.2 Cold standby 

• Hardware is duplicated 

• Short time at hardware error – move disks from one server to the 

other 

• Operators need good continuous training 

• Procedure for switch over is needed – and must be trained 




Revision 1.0 

2008-12-22 

4.2.3 Cluster – SCSI 

• Cluster solution with two separated servers 

• Automated switching at hardware failure 

• Max 25 meters between servers 




Revision 1.0 

2008-12-22 

4.2.4 Cluster – SAN 

Top of the line configuration: 

• Cluster solution with separated servers 

• SAN fiber solution 

• Automated switching at hardware failure 

• Up to 300 meters fiber cable can be used 

• Up to 2000 meters of fiber cable with additional fiber components 




Revision 1.0 

2008-12-22 

5 Installation scenarios 

Astro software product may be installed in several flexible configurations. 

In general there are no limitations on number of module layers as long as 

the following hierarchy is followed. 

Astro modular installation 

Server layer holds physical 

resources 

Standard layer contain all Astro 

standard modules. 

Application layer contains all 

customer specifics. More than one 

application module may share the 

same standard modules 

Installation layer contain installation 

specific information such as 

language, database etc. 

Server 

1..m 

Standard 

1..m 

Application 

1..m 

Installation 

1..1 

Database layer. A resource in the 

server or in the network 

Data 




Revision 1.0 

2008-12-22 

5.1 Scenario A 

The following picture describes a multi site installation with no 

dependencies between the installations besides that all installations are 

hosted in the same physical server. 

The database layer may also be split into several installations/versions if 

needed. 

Installation scenario A 

Standard 

Standard 

Standard 

Application 

Application 

Physical 

server 

Application 

Installation 

Installation 

Installation 

Data 

Data 

Physical 

server 

Data 

More than one complete set of installation modules may coexist in one 

physical server 

Database may be installed in the physical server or may be a resource 

on the network 

Pros 

• Independent installations 

Cons 

• Increased maintenance 




Revision 1.0 

2008-12-22 

5.2 Scenario B 

This scenario shows installations having a common standard and application 

layer. All installations share the same code base, but they do not share 

running processes in the server. 

Installation scenario B 

Standard 

Application 

Physical 

server 

Installation 

Installation 

Installation 

Data 

Data 

Physical 

server 

Data 

Multi site installation sharing Astro standard and application specific 

functions running in one environment 

Pros 

• Easy to maintain 

• One upgrade affects all installations 

Cons 

• One error could affect many installations

System Requirements Astro 7.1

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?