Server Guide : Testing server applications : Running a packaged image : Running Seaside Hello World
Running Seaside Hello World
This example is based on the Hello World Packaging Seaside Single Module Packaging Example. The Seaside Hello World example causes text and time to be printed to a website. The packaging example ends up with a reduced runtime image named seasideHelloWorld.icx.
Launching in Development Environment
The instructions here are sufficient to launch the seasideHelloWorld.icx from the directory in which the packager created it. For more see Running a packaged image.
In a command terminal, cd to the directory with the reduced runtime image, and then use the appropriate command below. The commands start VA Smalltalk headlessly. The Seaside Hello world example registers the domain part and starts the seaside adaptor. This sets up a local website.
For Windows:
esvio -lCON -iseasideHelloWorld.icx -ini:abt.ini
For Linux (UNIX):
esnx -iseasideHelloWorld.icx -ini:abt.ini
Launching in VAST Runtime
See Running a packaged image for how to get the VAST Runtime.
Copy the reduced runtime image, seasideHelloWorld.icx, into the root of the VAST Runtime tree.
Copy <server-runtime-root>\newimage\esvio.ini (abtnx.ini for UNIX) to the same directory as the packaged image, seasideHelloWorld.icx, and rename it seasideHelloWorld.ini
Open a command terminal, cd to <server-runtime-root>.
Launch the image from the command line.
For Windows: bin\esvio.exe -lCON -iseasideHelloWorld.icx
For Linux (UNIX): newimage/abtnx -iseasideHelloWorld.icx
 
Seaside launched
Here is a snapshot of the console on a successful launch. If you don’t see this, look at the troubleshooting section.
VA Smalltalk, Version 9.2
(g)VM Timestamp: 4.0, 12/12/18 (100)
(C) Copyright Instantiations 1994, 2018. All rights reserved.
(C) Copyright International Business Machines Corp. 1994, 2006. All rights reserved.
Virtual Machine PID: 6392
 
VM Options {
newSpaceSize set to 2097152
}
Commandline args {
-iseasideHelloWorld.icx
-ini:abt.ini
}
 
ServerName: 'Seaside Servlet Server'
Handlers: OrderedCollection(SstInvocationHandler(http://:8888/) )
Logger: nil
Contexts: LookupTable('
SstServletContext {
ContextPath: ''/''
DefaultServlet: WASstHttpServlet
ServletMaps: LookupTable {
''Seaside Servlet'' -> OrderedCollection(''/Seaside'' )
}
InitParms: LookupTable {
}
ErrorPages: LookupTable {
}
SessionConfig: a SstSessionManagerConfiguration
}' )
 
Browse page
To see the website, start a web browser on the URL http://localhost:8888/helloworld. The website looks something like this
C:\Users\documentation\Documents\vastePublisher\stable\VAS Documentation Word\images\sv\seahw.png
If the website includes the text ‘(ExWAError)’ check to see that you have installed OpenSSL.
To be sure Seaside is running, click the OK button to update the time.
Stop the Seaside example by closing the command window. Close the Internet Browser page showing the Seaside URL.
Troubleshooting
This section lists some common errors that indicate the Seaside example is not set up properly.
OS error 126: Module could not be found
If you are getting an OS error 126, check to see if you have installed OpenSSL.
Command window snippet:
The following error(s) were detected during the startup sequence which may interfere with correct operation:
 
 
1) Primitive failed calling 'SOCKETS':WSAGetLastError from PlatformFunction>>#call due to OS error126
Process reportError: Primitive failed calling 'SOCKETS':WSAGetLastError from PlatformFunction>>#call due to OS error126
Cannot establish communication with '127.0.0.1' because the following error occured: Primitive failed calling 'SOCKETS':gethostname from PlatformFunction>>#callWith:with: due to OS error126
Dumping Stack File seasid00.sdf ...
...Finished Dumping Stack File seasid00.sdf
 
Fatal Application Error: Exit due to error: 62 - Exit due to error with stack dump provided
Firewall
Make sure you have permission access the Seaside website.
For example, if you get a "Windows Defender firewall as blocked some features of this application” (for esvio) you need to give permissions in order to be able to see the website.
‘(ExWAError) An exception has occurred: no secure key generator available because seeding failed’
If the Internet Browser opens on the URL, but reports the above error, check to see if you have installed OpenSSL.
For Example, if you get a "Windows Defender firewall as blocked some features of this application” (for esvio) you need to give permissions in order to be able to see the website.
‘Process reportError: (ExWAError) An exception has occurred: no secure key generator available because seeding failed’
If the Internet Browser opens on the URL, but reports the above error, check to see if you have installed OpenSSL.
Resetting
If you are getting bad result you might like to get back to a clear out any Seaside state and start afresh. Here are some steps to consider:
o Close the Internet browser which is browsing the Seaside URL
o Close the command window which is running the Seaside example.
Once you have done one or more of the above,
o Open a new command window and start the Seaside example.
o Open the Internet browser and browse the Seaside URL
 
Last modified date: 04/18/2022