|
March 2008 |
|
|
|
|
eDeveloper
Server for iSeries
V10.1 Service Pack 3-1 |
|
|
|
|
|
|
|
We are pleased to present
you with the release of eDeveloper Server V10.1 SP3-1 for iSeries
platform. Please read the information
below to learn more about eDeveloper Server for iSeries,
Version 10.1 Service
Pack 3-1. For information about
eDeveloper Version V10.1 Service Pack 3 see ftp://ftp.magicsoftware.com/v10product/ReleaseNotes/v101_sp3_ReleaseNotes.pdf For information about
eDeveloper Version V10.1 Service Pack 2 see ftp://ftp.magicsoftware.com/v10product/ReleaseNotes/v101_sp2_ReleaseNotes.pdf HTTP Server (Powered by Apache) Using colors for browser tasks
eDeveloper for iSeries Server Version V10.1 Service Pack 3 lets you run remote, Internet and batch programs directly on system i (iSeries) and allows access to local and remote DB2/400 DDS (ISAM) files, DB2/400 SQL tables, Memory files, and OS/400 functions such as CL/RPG/COBOL programs, CL commands, Data Area, and other iSeries objects. ·
OS/400 V5R3 and later ·
OS/400 Private Address Space Environment (PASE) - IBM
License program 5722SS1 option 33 ·
TCP/IP configuration for iSeries ·
MAGIC400 Host Library from eDeveloper V10.1
SP1 and later installation ·
Permanent or Evaluation License PAK Execute the iSeries_srv10.1sp3.zip in your PC Temp directory and run
the installation program Mgobjtrf.exe. Accept the iSeries
library default and choose the FTP transfer protocol. You configure and manage
the eDeveloper server using the Magic server administration menu. Enter the
following commands in the iSeries command line in
order to invoke the Magic server administration menu: ·
Type CHGCURLIB <New
Library name>
and press ENTER. ·
Type CFGMGCSVR and press ENTER. HTTP server configuration (Back) -
From the Internet/Partition menu choose HTTP Configuration in order to
initialize the iSeries Web server for Magic
Internet requests. 1. Choose option
4, Work with HTTP Configuration. 2. Accept CONFIG,
the default configuration name, and press ENTER. 3. Make sure the
GET, HEAD and POST lines are enabled. Then add the following lines: ·
Pass /MAGICRUN10/* ·
Pass /MAGICRUN10/web_utils/* ·
Pass /MAGICRUN10/cgibin/* ·
Map /Magic101Utils/*
/MAGICRUN10/web_utils/* ·
Map
/Magic101Cache/*
/MAGICRUN10/Browser_Client_Cache/* ·
Map /cgi-bin/*
/cgi-bin/MGRQCGI.PGM ·
Exec /cgi-bin/*
/QSYS.LIB/MAGICRUN10.LIB/* 4. Select option 6
to end the HTTP server and then select option 5 to start the HTTP
server. In
order to send a request to a Magic eDeveloper Server on iSeries
from an Internet Browser open the following URL: http://<server_name>/cgi-bin/mgrqcgi101?appname=examples&prgname=AAA Note: The MGREQ.INI
file, which is used by the Apache or by HTTP original web servers is located
in the same directory where Magic Internet requester program mgrqcgi101
is located. The default location of MGREQ.INI file and Magic Internet
requester program mgrqcgi101 are in the cgibin
directory. HTTP
Server (Powered by Apache) configuration (Back)
- Start the administrative server instance
by issuing following command: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
Open
the following URL to create the Apache instance: http://<server_name>:2001 The
Apache instance directory and its configuration files are created in the /www
directory. Add the following lines to the httpd.conf
file:
Alias /Magic101Utils
/QOpenSys/magicrun10/web_utils
Alias /Magic101Cache /magicrun10/Browser_Client_Cache ScriptAlias /cgi-bin /QOpenSys/magicrun10/cgibin <Directory
"/QOpenSys/magicrun10/cgibin/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all </Directory> <Directory
"/magicrun10/Browser_Client_Cache/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all </Directory> Magic requester settings (Back) The following settings in the MGREQ.INI file affect the
requester execution: The eDeveloper 10 log file
is created for each server you start. Its name is determined by the ExternalLogFileName entry in the MAGIC.ini file. The Java CLASSPATH
separator character on iSeries platforms is a colon
(:) as opposed to the Windows platform
separator character which is a semicolon (;). For example: CLASSPATH = /java/MyClasses:/java/OtherClasses
For more information,
please refer to the Java documentation See:
(http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/index.html). Note: Java integration is
supported for OS/400 V5R3 and later. Make sure you have installed Java
Developer Kit (JDK) 1.5. In
order to set java 1.5 as your default Java you should: Specify
-Djava.version=1.5 on the java command or in your SystemDefaul.properties file otherwise the java will
default to 1.4. . if you
are on v5r4 they also have the option to run the 32bit java 1.5 by specifying the JAVA_HOME environment variable. Make sure you also have the latest java group on your
system - sf99291 lvl 10. Or: If
multiple JDKs installed, how can I change the default JDK to a different version? Answer: A number of properties are set when the
Java virtual machine starts. To change the version
of the Java virtual machine, you will need to set the property for Java version (java.version). Use one of the following
methods to set the property:
o Provide a file in /QIBM/UserData/Java400,
named
SystemDefault.properties.
The property values that you specify in this file
override the system defaults that IBM provides. This
file sets the default system properties
for all Java virtual machines that
run on your iSeries 400 system.
o
Or, place a SystemDefault.properties file in
your own user.home path. This file and the properties that it
contains override those in
/QIBM/UserData/Java400/SystemDefault.properties. This file sets the default system properties for all
Java virtual machines that run for
you.
Following is an example of a SystemDefault.properties file: java.version=1.2
WebSphere
MQseries (Back) If you are using an MQseries Queue manager on iSeries,
you need to set the following logical name in the MAGIC.INI file: Enter following lines in the
MGENV400 server profile file: # Websphere
MQ - UDP WMQseriesS=$MAGIC_HOME/bin/mgmqseries_c WMQseriesC=$MAGIC_HOME/bin/mgmqseries_c Using
colors in browser tasks (Top) - In
order to use colors properly on iSeries, you must
define all the colors that are used as non-system colors. The easiest way to
do this is to access the color file in the Magic toolkit mode and define the
colors accordingly. Developers familiar with
the UNIX operating system can use the eDeveloper Server on iSeries through the PASE interface, which is actually an
IBM AIX operating system. From the iSeries Utility
menu choose PASE environment in order to enter the UNIX shell on iSeries. Server
Initialization
(Back) - Run the following command in
the shell: . ./.profile The browser client technology of eDeveloper enables
the end-user’s browser to locally cache the logic segments of the
application. In this way a significant amount of data is retrieved from the
client’s cache instead of being transmitted anew for every task. The browser
client caching mechanism is aware of changes introduced to existing tasks and
will cache and utilize the modified task. This mechanism is affected by the following
environment settings: Browser client cache path and Browser client cache
alias (CTLCacheFilesPath and CTLCacheFilesAlias
accordingly). Both are defined in the MAGIC.INI file. The eDeveloper server should have write
permission to the directory defined by the CTLCacheFilesPath
environment setting. The Web server should have read permission to
the same directory. You may choose to create a different directory and point
to it by the CTLCacheFilesPath environment variable.
The alias defined by the CTLCacheFilesAlias
environment variable should also point to this directory. A remarked entry named MGLOCAL, which points to the
Korean support library mglocal.kor, exists in the mgenv
file. This file is required for proper functioning of browser-based
applications when using Korean/Hangul characters. ·
Connectivity to messaging servers via JMS is not
supported using the provided messaging component in this release. The license procedure and the server license mechanism have not been changed since the previous version. The valid license names for this version are:
You need to update the
Host Library License file by using the EASYCLEF command on the iSeries command line and the LicenseName
line in the MAGIC400.INI file for an appropriate license name when you get
evaluation or permanent License PAKs. ·
Back up all Magic configuration files, such as
MAGIC400.INI, MGRB.INI, MGREQ.INI before modifying them. ·
Use the HTTP server
(Powered by Apache) for better performance. The sample Apache
configuration file Sample_Appache_httpd.conf is located in the cgibin
server directory. |
|
|
|
Thank
you, The
eDeveloper iSeries Team |
|
|
|
|
|