Home

Contents of Version 9.2.1 - JIS Mobile Demo

1. 23 Server Monitor ia Runtime Configuration Done ul Local intranet Process id Specifies the operating system process ID useful for identifying the specific Java virtual machine process in the Windows task manager or using the Unix ps command Stat Memory free the amount of free memory out of the current heap memory size specified in Kilobytes Stat Memory total the current heap memory size specified in Kilobytes Stat Memory xmax the maximum allowed heap memory size as defined by the Java mx command line parameter specified in Kilobytes Stat Thread current the current number of operating system threads used by the Java virtual machine Stat Thread peak the number of operating system threads used by the Java virtual machine at peak usage since the server started Best practices If for a given server process Stat Memory total equals Stat Memory xmax and Stat Memory free is less than 10 of Stat Memory total then the server process is at risk of running out of heap memory To mitigate this risk increase the memory heap size of the specific process using the mx flag or allocate more work processes on the machine by increasing the MaxProcesses setting Before allocating more memory to a process always make sure the server machine itself is not running out of memory A single Java process has limited capacity for running operating system threads the larger the heap memory the s
2. param debugLevel variables will be printed when the server log debug level is equal or higher than debugLevel Uf public void logSharedUserVariables int debugLevel Usage examples 1 From within an ACE method Action Enter Trigger 18000 WaitIndicator True ScrambleName False MoveMode MoveNone Description This method presses the Enter key on the host and then proceeds to the next screen Wiscleices wieilelss ALL Wielce Frons Le Moo Nes eneen DoMethod Receiver System Method logSharedUserVariables Parms 50 DoMethod Receiver System Method logUserVariables Parms 70 DoMethod Receiver SubApplication Method SetCursorPosOnScreenAccordingToFocusedControl Parms HostType AidKey AidEnter RemainInScreen False DoMethod Receiver SubApplication Method MoveAccordingToHost Parms 2 From within a server side extension package appls TESTB48 server user Software AG import cst server general ILIMOOE EVE MEL public class GeneralSubApplication extends appls TESTB48 server original GeneralInternalSubAppl public GeneralSubApplication Globals globals parm super globals parm iaSiebucin 7p public void u_Enter int lParam super u Enter lParam Map vars globals system getSharedUserVariables if vars null Set keys vars keySet Iterator iterator keys iterator while iterator hasNext String
3. Printing Handlers section The following parameters still need to be configured in order to enable printing GUISys TN5250 enable host printing Printer 1 TN5250 Printer set the device nam LUName lt Device name gt Improved Host Language Support Introduction JIS support of host languages has been simplified JIS has now integrated the descriptor mechanism which enables support of more than one host language on the same server requiring minimal configuration Users no longer need to use the complex and error prone LanguageDescriptorFactory extensions This version of JIS also clarifies the level of support to languages that were not previously supported An additional language related enhancement which has been added supports printing special characters to the log file improving debugging capabilities Note Language Descriptors can still be customized at the project level to maintain backward compatibility Using this Feature The following details how to enable and configure this feature on the server the Java Client and the XHTML client Server Add the following lt ApplicationName gt ini setting to enable the feature Emulator LanguageDescriptorEnabled 1 Note Applications that have used LanguageDescriptorFactory extensions in previous versions will also need to add this setting when upgrading Detailed Description of Version 9 2 1 89 90 Java Client 1 Specify the host l
4. To use the command line interface open a command prompt navigate to the lt JISRoot gt folder and issue a JAM x lt command gt as shown below jam x shutdown lt time in minutes gt Closes a JIS server after a time interval specified in minutes when the time interval is not specified the server is closed immediately jam x suspend Suspends connections of new users to the JIS server jam x resume Resumes activity on the JIS server Jam E SESTUS Checks if the JIS server is running Detailed Description of Version 9 2 1 81 82 The status command has the following return codes Code Description 1 The server is running 1 The server is not running or there s a communication problem between JAM and the server In order to check the value of the status command you can create the following CheckServerStatus bat file in your lt JISRoot gt folder echo off Cali Jan x rarus IF SERRORLEVELS EQU 1 goto servererror cho CheckServerStatus server is Ok goto exit Servererror cho CheckServerStatus something is wrong with the server or with the connection from jam to the server RESNE Modifications made to the J2EE Deployment Procedure XHTML only The JIS common installation for J2EE will no longer attempt to update the classpath of an application server or deploy the application EAR files automatically After installing the common in
5. Software AG lt IPAddress gt fe80 21c 23ff fe31 8268 lt IPAddress gt lt JacadaServerAddress gt lt Settings gt Limitations Capturing screens from ACE is not supported when the host address uses IPv6 address format Specifying a Folder where the Java Client Log File will be Saved It is now possible to determine that you want to save the Client log file in a specific folder To do this set the following Applet parameter lt PARAM name DebugFileFolder value lt path to a local file system folder gt For example lt PARAM name DebugFileFolder value c temp gt If the specified folder does not exist on the local workstation the log file will be created in the operating system temp folder The Java console displays the following message indicating the location of the log file Client log file name is c temp debug_1317653980569 log In order to use this feature you must use the signed Java client Applet Logging Messages Improvements The following messages have been added to the logger When receiving the version mismatch page for the Java client the client log will now include the time stamps of the client code and server code thus providing better understanding of the problem All uncaught exceptions are now logged in the client log when using the signed Java client Applet and in the server logs When running the XHTML pages inside the browser JavaScript exceptions are now dispatche
6. These parameters can be set in the jacadasv ini file or from the command line as follows Detailed Description of Version 9 2 1 111 Via jacadasv ini Specify the parameters in the GeneralParameters section GeneralParameters RtDebugFileMaxSize lt max size of log file in bytes gt RtDebugMaxFiles lt number of log files gt Via the standalone server command line Specify the following switches for the parameters RtDebugFileMaxSiz m lt max size of log file in bytes gt RtDebugMaxFiles b lt number of log files gt New Features in Service Pack 9 0A 01 112 Enable opening a window in a maximized state The Java Client now enables writing a Java extension for opening the Applet window in maximized state To maximize a window use the following code package appls TEST user import java awt OTE CSTE aCe oF public class MainWindow extends appls TEST original MainWindow boolean firstShow true public void setVisible boolean show if show amp amp firstShow firstShow false GUICSTFrame getMyFrame setExtendedState Frame MAXIMIZED BOTH super setVisible show Register the MainWindow java extension in the JacadaStarter using the addWindow API Deploying a service to a J2EE Server The HTML page generated by JIS contains links to resources such as images script files css files Html files etc The URLs specified by these links differ be
7. AutoSkip is now supported enabling automatically skipping to the next field in the tab order once the field has been filled and the caret is at the end of this field In the lt ApplicationName gt ini file in the XHTML section configure the AutoSkipSupport parameter AutoSkipSupport 0 does not support using autoskip AutoSkipSupport 1 supports using autoskip default value New Features in Service Pack 9 0B 98 Command Line Access to ACE Command line access to ACE enables automating the following operations e Generate Runtime e Create Runtime Installation e Pack Unpack The command line access mechanism allows external tools to run ACE in automatic mode using an XML file that contains a list of operations to execute in ACE The XML file must be named buildapp xml Place the buildapp xml file in the folder from which you launch ACE the folder containing the ACE executable To launch ACE in automatic mode e Use the following command parameter oREMOTE For example to launch JIS XHTML for 3270 in automatic mode use the following command line ACE EXE Imp oREMOTE When running ACE with the oREMOTE command line parameter the buildapp xml is read and the operations are executed by ACE Running ACE in Automatic Mode When ACE is launched in automatic mode it creates a GUI Additional windows such as the Pack animation window are also displayed However in automatic mode the ACE GUI is disabled Software
8. All processes exited Started server restart Server Module Copyright lt C gt 1997 2616 Software AG Loading interface server please wait Server ready STARTED Running the restart command via JAM s command line operations C JIS91_b29 gt jam x restart C JIS91_b29 gt jamimpl bat p http localhost 8686 port x restart C JIS91_b29 gt C JIS91_b29 JacadaFiles utils jre16 bin java Dsun java2d noddraw classpath C JIS91_b29 JacadaFiles c lasses 5 C JIS91_b29 JacadaFiles classes cst jam jap C JI 91_b29 JacadaFiles utils javahelp javahelp lib jh jar cst admin J AM p http localhost 8686 port x restart Administrator CJAM gt Version 3 8 Copyright lt C gt 1997 26186 Software AG Port file URL http localhost 8686 port Restarting server Done CEA ESA E Executing the Restart command using a JMX enabled monitoring tool or from a Java class which uses JMX code Detailed Description of Version 9 2 1 69 70 Java Monitoring amp Management Console Connection Window Help controlRole localhost 2100 I MBeans E IMImplementation Operation invocation BE a com jacada jis runtime server jmx Status gent x 5 1 Command Line Operations void Q Attributes Operations MBeanOperationInfo resume E suspend Name Value shutdown hestar Name restart H Debug Description restart all the servers License Impact ACTION H Runtime Configuration ReturnType void
9. amp Applet parameter Allows using a server side LanguageDescriptorFactory for backward compatibility Users upgrading their descriptors from an earlier version who would like to continue to use the external descriptors should configure this setting Configuration file lt ApplicationName gt ini Section within file Emulator Possible values Class name default uses internal factory Example ini setting LanguageDescriptorFactory appls MYAPP server user ILanguageDescriptorFactory Applet parameter lt PARAM name LanguageDescriptorFactory value appls MYAPP user ILanguageDescriptorFactory gt LanguageDescriptor Applet parameter 8 URL parameter Name of the language descriptor to be used by this client session Configuration file Java client launcher HTML Section Applet parameters Possible values Are listed in the Supported Languages table Example Applet parameter lt PARAM name LanguageDescriptor value Chinese gt URL parameter http localhost 8080 Xhtml JacadaApplicationName MYAPP amp LanguageDescriptor Chinese Parameters for Backwards Compatible Settings to be used only when not using the Descriptor mechanism Conversion File Software AG This value will override the host code page defined by the language descriptor for all sessions Configuration file lt ApplicationName gt ini Section GUISys TN5250 HostCodePage This value will override the host code page defined by the la
10. following update policy takes place The following configuration files are not overwritten by the runtime installation e Server start up script jacadasv bat on Windows jacadasv on Unix these files are located in the bin folder e Server ini file jacadasv ini in the classes folder e Application ini files lt AppName gt ini and formats ini in the classes appls lt AppName gt server resources folder e Application Html files lt Appl gt html lt Appl gt xhtml html in the root folder The rest of the installed files are always overwritten Uninstalling a runtime installation Use the following procedure to uninstall a runtime installation e Make sure the server and JIS administrator are not running e Open a command window and navigate to the root folder of the runtime installation e Run the following command java jar Uninstaller uninstaller jar e The Uninstaller dialog opens loxi O This will remove the installed application e Check the Force the deletion of checkbox and click the lt Uninstall gt button to remove the runtime installation Enhanced Java Client Packaging Procedure With the introduction of the Java 1 7 0 update 51 JRE unsigned Java class files Jar files and other resource files are blocked by default Therefore unsigned product Jar files are no longer usable and auto generated application class files must be packaged into Jar files and digitally signed by the customer before deployment to produc
11. AppName gt xhtml html itself or write the full URL in the browser s address bar such as XHTML JacadaApp 2 Make sure the client operating system supports the language specified in its Regional Settings and that the language specific fonts if any are installed Customization It is still possible to customize the LanguageDescriptor provided by the product for project specific requirements In order to do this the language descriptor classes must be named as follows Client side appls lt AppName gt user User lt LanguageName gt LanguageDescriptor Server side appls lt AppName gt server user User lt LanguageName gt LanguageDescriptor Software AG Log Files The server log and Java client log now displays field content encoded using the current session language encoding To view the log files with the correct encoding we recommend viewing the log file from a client machine which supports the encoding used by the sessions and use an encoding aware text editor such as Wordpad Backwards Compatibilility Applications which do not use LanguageDescriptors Existing applications that use the application level language setting in ACE and do not use language descriptors will continue working as before Applications which use LanguageDescriptor extensions Existing applications already using language Descriptors implemented as extensions should first try to use the internal descriptors and remove and discontinue the usage of t
12. Chrome 15 0 874 106 Safari 535 24 15 The lines above shows a typical sequence of requests generated when starting a new XHTML session The parameters logged are Server name Client address Username currently not supported Date and Time Http method URI Protocol version Response status Response length bytes Referrer User agent Response time ms To activate access logging either run the server with debug level 70 or higher or add the new ACCESS filter to the list of debug filters There is one access log per server process the log is created in the same folder as the server log The log name is of the following format access lt process_alias gt _yyyy_mm_dd log For example the access log for server process 1 1 for the date November 13 2011 is named access_1 1_2011_11_13 log The access log is rolled over every 24 hours and is kept for 14 days There is no limit on the size of the access log When restarting the server the new access log is appended to the existing access log Detailed Description of Version 9 2 1 55 56 Pattern Matching according to Character Attributes ACE always supported pattern matching using the following character attributes Text color foreground color of the text on the host screen Background color background color of the text on the host screen Underline Reverse image However the knowledge base user interface did not support defining
13. Clear the problem condition for example by excluding the problematic panel and run the verification again until getting a clean run Additional settings defined in the runtime ini ApplicationVerification section VerificationMode there are two modes of verification 1 SCREEN is focused on low level comparison of the new Java code and old C code this is the default mode and every error in this mode should be reported to the Customer Support 2 SESSION is a higher level form of verification When running the utility in this mode it will generate the window components run all methods and server side extensions and invoke all protocol messages as well as performing the functions of the SCREEN verification type Note that the SESSION verification mode is more susceptible to false positives related to environment problems or internal assumptions implemented in project specific code therefore it may sometimes report problems which do not really exist in the real application or even loop endlessly Therefore it is unnecessary to report to Customer Support errors shown when running the Session verification ActionId when using VerificationMode SESSION the ActionId setting represents the action ID of the default method to invoke on the server when moving between panels By default the value is 18000 which represents the default action ID of the Enter method in ACE IncludePanelFiles semi colon delimited list of fully qual
14. Detailed Description of Version 9 2 1 47 48 The supported emulator commands that can be used are YN YS YP for the different layouts of the function keys line YA to display both function key lines YF YYL YX to switch between F1 F12 and F13 F24 function key lines The Dynamic option is the default option for new applications In order for the dynamic keys pattern to be analyzed correctly all of the steps below have to be performed 1 Set PFType DYNAMIC as explained above before importing the Natural map 2 Import the Natural map and compile it into a screen image using the Create Screen Images or Maintain Screen Images wizards 3 When creating the new subapplication from the Natural screen image in the Select Screen Layout step choose the WebLookNatDynamicFKeys screen layout or in the subapplication itself open Layout View and drag the section NatDynamicFKeys around the function key prototypes in lines 22 23 model 2 4 Existing applications using knowledge base definitions developed in previous versions of JIS should append the knowledge base definitions from the NATURAL GKB file in lt JISRoot gt KB_3270 into their knowledge base list in the specific ini note this is an advanced operation which requires knowledge base administration skills Additional Parser Configurations Additional settings can be specified in specific ini section NaturalParser MessageLinePositio
15. EEA a ANE EEEE KEE ASEE 85 Allowing the User to Adjust the Java Client Debug Level 0 eee ceecssecnseceseceseceseceseeeseeesneseneeseeeeeneesaesnaees 85 Post Class PA Ad 85 New Methods for Handling User Variables oo cece eseeseeseecssecesecesecsecesecsseceseesseesseeseaeesaeecseecsaecaaeesaeseseeenaes 85 Rebrandin Ett AN A eaves tet hottest A aden tt do liz 87 New Features in Service Pack 90 3 nit ie 87 Changes in the Product Nate ses scicnsc iavecttscagettdacheessusdadeenes TEE RE O EE E REEE NEEE E EN Ee AEAEE Er Rt 87 Runtime Installation Improvements neie en i E E EE a E EE E EE E ncnnnnos 87 Simplifying the Printing Emulation Configuration XHTML sssssssssssssssssssssresssesssrssressersseesseesseesseessseesseessee 89 Improved Host Language Supported ncnian r a eana re a eTa a aa aaen iae 89 Java Client About Dialog Box aii a a e e babe sete oteti oes 95 Host Print Transform Printing using Java Services eessseeeeseressesressesresserrissresesresresteserresseertssrestestesesressete 95 Exposing the XHTML Page DOM for Java Extensions eseseeeeseereesesressesrreseesrssresresresesrisstsrtestentesressesressee 95 Autoskip Supported MAH TM AA A co 98 New Features in Service Pack OB 0 A A A yee 98 Command Eine Access to ACE anemer eean i eee aee nanai daoen eE nian EE nenas 98 Improved User Interface ny orio ienai ee hee E E en E EE eae ae ee ee ieee 102 Additional Enano MENS ii A A a ae Ag aE ean bea eas ecko 104 Det
16. a JITGUI screen converted screens have different structure specially if they contain tab controls Document xhtmlDom context getXhtmlDom NodeList formList xhtmlDom getElementsByTagName XhtmlConstants HTML FORM Node form formList item 0 we assume this is the jacadaform but you need to check to make sure NodeList formElements form getChildNodes for int i 0 i lt formElements getLength i Node formNode formElements item i if span equalsIgnoreCase formNode getNodeName NodeList spanChildNodes formNode getChildNodes for int j 0 j lt spanChildNodes getLength j Node spanChildNode spanChildNodes item j if pre equalsIgnoreCase spanChildNode getNodeName NodeList preChildNodes spanChildNode getChildNodes for int k 0 k lt preChildNodes getLength k Node preChildNode preChildNodes item k 1f label equalsIgnoreCase preChildNode getNodeName clone the label change its color to Blue and update it back to the dom Element label Element preChildNode cloneNode true String style label getAttribute style style style replaceFirst color RED color 0000f f label setAttribute style style spanChildNode replaceChild label preChildNode public void onPageSubmit OnPageSubmitContext onSubmitContext Detailed Description of Version 9 2 1 97 AutoSkip Supported in XHTML
17. address is the external machine address and not the internal localhost address To specify the machine redirect address use the following jacadasv ini GeneralParameters MachineRedirectAddress lt machine name or ip address gt Detailed Description of Version 9 2 1 39 40 SI 5073514 SI 5073513 JIS 1290 When turning off the auto reconnect feature AutoReconnectToHost 0 nO message box is displayed and no session dump is created when the host closes the Telnet connection In addition if the same device name is reused and RequestDefault LUNameWhenLUNameIsRejected 0 ini setting is set a message box is displayed but no session dump is created Java Client SI 5070655 JIS 1126 When the client communicated with the server over HTTP data from the client was submitted more than once SI 5070122 JIS 1138 Popup windows were not printed correctly when using the print GUI feature SI 5076000 JIS 1189 When using the emulator screen the screen sometimes was not painted correctly SI 5084914 JIS 1233 In some cases the Java internal type ahead mechanism causes problems for the user interface We have now introduced a setting which specifically disables this mechanism lt PARAM name IsDisableJavaFocusManagerTypeAhead value true gt The default value is false not disabling the mechanism Customers using the fix for ticket 5041270 should set this parameter as true SI 1048440 JIS 1237 Creating an SSL sock
18. ee ans eea a ee a aa en eea E aey E adea 74 XHTML JavaScnpt Chient Logs iii tease nite eden ie el ag ae des nearest peace 74 Keyboard shortcut for Java client Print GUI ee eeecssecsseceseceseceseceseeeseeeseeseneceaeeeneecaaecsaecsaecaecsaeesseeeeessaeee 75 Localization Improvements aaee A A A A bc 75 Localizing Dynamic Control Strings nsec ien ia nono nono E nono no nono none none e aa e ran e Aa a ete 75 Multiplying Default Control Size by a Pre Defined Factor ooooconccnoconocononoconoconoconncnnncnnncnnnn nan conan ono nr nnn cra cra ccoo 77 New Features in Servico Pack IDA a be A aE veut ee esl ie ee 79 Eo gging Improvements etoos ets RR OR 79 Simplifying JIS Windows Service Configuration cccessccesseceeeeeesseceeseeceeaeecesceeesaeceeaaeceeaeeceaeeeesaecseaaeceeneeesas 80 Using JAM as an Applet in JIS Standalone Server eee ceecceecsccesseeceseceeseeceeseeceeneeeaeeeeaaeceeaeeceeeeeeeaeeseaueceeneessas 80 JIS Administrator Command Line Operations cccccceecceessecessseceeecececeeeaeceeaaecsenceceaceeeaaecseaeeceeeeeeeeeeeaaeceeenees 81 Modifications made to the J2EE Deployment Procedure XHTML only cconicccnncccnnocaninonanonocononaconnnocnnononnncnnnnos 82 UWperadeto Ted AA A AA AREA AE A N EEE A ave dtd AAC IES 83 Running the JacadaProxyServlet as part of the JIS Server cceecccessceeseeceeseeceeneecseeeesaeceeaeeceeeeeeeaaeceeaeeneneeesas 84 Reduction of the size of the XHTML Meur roere tE n EENE aa nii EEEE A
19. in practice the servlet is always running as part of the integrator process 1 0 of the JIS server itself Therefore the independent proxyConfiguration xml file is no longer necessary and the serviet configuration can either be automatically set by the server or configured using the standard jacadasv ini file The following optional settings were added to the jacadasv ini RedirectionProxy section IPAddress IP address of the server This setting is now determined automatically in most configurations Note never use the value localhost or 127 0 0 1 for this setting as this will cause sessions to switch servers when using multiple servers behind a load balancer Port port of the server root process Set it to the Http port used by the server root process This setting is determined automatically in most configurations UseGzip set to 1 or yes to compress the response to the client using GZip Default un no CloseStreamToClient set to 0 or no to prevent closing the client response stream by the server this helps working through a reverse proxy Default yes BypassAfterRedirection set to 1 or yes to configure the client to redirect directly to the worker process bypassing the proxy Default no The file proxyConfiguration xml has been removed from the product installation and runtime installation Backward compatibility As long as your installation contains the now obsolete proxyConfigu
20. made Additional improvements e Default compilation batch size was increased from 30 classes to 90 classes e The source and target release of the compiled application classes changed from 1 4 to 1 5 This allows users to write code extensions which rely on Java 5 specific syntax e When generating an XHTML client the obsolete and confusing static HTML files are no longer generated in the lt JISRoot gt JacadaFiles classes appls lt AppIName gt xhtml templates original folder Users may delete existing old files in this folder to reduce the size of the runtime installation Changing Default Settings In previous releases after clicking Finish in the last screen of the Run Application Wizard the default browser associated with the html extension was opened This approach which had several drawbacks has been abandoned Instead by default the browser opened is the browser specified in the following path C Program Files Internet Explorer iexplore exe This path can be customized using the ini setting RunApplicationWizard BrowserCommandLine lt command line for the browser application gt Examples To run the application using Firefox use the following specific ini setting RunApplicationWizard BrowserCommandLine C Program Files Mozilla Firefox firefox exe new window To run the application using Internet Explorer 32 bit on a Windows 64 bit operating system use the following specific ini setting BrowserCommandLi
21. of memory Therefore make sure to set mx200m or higher for each server process including processes which are usually not serving sessions such as the root process debug_1 log and the integrator process debug_1 0 log For server processes serving sessions the maximum amount of memory allocated to each process should be calculated as follows 200 3 number of session per process For example a server process running 500 sessions should be able to allocate a maximum of 200 3 500 1700MB of memory Q What is the upper bound of memory I should allocate for server processes A There are several factors to consider 1 as a rule of thumb we recommend that the total maximum memory allocated to all server processes should not exceed the total physical memory of the server machine minus 1GB This ensures that the server never exhausts all the available machine memory which will cause swapping problems and has major effect on performance In addition we recommend to never allocate more than 3GB memory for a single server process since this may lead to lengthy cycles of garbage collection which may cause noticeable service interruption Q How many server processes should I configure the server to spawn A We recommend that the number of server processes serving sessions will be in par with the number of CPU cores used by the server machine For example on a dual quad core server i e 8 cores we recommend setting MaxProcess 10 and to con
22. retired e Wise Runtime Installation replaced by the IzPack runtime installation Wise installer functionality is still part of the product in order to allow for smooth migration e Session Pre loading this feature was introduced in V9 0 as the first step towards full fledged session pooling implementation However session pooling is no longer in the product roadmap and the feature in its current state does not provide significant benefit e Online help for the Administrator utility removed since the JavaHelp 3 party component on which it relies has not been updated by its vendor As of release 9 2 the following product components were retired e Innovator removed as part of migration to 64 bit e Jacada Connects sites still using Jacada Connects should continue to use their current version and discuss their project roadmap with Software AG s product management e Deploying the standalone server to AS 400 sites should switch to deploying the server to Windows or Unix platforms e Application Clustering sites using this feature should switch to deploying the clustered applications as separate applications e Jacada Common Installation for application servers no longer required since the application ear file now includes all product components e Standalone Java Client Proxy replaced by internal server functionality Note Extended maintenance for previous versions can be requested from Software AG Software AG New Feature
23. server this should be the address provided by the client browser when connecting to the server using HTTPS or SSL For example www mydomain com or sagjacada eur ad sag Specifying this name correctly is Detailed Description of Version 9 2 1 49 50 important in order to avoid an HTTPS warning message from the client browser By default JIS sets this value to the network name of the machine on which the server is running The OrganizationalUnit Organization City State and Country settings are the X509 certificate distinguished name fields which contain free text relevant for the customer s site The default value of each of these settings is Unknown It s important to set these settings correctly as they can be used later for generating a certificate signing request as part of the process of obtaining a valid SSL certificate instead of the auto generated test certificate The automatically generated JettyKeyStore has the following properties Keystore format JKS Keystore password defaults to the value specified by the jacadasv ini setting HTTP KeystorePassword When the setting is not specified the default password is JettyKeyStore The automatically generated private key has the following properties Alias server key Key algorithm RSA Key password same as the keystore password These settings are non configurable The keystore is generated using the KeyTool utility provided by the vendor of the Java VM currently Oracl
24. settings Software AG Localization of Table Headers Dynamic table header strings can be written to the localization resource file without defining selection rules by using the following ini setting JAVA UseStaticTableHeaders 1 Localization of Control Strings in Runtime Previously only static control strings were localized in runtime according to the user locale Now dynamic control strings for controls that matched one the localization expressions are also localized Note The dynamic strings which are written in the resource file are only those strings that are found in the design view when generating the runtime In runtime these dynamic strings may change and as these values were not found previously when generating the runtime they are not included in the resource file In order to add these strings to the resource file they must be identified in runtime and recorded into the resource file manually The identification of the strings is done by overriding the method AppISubApplWindow java Public String windowMissingResource String key The method receives the string that wasn t found in the resource file and returns the localized version of the string By default the method returns the given text as is or prefixed by when working in a localization debug mode public String windowMissingResource String key Write the missing string to a file or send message to the administrator return k
25. size of the XHTML file This feature reduces the HTML page size generated by JIS and in this way reduces the network bandwidth consumed by JIS applications In addition it also accelerates the generation of the XHTML page in runtime e Position related style attributes of HTML elements are no longer part of the page itself instead they are externalized into a CSS The CSS is generated in runtime the first time the sub application window is accessed e The generated CSS for a sub application is sent to the browser once per session We predict that this will reduce the page size generated by JIS by approximately 30 The feature is enabled by default and can be disabled by setting the following parameter to 0 XHTML OptimizeStyleAttributes 0 1 is the default value Allowing the User to Adjust the Java Client Debug Level It is now possible for the end user to set the debug level of the Java client logs in the current session This can be done by selecting Application gt File gt Adjust Debug Level or by clicking on a key combination defined by the JIS developer The key combination can be defined in the DebugLevelAdjustKey set to any valid single character and DebugLevelAdjustKeyModifier set to Ctrl alt or Shift applet parameters inside the HTML page When not specified the default key combination is ALT d This feature is useful for debugging resource problems in the Java client The user can start the session with debug level 1
26. to support configurations that are no longer supported by their vendor ACE The ACE interactive development kit has been tested on the following operating systems Windows XP Professional SP3 Windows 7 Windows 8 1 Clients The Java Client has been tested on the following operating systems browser and Java versions e Windows 7 e Windows 8 1 Browser JRE IE 8 11 Oracle 1 7 0 Firefox Oracle 1 7 0 Chrome Oracle 1 7 0 Detailed Description of Version 9 2 1 5 6 When using Java 1 7 0_51 and higher all the components of the Java Applet has to be packaged into Jar files and digitally signed This process is explained in the Runtime Installation section However during development you may configure the Java JRE so that it is not necessary to package and sign all class files and resources as explained below When launching the Java client in the development environment for the first time you are prompted to download and install the Java JRE from the Java com web site After installing the Java JRE 1 7 0_51 or higher and launching the client Applet you ll receive the following error message Application Blocked by Security Settings Name appls MOBILE user Applet Location http localhost 8080 Your security settings have blocked an untrusted application from running The reason for this message is that the class files and resources generated by the Generate Runtime proces
27. user defined Theme class lt PARAM name ThemeName value UserDefined gt lt PARAM name UserDefinedThemeClassName value Fully qualified name of the Theme class gt To learn more about implementing project specific look amp feel we recommend 1 Reading the JavaDoc for interface cst gwt general UIManager and for class cst gwt general DefaultTheme in the JIS client Java Doc located in JacadaFiles Docs Client 2 Reviewing the sample theme classes provided as part of the JIS samples located in JacadaFiles samples features themes These user interface improvements include Mouse rollover mode Controls such as arrow buttons scrollbars checkboxes and radio buttons will now change their look when the mouse rolls over them This feature is only enabled when a Theme name is defined Mouse wheel support Mouse wheel support is incorporated into window scrollbars and table scrollbars when using cached tables This feature is only enabled when using JDK 1 4 and above Software AG Arrow buttons and scroll bars The arrow buttons used in prompts combo boxes date fields and scroll bars are now displayed using a more modern look amp feel Rounded rectangles for group boxes and frames Group box frames and tab headers now support rounded corners This feature is only enabled when a Theme name is defined Calendar control The calendar control s look has been improved Client persistent s
28. written back to the client Therefore this value includes any think time caused by the host and the communication between the server and the host but does not include any think time caused by the client browser or communication between the client and the server Typically a value of more than 2000 2 seconds indicates a performance tuning problem stat transaction count the total number of transactions since the server was started Use this parameter to evaluate the total load on the server and to make sure work is equally distributed between servers in a multi server configuration this parameter is not implemented when deploying the application as an ear file Stat transction per minute the current number of transactions per minute Measuring this parameter is especially important during peak hours and during server loadtest You can compare the value of this parameter with the Software AG benchmark results this parameter is not implemented when deploying the application as an ear file The new performance indicators are exposed in the following configurations Standalone JAM JAM in J2EE JISAdminServlet JMX and Java code acting as a JMX client Software AG Note that a JMX enabled monitoring tool may monitor these parameters over time and allow you to chart the data and define alerts Localization Improvements The following localization improvements have been made to Java Client localization support Anew parameter for spec
29. 0 ee ee eeeeeeeceeseeeeecseecsaecsaecseceaeceseesseeeseeseaeseaeesaeeeaaecsaecaeonaaes 18 Support Underline and Strike through Font Attributes 00 0 ceeeceseceseceseeeseeeeeeseneesaeesaeecsaecsaecsaecsaecsaeesaeeees 19 Solaris KIM A Bande A EARE 19 Jetty Http Tbread pool Mont Mia A e i 20 Server Business LOBA 20 O ANA 20 Server Remote Manage Metric a ae drets 21 Remote Debug ein g sti iii 22 BINZAME DIA O a e O e O a e ueatece 23 Mobile Demo WebSite in il RLU eee a 23 Logging Improvements mitin dra 24 Detailed Description of Version 9 2 L FIXKES A tas 24 DET VEL a a O A T ts A A ERE KAE NO 24 Java Client niiin pi s i a A a e ie 26 Atl E aia 27 aN E E A A E ds ETE A A 27 Limitations OF Version A namra nena in dyke RA chante wae oc de dy tu i le a 27 New Features TA NS OM IA 28 JIS Summary of Changes Document for Version 9 2 1 1 Running the Server using 64 Dit Java ee cescesccssecesecesseseseeeseeeseecsaecsaecsecssecsseesseesseesseeseseeeaeesaaeesaeeeseeenaeenaee 28 Application Verifier smart aid 29 Simplified Web Application Deployment eee eseecssecsseceseceseceseceseeeseeeseeseseceaeeeseecaaecaaecsaecaecnaeenseeesaeenaeens 31 Mobile Device SUPpottei at la Sa wat eer eee 32 Simplifying the use of the LoadTest Applet 0 0 0 cece esecssecssecsseceseceseeeseeeseeesneseneseaeeeseecaaecaaecsaecsaecsaeenseeeseeenaeens 33 Support for Keyboard buffering ui ita 34 Upsrading tO JS LI aa e e EE E E TENE EA A EE TEE E E E RE e eaw
30. 1538 fix infinite loop in screen interpreter Changes to the screen interpreter internal object pool were implemented to solve infinite loop problem 5103216 JIS 1358 JIS 1359 Checkbox translation failed when using empty settings A problem related to the configuration of the Localization of Checkbox Values feature has been fixed 5125057 JIS 1528 JIS 1530 ArrayIndexOutOfBoundsException on sendAIDKeysAndWait Screen interpreter fix related to accessing position outside of the screen boundaries JIS 1477 Root node information is not updated in Jam The information related to processes not handling sessions is now updated in the administration utility every 60 seconds JIS 1570 passing data between server and administrator The data sent from the server to the administrator utility is now compressed by the server 1080114 JIS 1553 JIS 1558 production server not connectable The creation of the server sockets used for Java client communication is no longer performed in parallel to prevent problem of two server sockets allocating the same port 1072189 JIS 1480 JIS 1488 Problem when the first session does not complete its initialization The first session started on a server process performs some data structure initializations These data structures are later used by all other sessions Therefore if the first session fails to initialize these data structures other sessions fail to start Some specific scenarios relat
31. 25 Cp1251 Slovak Slovak Cp870 Cp1250 Slovenian Slovenian Cp870 Cp1250 Spanish Spanish Cp1145 Cp1252 Swedish Swedish Cp1143 Cp1252 Swiss German SwissGerman Cp500 Cp1252 Thai Thai Cp838 MS874 Turkish Turkish Cp1026 Cp1254 Ukrainian Ukrainian Cp1025 Cp1251 Comments e The EBCDIC Codepage is being used by the server when converting information sent and received from the host into an ASCII encoding e The ASCII Codepage is being used by the server when converting ASCII encoded bytes into Java characters encoded using Unicode e All information sent and received between the clients and the server is encoded using Unicode encoding e For extension developers to obtain the descriptor class name from the Class Name Prefix append the string LanguageDescriptor to the prefix e Belorussian also refers to Belarussian and Slovenian also refers to Slovene Software AG e The matching AS 400 CCSID can be obtained by looking up the EBCDIC Codepage for a specific language descriptor in the following link http publib boulder ibm com infocenter iseries v6r1m0 index jsp topic rzaha fil eenc htm e Follow this link for a list of codepages supported by Java http download oracle com javase 6 docs technotes guides intl encoding doc html Note Customers can implement their own descriptors by extending the existing product descriptors Example package appls IT server user public class UserItal
32. 5071805 JIS 1206 The product logger no longer implements the java lang Object finalize method as this caused problems when running multiple sessions from the same Applet SI 5091782 JIS 1286 A problem related to printing the host screen has been fixed XHTML SI 5085238 JIS 1243 When a user updated a table cell then placed the focus on the table on a protected table cell and pressed a function key the server processed two cell changed events 1 for the changed cell 2 for the focused cell This caused a warning about trying to update a protected cell This scenario no longer causes a warning JIS 1222 When setting a value to an editable combobox table cell the combobox value was not updated in the host Limitations for Version 9 2 SI 5072258 JIS 1135 When the character 0x1A Ctrl Z appears within the code of a BMS or MFS file the SDF parser considers it to be an end of file character and therefore aborts the processing of the file without creating an SDF file Workaround Manually delete the Ctrl Z unprintable character from the BMS or MFS file SI 5077748 JIS 1187 Within the system triggered method UserDestroySubApplication when accessing a specific variable using an expression line or using the GetVarValueByName DoMethod the variable value is retrieved from the current subapplication and not from the destroyed subapplication In order to access variables of the destroyed subapplication users should update the s
33. AG When all of the operations run successfully without errors no user intervention is required So for instance the Generate Runtime process dialog still opens but closes automatically when it is done If however there is an error message such as an alert about missing image files then this message is shown and the user needs to click OK to close it For more information see ErrorHandling Once a valid buildapp xml file has been created and tested the operations run in ACE without the need for user intervention Changes in the Behavior of ACE Operations The following sections describe changes in the behavior of ACE operations when using automatic mode Changes in Generate Runtime The Generate Runtime process is always carried out for the entire application It is not possible to specify specific libraries or subapplications To speed things up you can use the option to compile only new and modified subapplications Changes in Create Runtime Installation with Wise After creating a runtime installation with Wise ACE asks whether to launch the newly created installation In automatic mode this question is skipped and the installation is not launched Changes in Pack When packing an application it is possible to select the libraries to pack and to add additional files but the other steps of the Pack Wizard are not supported Thus for example it is not possible to specify a maximal file size nor to skip input d
34. Browser communicates with the server using Https using the RedirectionProxy servlet e A web page or other mechanism is defined for posting user credentials to the server using an Http POST request Example of credentials entry page lt html gt lt form action XHTML JacadaApplicationName MYAPP method post gt lt input name user gt lt input name password gt lt input type submit gt lt form gt lt html gt The signon process works as follows e Initial connection from the browser to the redirection proxy is implemented using a POST request e Redirection proxy connects to the root process and then redirects to the worker process e Data posted by the browser to the redirection proxy is now posted again to the worker process this is the new behavior which did not exist before e Worker process maps the posted data to shared user variables e Once the connection to the mainframe is established the data posted by the browser is typed into the mainframe signon screen to perform the signon operation To improve performance it is now possible to configure the redirection proxy to bypass itself after the initial signon is performed This way the redirection proxy is used only for the initial connection and is then bypassed by the client which connects directly to the worker process for the lifetime of the session To configure this option add the following jacadasv ini setting RedirectionProxy BypassAfte
35. Defining the device name template to allow generating meaningful but unique device names based on the workstation username or computer name 3 Gracefully handling of device name collisions Explanation 1 The client can now specify the device name template using the lt PARAM name DeviceNameTemplate value gt Applet parameter which will override the value of the LUName ini setting This allows for specific clients to specify specific device name templates based on workstation specific information 2 In addition when using the 5250 protocol the user can now specify a device name template which includes wildcards characters The wildcard characters are automatically replaced by random letters or digits by the server before attempting to connect to the host thus significantly reducing the chance for device name collision For example if the client specified a device name template MYDEV in runtime JIS will connect to the host using a device name such as MYDEVX5D or MYDEVAGS i e the last 3 wildcard characters were replaced by random letters Furthermore if the device name template is specified by the Java client DeviceNameTemplate parameter see 1 The following substitution parameters can be specified C C U U The substitution parameters are composed of 3 characters First character is a percent sign indicating a substitution parameter 2nd character is a case insensitive parameter the possib
36. H System Status Log Descriptor Name JMX Support The JMX technology provides the tools for building distributed Web based modular and dynamic solutions for managing and monitoring applications By design this standard is suitable for adapting legacy systems implementing new management and monitoring solutions JIS now enables performing administration activities including session monitoring application configuration and server operations using JMX previously these activities were available only via the standalone JIS Administrator tool This allows data management and data viewing using monitoring tools which support JMX such as JConsole and or by writing dedicated Java code In order to use JMX enable the XML server in the jacadasv ini file LogClasses XMLServer XMLServer Enable 1 TimerTick Note JMX is supported only when running the standalone JIS Server and not when using J2EE deployment Software AG MBeans are managed beans Java objects that represent resources to be managed Data shown and managed in the standalone JIS Administrator tool is exposed by creating matching JMX s MBeans All the MBeans exposed by JIS are defined in the object name root com jacada jis runtime server log StatusAgent and are categorized according to the data and operations they expose Following is a detailed list of the configuration data and administrative operations exposed using JM
37. Improvements Mixed code warning displayed by all versions of JIS when using Java 1 6 0_19 and higher is no longer displayed The clfull signed jar and clbase signed jar files are now digitally signed and time stamped hence their signature will continue to be valid after the certificate used for signing the files has expired The following limitations have been removed when running the Java client as an application 1 Link controls are now operational for activating methods but not for opening a browser URL 2 The params txt file is no longer locked for editing while the application is running GUI Printing improvements Images in popup windows are now printed correctly Some deprecated APIs have been replaced and logging messages have been improved New Features in Version 9 1 66 WebSphere 7 Support JIS has been tested using WebSphere 7 0 0 11 on Windows 2003 Deploying a JIS application into WebSphere 7 requires additional configuration Copy all the jar files from lt JISCommon gt lib to lt WAS_HOME gt lib ext this operation should be repeated every time the JIS common installation is updated Add the following argument to the Generic JVM arguments field in the Java Virtual Machine setting panel DJacadaCommonDirectory lt Installation directory of JISCommon gt see attached example Software AG Cell IL OAAPEWEB O1Node03Cell Profile ApcSrvO3 Application servers Application servers gt server
38. P gad C jis appls MYLIB 1lib SUBAPP gad xml created Mobile Demo Web Site The JIS mobile demo web site https apxdemoenv softwareag com has been upgraded to V9 2 1 and the following fixes were introduced e Username and Password fields on the Signon screen are now using the Html5 lt input Detailed Description of Version 9 2 1 23 placeholder text gt attribute to provide place holder text Back link from the Signon screen to the welcome page has been implemented The dangling button problem on the main menu has been fixed Table right click menu is now placed correctly Site has been re branded according to the Software AG official guidelines Logging Improvements LOCALIZATION debug filter is introduced For the Java client it has the same functionality as the localeDebugMode Applet parameter For XHTML it provides diagnostic information related to localization resources JavaScript logging is now operational and additional diagnostic information is now logged both to the browser JavaScript console if supported and enabled and to the server log Detailed Description of Version 9 2 1 Fixes 24 Server 1071275 JIS 1469 JIS 1484 Invoke UserDestroyApplication on unexpected disconnect UserDestroyApplication is a system trigger method invoked by the server just before closing a session Its purpose is to allow project specific code to perform last minute cleanup before a session is closed Typically this involves gracef
39. Product JIS Released May 2014 Release Notes for Version 9 2 1 Contents of Version 9 2 1 Installation amp Upgrade Information 5isis 2 scdassccssadssencdcnsasacsaneacassdedas seed vacevduatavesecaeneesedaanausiadevensdcncanncdadannceane 5 Supported Platforms ii eae niece A Reese MA eae i aan 5 Recommended C ntis rat onse ici A ened beet thes 5 ACE ie ea 5 CHEMIE iaa rE E A ie 5 Standalone Server O 7 Application Server Deployment tt ii a A A A R A A a eal i 8 05400 Components ini ada 8 Upgrade Instruir AAA rain tia 8 Retirement of Product Components ese seessecssecssecsseceseceseceseceseeeseeesseeeseeeseeesaecsaecsuecsaecaecssecesaecsaeceaeceeeeeneseaee 8 New Features 1n Version 9 2 lia ii bd 9 Runtime Installation Leas Mal eet a ees 9 Enhanced Java Client Packaging Procedure ooococononcconncoonnnonnnnnnnnnncnnnonnnono nono no nono cn nn conca nnnn naar ran rnn crac ran arrancan 12 Parameter Substitution in Html Launcher Page ou ee ee eeseeeseeeseecscecsseceaeceseceseceseesseesseeseseseneeesaecsaeenaecsaeenaaes 14 Pass Through Gateway sisas 15 View Host Screenin AO ti A A teas aes teats ee hoe AE 16 Simplify Redirection Proxy Configuration cece eseesseessecssecssecsseceseceeceseesseeseaeeeseeeseeeaaecsaecsaecsaecsaeesseeeaeenaeee 17 Secure Single Signon Implementation using Redirection Proxy 0 0 0 cee ceeeseseeeeseeeseeeeeceecaecaeceseceseeeseeesaeenaeens 18 Proxy Servlet to Server Direct COMMUNICATION
40. X System Status Log combines read only information for JIS servers processes applications and sessions The information encompasses the same attributes shown in JIS Administrator s properties tables and is sorted in the same hierarchical tree like topology Root gt Servers gt Processes gt Applications gt Sessions Running Sessions lists information about the currently running sessions displayed as a list and allows executing operations such as closing sessions and changing the debug level for a specific session Debug contains editable settings that are included in JIS Administrator s Debug panel Debug level Log file size Number of log files and Log directory The Debug MBean also exposes operations such as placing a message in the log file clearing the log file and saving the debug settings to the ini file for future use License contains read only attributes that are shown in JIS Administrator s License panel Also allows replacing the current license file by specifying the location of a different license file Runtime configuration allows setting the application s ini file configuration as done in the JIS Administrator s Runtime Configuration view The data is sorted in a hierarchical topology each application deployed on the server includes MBeans per each of the application s configuration sections each of the sections includes a set of editable parameters Command line operations allows performing the same operation
41. ailed Description of Version 9 2 1 3 New Features in Service Pack 9 0A07 woe cceccccecccccccccsssssssceccccceesssssssesccscsssssseusscsscesesseeseasceccesseeeuens 107 Refreshing the XHTML Client When a Page on the Host is Updated eee ceseesseceseceneceseeeseceseeeseeeeneeeaes 107 New Peaturesdn service Pack DA Dri aire 108 Support tor Keyboard BUEN it A A A A A A eee 108 New Peatires in Service Pack DAD AA a 109 API available to trigger server methods cee eesceseceseceseceseeeseeeeneeeseeeseeesaecsaecsaecsaecaeceseeeseesseeeseeeeaeesseeeeeeeees 109 Printing A hee cased deni eae es pce eevee 109 New Features 11 Service Pack 9 OA0 2 cui dicci n 110 Enabling reconnecting to a database after the connection or session fallS oononncnnnccnnccnocononaconaconnconncnnnananonnnos 110 Limiting the size of the server log HES cocaina diet 111 New Peatures n Service Pack O DADD a 112 Enable opening a window in a maximized State oooonncccnoccccnonanononononononononononacnnoconnnnnr nono cnnn non nn nro nn anna nc cnnncannnna ns 112 Deployine a service to aJ2BB SV A A ta iR 112 New Features in Service Pack 9 0A00 iieiea n ni a E A E e 113 XINIT keyword in BMS maps now supported 00 0 cee eececssecseceseceseceseeeseeeseeeeeeeeseeeseeesaecsaecaecaeenseesseeseeeeeeeees 113 Maximum permitted size of ACE method increased 0 0 0 eesessecsseceseceseceseceeeeescesseeeeneeeseecsaecsaeceaesaecnseenseenes 113 Print setup dialog canbe skipped
42. an be obfuscated e storetype keystore type as specified by the Java keytool utility e tsa fully qualified url of the time stamping service optional Time stamping your Jar file at the time of signing ensures that the signature will never expire e alias the alias of the code signing certificate Example MakeJar jarsigner 1 Keystore c sign mykeystore pfx storepass OBF 118mlirzlge513enlghtliunli9d storetype PKCS12 tsa https timestamp geotrust com tsa Detailed Description of Version 9 2 1 13 14 alias 972e90db cbbd 4bfc 80af fbla6f39292a For more information about the keystore storepass storetype tsa and alias parameters consult the documentation of the Java JarSigner utility For more information about creating obfuscated password for use as the storepass parameter see the section Secure Login to JISAdminServlet in the product release notes Parameter Substitution in Html Launcher Page JIS client sessions are launched by pointing the client browser to one of the following Html pages lt AppName gt html launches a Java client session lt AppName gt xhtml html launches an XHTML client session It is now possible to add dynamic server based data to these static Html pages Inside the Html page used for launching the JIS session specify substitution parameters in the following format lt context gt lt property gt Where lt property gt is the case sensitive name of a property or parameter a
43. and only increase the debug level when a problem such as slowdown is observed Post Class Path This allows running the JIS server with an additional set of jars It is possible to add an extra token to the classpath which is appended at the end of the default JIS classpath This is done in the jacadasv ini file where you can set within the VMCommandLine section the PostClasspath setting to list all the required jar files which are not part of the JIS default classpath Example VMCommandLine PostClasspath c jdbc jdbc jar myapp jar New Methods for Handling User Variables The following DoMethods were introduced DoMethod Receiver System Method logSharedUserVariables Parms lt debug level gt DoMethod Receiver System Method logUserVariables Parms lt debug level gt Detailed Description of Version 9 2 1 85 86 The following public APIs were introduced Retrieve all user variables return Map of variables in key value pair format yf public Map getUserVariables print to the server log file all user variables param debugLevel variables will be printed when the server log debug level is equal or higher than debugLevel e public void logUserVariables int debugLevel Retrieve all shared user variables return Map of shared variables in key value pair format if public Map getSharedUserVariables print to the server log file all shared user variables
44. anges should have no functionality impact A warning message is logged to the server log whenever a method is invoked in runtime not from the session thread since this may result in a race condition Make sure ACE methods are never invoked from a separate thread by a Java extension Backward compatibility The following XHTML Java extension APIs are now deprecated and should be replaced as follows e OnPageSubmitContext getPostData is now deprecated and should be replaced by getPostDataMap which returns java util Map lt String String gt object e Window getAllControls is now deprecated and should be replaced by getAllControlsList which returns java util List lt XhtmlControl gt object e Window getControlsByType is now deprecated and should be replaced by getControlsListByType which returns java util List lt XhtmlControl gt object You may continue to use the deprecated methods at the expense of creating a new Hashtable or Vector object on each invocation IE10 IE11 With the introduction of IE10 Microsoft made extensive changes to adapt its browser to the same level of standards support as Firefox Chrome and Safari By doing so they reduced backward compatibility with previous versions Software AG A year later IE11 has introduced several additional changes which made it even more standards compatible and less compatible with previous versions of IE For desktop environments the introduction of IE11 made IE10 obsole
45. anguage used by the client using the following Applet parameter lt PARAM name LanguageDescriptor value lt Language Name gt gt 2 Make sure the client operating system supports the language specified in its Regional Settings and that the language specific fonts if there are any are installed 3 When using Chinese Japanese Korean or Thai add the clcharsets jar file to the ARCHIVE tag and the clcharsets cab file to the Cabbase parameter in the launcher Html page If you are using one of these languages and the clcharsets archive is not added this will cause the LanguageNotSupported html page to be presented when starting a session 4 When using some languages such as Japanese Chinese or Thai the default fonts used by the JIS host screen and the JIS JITGUI sub application do not display the screen contents correctly Instead you may see square signs or question marks To fix this experiment with the following Applet parameters lt PARAM name CourierFontType value Courier gt to control the font in the JITGUI and dynamic areas lt PARAM name EmulatorFontName value Courier gt to control the font used by the Host Screen XHTML Client 1 Specify the Language used by the client using the following URL parameter or post data or Http header LanguageDescriptor lt Language Name gt Note that you cannot pass this parameter to the lt AppName gt xhtml html You either have to code it in the lt
46. annot be reordered e When using fixed columns the fixed columns cannot be reordered Detailed Description of Version 9 2 1 103 104 Table row sorting When using fully cached tables it s useful to sort the table data by column This is now possible by clicking the column header of the column to be sorted Clicking the column header once sorts the table by ascending order clicking again sorts the table by descending order In order to return to the original host row order you must reload the table This feature is of limited use for most host tables since on normal tables it only sorts the current table page To activate this feature add the following Applet parameter lt PARAM name AllowTableRowSorting value true gt Sorting order is not maintained after exiting the current screen Known Limitations e Heavy weight controls such as non transparent frames do not comply with the new look e Multiline labels are based on the java awt TextArea component which draws its own scroll bars and therefore cannot be adapted to the JIS look and feel Additional Enhancements Accessing the application server s HTTP session from an XHTML extension ATL 27368 It is now possible to access the application server s HTTP session from XHTML extensions Get J2EE sessionId return sessionid El public String getSessionld pk Binds an object to this session using the name specified iv public
47. arate Java process Instead the Node Registry now runs within one of the other server processes This change improves startup time and removes the need to specify the path to the jacadasv policy file using the Djava security policy flag Server quit time was reduced by approximately three seconds The Administrator tool now displays the Integrator 1 0 process immediately after it is fully started Previously the Integrator process only showed up in the monitoring tool 60 seconds after it was fully started Monitoring Improvements A JIS server deployment is comprised of one or more JIS work processes Each process represents a Java virtual machine operating system process The JIS administrator utility is now able to provide environment and performance indicators related to the underlying Java virtual machine Use these indicators to monitor the status of the underlying Java virtual machine New process attributes Software AG JIS Administrator Windows Internet Explorer http localhost 28080 I1SAdminServlet Ve de Gs administrator a dh gt Ep Page Tools ystem Status Log Properties Sessions Debug License 0 64 21 4 Property P p oO 77m Alias Http Port Https Port ld Java Port1 Process id Stat Memory free Stat Memory total 104064 Stat Memory xmax 197248 Stat Thread current 78 Stat Thread peak 95 State STARTED
48. ath of these links should be added to GatewayMappings section see for example the w3c css mapping in the example above which enables the w3c web site to locate its CSS files using a relative path 2008 which passes through the JIS gateway to url http www w3 org 2008 Limitation JIS cannot serve as a gateway to any site sites that rely on advanced web technologies or advanced encryption technologies might be incompatible with the gateway functionality View Host Screen in Xhtml When using the Java client users were always able to view print and save the emulator screen We have now introduced this functionality into the XHTML client To enable XHTML users to view the host screen add the following runtime ini setting Xhtml ViewHostScreenEnabled 1 When setting ViewHostScreenEnabled 1 a new View Host Screen button is added to each sub application page at the bottom right of the web page Clicking the new View Host Screen button displays the View Host Screen page in a new browser tab The View Host Screen page presents a read only snapshot of the current host screen The left pane of the View Host Screen page contains the following widgets Show Line Numbers checkbox toggles line number display on the host screen Show Attributes checkbox toggles field attribute display Input attributes are marked with the symbol output attributes are marked with the amp symbol Refresh button u
49. ble click using double tap functionality e Replace the product calendar component with the Native iPad calendar widget Note the following are recommended best practices when running the XHTML client using Safari Mobile on an Apple iPad e Using the iPad in landscape orientation is recommended rather than in the default portrait orientation e The built in auto correction feature can change the data entered incorrectly therefore it is recommended to turn off the Auto Correction feature Settings gt General gt Keyboard gt Auto Correction gt OFF e When typing in a field on the web page using the on screen keyboard the most intuitive way to commit editing changes to a field is to press the lt Go gt button however this button also submits the form to the server using the first lt Submit gt button on the form which in some cases may even be the lt Exit gt button To avoid this from happening never click the lt GO gt button instead make sure you navigate between the input fields using the lt Next gt button and close the keyboard using the lt keyboard down arrow gt key To make the windows and table right click menus look good on the iPad add the following code extension to src appls lt AppIName gt xhtml Appl java public void onPageLoad OnPageLoadContext context context getWindow setRMBMenuBackgroundColor White setR context getWindow enuForegroundColor Black context getWindow setR enuFontNam
50. buffering functions e Keyboard buffering should replace existing Java client code extensions which provide keyboard buffering functionality e Manipulating key events or focus events using Java extensions can adversely impact keyboard buffering e Buffering key events starts after the display of the first window Backward compatibility Software AG Customers who used the Keyboard Buffering feature in previous versions using a runtime license should add the following Applet parameter to enable it in this release lt PARAM name EnableKeyboardBuffering value true gt Upgrading to Jetty 8 1 5 The internal Jetty web server has been upgraded to version 8 1 5 in order to utilize the latest security and performance enhancements Localization of Checkbox Values This feature affects customers converting the application in English and localizing it to various languages using the localization resource file specifically when representing checkbox values using the host locale For example an English Y N checkbox can be translated into S N in Spanish and O N in French on the host application These translations are now supported using the new ini settings in the following format CheckboxStateTranslation unchecked checked y 0 Y 0 intermediate The example above assumes that the checkbox is designed to represent checked status as Y while the host application represents checked value as O therefore the checked va
51. can attach to Java processes running on the local machine in order to monitor its performance However in order to monitor a server from a remote workstation each of the Java server processes has to listen on its own remote JMX port Specifying the JMX port using the JavaOptions setting of jacadasv ini does not work since multiple processes will try to listen on the same port and thus fail to start The solution is to define the following jacadasv ini settings VMCommandLine JmxRemoteMonitoringStartPort lt port number gt The server would then increase the port number for every spawned process to prevent more than one process from allocating the same port For example When setting JmxRemoteMonitoringStartPort 3333 Detailed Description of Version 9 2 1 21 22 In a single process server the root process allocates port 3333 for JMX communication In a multiple process server each process will allocate its own JMX port Process 1 0 port 3333 Process 1 port 3334 Process 1 1 ports 3335 Process 1 2 ports 3336 The JMX remote connection provided by JIS does not require authentication or encryption Under the hood the following Java system properties are specified in the Java command line Dcom sun management jmxremote port portNum Dcom sun management jmxremote authenticate fals Dcom sun management jmxremote ssl fals To connect remotely to a JIS server process using the tools provided by the Java JDK Insta
52. cessing Document staticXmlFromSession Document context getSessionAttribute staticXml NodeList nl staticXmlFromSession getChildNodes Debug print 1 staticXml from HttpSession nl item 0 public void onPageSubmit OnPageSubmitContext onSubmitContext Known Limitations The new APIs cannot be used from onPageSubmit XHTML Date control enhancements EU 05423 1 The calendar window default style Detailed Description of Version 9 2 1 105 106 The default style for the calendar window can be overridden from an external CSS file calendar css The calendar css is created during runtime generation process in the appls lt APPLNAME gt xhtml CSS By default the file consists of only one line comment to allow browsers to cache it For example if you want to increase the font size of the day numbers in the calendar window you can do it by defining a CSS definition day font font size 150 Following is a list of CSS class names in the calendar window currentDay class name for current day weekendDay class name for weekend days day class name for all other days weekday class name for the titles of the week days Sun Mon currentDate class name for the current date title August 2007 2 It is now possible to use the character as a date separator 3 The default date format is selected according to the browser locale Displaying digits in Java Client spin box contr
53. completely eliminating the message box using an XHTML extension For Example file src appls lt app name gt xhtml user Appl java public void onPageLoad OnPageLoadContext context Window window context getWindow XhtmlControl control window getControlByName messageBoxText if control null if control getText equalsIgnoreCase Test message box control setText This extension will remove the message box if it contains the text Test message box by changing its text to Menus in XHTML ATL 28670 Infrastructure has been added to create a menu bar using in an XHTML extension New Features in Service Pack 9 0407 Refreshing the XHTML Client When a Page on the Host is Updated The client oriented architecture of HTML means that requests always originate from the client A state change on the host such that the host updates the server with a new screen was not displayed on the client unless the client sent a request to the host Session changes on the host are now pushed to the XHTML client without the client requesting the updated server page A new connection is opened to the server and if there is a screen change on the host the new page is sent to the client immediately Detailed Description of Version 9 2 1 107 To enable pushing pages from the host to the client in the XHTML section of the RUNTIME INI file set the EnableAutomaticServerUpdates parameter to 1 Note E
54. d by one for each server process For example When setting RemoteDebugStartPort 5005 In a single process server configuration the root process allocates port 5005 for remote debugging In a multiple process server configuration each process allocates its own remote debugging port Process 1 0 port 5005 Process 1 port 5006 Process 1 1 ports 5007 Process 1 2 ports 5008 Activating remote debugging Use your favorite Java IDE remote debugging capability and attach to the specified port Under the hood the Java command line parameters used by the server are agentlib jdwp transport dt_socket server y suspend n address portNum For more information consult the documentation for your Java JRE and Java IDE BIN2XML Utility One of the main challenges of integrating the JIS development environment with source control tools such as SubVersion is the in ability to compare binary files such as the gad acc and mnu files for each subapplication bin2xml bat is a simple command line utility which streams these binary files into a textual XML format so that these files can compared using external visual diff tools To activate this utility run bin2xml bat from the lt JISRoot gt folder Use the f flag to specify the name of the file you wish to parse into an XML document The resulting XML file has the same name as the source file with xml postfix appended Example C jis gt bin2xml bat f appls MYLIB 1ib SUBAP
55. d using an AS 400 host is still supported In order to simplify migration the Wise related functionality can still be used but is no longer maintained Creating the IzPack runtime installation From ACE invoke the Create Runtime Installation wizard The Select Installer Type step of the Create Runtime Installation wizard has a new option Create IzPack installation Select this option and click Next to create an IzPack based runtime installation Create Runtime Installation Wizard Select Installer Type Select the runtime installation product used for creating the runtime installation Installation Type The IzPack installation is the recommended installer for new applications C Create Wise installation The Wise installation remains for backward compatibility since the Wise product is no longer supported by its vendor Only select the Wise installation in case you purchased the Wise porduct in the past and customized the default installer stet The rest of the wizard steps are similar to the Wise installation steps Finish the Create Runtime Installation wizard to package the runtime installation Packaging related messages are logged to the console window Detailed Description of Version 9 2 1 9 10 Adding native library ShellLimk dll Adding native library ShellLink_x64 dll Adding content of jar C 3IS921B29 JacadaFiles utils IzPack bin panels HelloPanel jar Adding c
56. d the following setting Program Libraries lt semicolon separated list of libraries gt If you do not have any libraries then the list should just contain the name of the application For example Libraries TEST for an application named TEST Detailed Description of Version 9 2 1 101 102 e Do not use comments lt This is a comment gt in the buildapp xml file e When the packaging of the J2EE runtime installation fails remote log still reports successful completion e When using the command line interface if you set the NewAndModified attribute to 1 the first time you generate runtime the compilation fails The first time you compile you must not use NewAndModified Improved User Interface Introduction The JIS Java Client user interface has been improved to create a more modern look and feel for the JIS Java components and to improve the table components functionality Note Excluding the mouse wheel support explained below all of the other features are disabled by default in order to maintain backward compatibility To enable the new JIS look amp feel add the following Applet parameter lt PARAM name ThemeName value default gt In addition JIS now offers the ability to customize the look amp feel per project specific requirements To achieve this users will need to implement the UIManager interface or extend the DefaultTheme class Setting the following Applet parameters activates a
57. d to the server and correctly logged to the server log by default The server log now identifies the Linux operating system The product now represents debug filters internally using a java lang Enum instead of the old implementation which relied on String constants Therefore when using Method Debugging it is required to generate the runtime again and when using code extensions which utilize debug filters this code will need to be re compiled This operation is performed once after updating the version Detailed Description of Version 9 2 1 53 54 Proxy Servlet Improvements When accessing the servlet monitoring page using the URL JISProxyServlet the list of active connections is now printed to the server log This can be useful in order to compare the number of open connections displayed by the proxy servlet with the number of open sessions displayed by the JIS Administrator Open the server log and search for List of open server connections Updated JIS Perl to Version 5 12 2 0 The Perl distribution used by JIS has been updated to Strawberry Perl 5 12 2 0 Session Dump Improvements The following improvements were made in the session dump mechanism 1 On the Java client the dump is now printed to both the Java console and the log file 2 On the server the dump can be turned off completely using the following runtime ini setting SessionCoreDump IsEnabled 0 3 Additional exceptions are now recorded in the du
58. default Natural function keys line This mode is compatible with the screen images generated by the old mainframe based Natural parser 2 DYNAMIC the screen images contain prototype information and the actual function keys are created in runtime this mode is more flexible and supports most function key layouts Use this mode when creating a new application The type of function key lines displayed in the screen image is controlled by the following specific ini setting NaturalParser PFType STATIC or PFType DYNAMIC Software AG The default value is STATIC however new applications are created with the value preset to DYNAMIC Displaying function keys using the STATIC option When using the STATIC option the natural parser displays the following line exactly 2 rows from the bottom of the screen line 22 in model 2 screens Enter PF1 PF2 PF3 PF4 PF5 PF6 PF7 PF8 PF9 PF10 PF11 PF12 In runtime JIS expects this line to appear as is or else the screen won t be identified Use the Static function key layout when using Natural maps for existing projects which relied on the old mainframe based JIS Natural parser In this scenario every map based screen image needs to be combined with a corresponding screen capture in order to overlay the function key descriptions one line from the bottom of the screen line 23 in model 2 screens In order for the static keys pattern to be analyzed correctly all of the st
59. e The reset key code Pressing the specified key resets the playback buffer Valid codes can be obtained using KeyEvent getKeyText lt Virtual key code gt KeyboardBufferingResetKeyModifier Shift Reset the key modifier Valid codes can be obtained using 108 Software AG KeyEvent getKeyModifiersText lt Virtual modifier gt true Set this parameter to false to HideKeyboardBufferingToolbar show the keyboard buffering toolbar when testing the application Known Limitations The following limitations influence how keyboard buffering functions e The product s keyboard buffering feature must replace existing extensions that provide keyboard buffering functionality e Replace every occurrence of JacadaStarter activate true API in the client extensions to JacadaStarteractivate false e Manipulating key events or focus events using Java extensions can adversely impact keyboard buffering e Buffering key events starts after the display of the first window New Features in Service Pack 9 0405 API available to trigger server methods An API is now available to enable triggering a given method on the server directly from the Java client without the need to trigger a menu item button or accelerator linked to the method Activate method on the server by trigger id The trigger id can be obtained as follows For subapplication specific me
60. e Helvetica context getWindow setRMBMenuHighlightColor Blue MenuHighlightTextColor White B B context getWindow setRMBMenuFontSize 12 Y B B context getWindow setR 32 Software AG You may further adjust these settings according to your preferred application look amp feel Limitations e Function keys are not supported when using a mobile device therefore if you don t have a button or Commands menu item for a specific function key you cannot execute it e Due to differences in the iPad screen size and the browser size and to the fact that the iPad does not show scroll bars some screen content is not displayed though it does exist and can be reached using a drag gesture Simplifying the use of the LoadTest Applet The Loadtest Applet is a component used for load testing the JIS Java and XHTML clients This component provides the only available mechanism for load testing Java client applications and it can also be used for load testing XHTML applications In previous versions of the product the loadtest Applet required a Jar file which was not included in the product installation This is no longer the case For detailed instructions please contact our support team The following improvements were made 1 The Loadtest Applet is now packaged into the standard client JAR files so that it is no longer necessary to use the separate loadtest jar in order to run a l
61. e SUN and IBM Java VMs are supported Setting up HTTPS Communication between the XHTML Client and the Server For XHTML users HTTPS communication is enabled once the JettyKeyStore has been created and the SupportHTTPS 1 setting is defined in the Http section of jacadasv ini HTTPS communication works by default by accessing the server on port 8443 and using the following URL https lt Server Address gt 8443 lt AppName gt xhtml html Note that the browser will show a browser specific warning related to the website security certificate For example Internet Explorer 7 will show a page titled There is a problem with this website s security certificate Ignore these warnings and continue to the web site in order to establish an HTTPS connection For explanation of how to eliminate the warning see the Browser Certificate Warning when Connecting to the Server section below Setting up HTTPS Communication between the Java Client and the Server Java client users using the Applet parameter lt PARAM name UseHttp value true gt HTTPS is enabled once the JettyKeyStore has been created and the SupportHTTPS 1 Software AG settings is defined Https communication works by default by loading the launcher Html page from the server on port 8443 using the following URL https lt Server Address gt 8443 lt AppName gt signed html Setting up SSL Connection between the Java Client and the Server Java client users using p
62. e changes which affect the style of the specific page instance context reOptimizeSubApplication Server Log JIS server log file now uses file renaming when the current log file reaches its maximum size Once the active log file has reached the maximum size limit the file is renamed and the revision number is added to the file name A new log file is created with the original name Example Start the server allowing each server process to create 6 log files of up to 100MB in size Use the following command jacadasv b5 m1i00000000 b5 indicates to the server to keep 5 revisions of each process log file in addition to the current process log file m100000000 value in bytes Defines the maximum size of a single log file to be approximately 100MB As a result when running the server over a period of time the following files are created for the root process 06 27 2010 OSg il F 22 802 414 debug 1 1og 06 27 2010 OS3 il 12 99 999 061 cdsous 1 Rew Los 06 27 2010 05 01 12 99 999 968 debre 1 eva Los 06 27 2010 05 00 P 99 999 878 debug L Revd Los 06 27 2010 059300 2 99 999 968 debe il evt log 06 27 2010 05 00 P 99 999 969 ces Il Rew Los When the size of the debug_1 log file reaches 100MB debug l Revs log is delewedl debug _1 Rev4 log is renamed to debug 1 Rev5 log cele la keys los is renamed to debug 1 evt oc celug 1 key2 los is menemecl to clelowg 1 Jews log clelue levi leg ie mememecl o cleiou
63. e the resource folder if it does not exist and extract its configuration files from the war file to this folder The value of the RootDir parameter can be overridden using the Java command line property DJacadaCommonDirectory lt JIS Common directory gt In addition when using ACE from the command line the following parameter was added to buildapp xml to simulate the usage of the new wizard step TargetRootDir lt Web Application Resource Dir gt Limitations When running as a Web application it is no longer possible to replace the runtime license from the Administrator License dialog box Instead replace the license file in your development environment generate a new WAR EAR file and deploy it to the Application Server Detailed Description of Version 9 2 1 31 Mobile Device Support This release implements the first step towards mobile device support based on the W3C HTML5 specification As there are still many evolving changes in this direction we decided to start by adding support for the Apple Safari Mobile Browser and specifically target large screen iOS devices namely the Apple iPad A demo application demonstrating the supported mobile features can be found in https apxdemoenv softwareag com Emphasis was placed on the following e Safari Mobile running on iPad e Enabling touch capabilities to scroll within tables e Simulate the window and table right click menus using touch capabilities e Implement table dou
64. ecure Socket Extension by default To improve performance when deploying the server to a Solaris operating system use the KSSL operating system service which relies on the operating system encryption kernel KSSL is now supported by the JIS server Detailed Description of Version 9 2 1 19 20 Jetty Http Thread pool Monitoring The following KPIs are now displayed in the process properties panel of the JIS administrator utility e Stat 1 Http Min Thread minimum number of Http threads e Stat 2 Http Max Thread maximum number of Http threads e Stat 3 Http Idle Thread number of idle Http threads waiting in the pool e Stat 4 Http Is Low On Thread this value is set to true when the server is unable to allocate Http threads for new Http requests this is a critical condition which severely affects server response times By default the minimum thread pool size is set to 10 threads and the maximum is set to 200 In certain configurations this number should be increased in the http xml and proxyHttp xml configuration files Use the new KPIs to monitor the Http thread pool behavior Server Business Logic In order to further improve the server scalability usage of the old Java synchronized collections was replaced with the newer unsynchronized collections where appropriate java util Vector objects were replaced with java util ArrayList objects java util Hashtable objects were replaced with java util HashMap objects These internal ch
65. ed from the default applicat ion file so that new applications will no longer be able to use these methods Limitations of Version 9 2 1 JIS 1594 When using IE10 and higher the list of items for an Xhtml combobox may open above the field depending on the position of the selected item Detailed Description of Version 9 2 1 27 New Features in Version 9 2 28 Running the Server using 64 bit Java Starting from this release the JIS standalone server can run using a 64 bit Java version on all 64 bit enabled operating systems and a JIS web application can be deployed to application servers running a 64 bit Java version As of this release we recommend running the server with 64 bit Java We recommend this as 32 bit Java is limited in the amount of memory it can allocate less than 2GB and the number of threads it can run concurrently These limitations effectively limit a 32 bit Java process running on a 64 bit operating system to running no more than 200 concurrent JIS sessions This implies that your server has to sometimes spawn dozens of server processes in order to serve the desired number of concurrent sessions In addition JIS components which can only run in a single process such as the XHTML RedirectionProxy and the Java client JISProxyServlet are limited in the number of connections they can serve When using 64 bit Java the limitations on the amount of memory and the number of threads are effectively eliminated Therefore it i
66. ed to this problem were fixed 5121179 JIS 1504 JIS 1598 Textbox max length set when JIS DoMethod SetVarValueByName used Using DoMethod SetVarValueByName to change the value of an input field which exists only in design view also changed the field length according to the length of the value Detailed Description of Version 9 2 1 25 26 Java Client 5095377 JIS 1378 JIS 1380 printed host screen sometimes lose data The following problems were fixed Distorted host screen printout Blinking cursor stability 5080361 JIS 1193 JIS 1398 Closing Applet When running the client Applet inside the browser frame terminating the session would now display the termination message inside the browser window 5110432 JIS 1416 JIS 1437 Rollover image does not work properly on an image button Button rollover image support was added as part of the Look amp Feel enhancements for the Java client It presents a different image when the mouse pointer moves over an image button as common in many web applications There is no way to define the rollover image in ACE you have to define it using a Java extension calling the setImages API The problem is that calling setImages twice once by the auto generated code or the server and once from the code extension resulted in either missing or incorrect rollover image This has been fixed Sample code to add rollover image to a link control public abstract class ApplSubApp
67. ee 35 Localization of Checkbox Valles titi A A td 35 Optimizing the Mechanism which Searches and Identifies Popup Host Screens oocooconoccnnoconocononcnonaconnconccnnacono 36 Client Specific Device Name Assignment ine inneni iaeiei aini ie oei e aaa ioie pea i 36 Emulator Trace Utilities Integrated into JIS oooconnccinonanaconanonanonanonanonononn nono no nono cnc cnnccnnnnnn nan n ran rnn crac ran coran cra 38 Detailed Description of Version 9 2 Fixes siiviinida idad inician eii 38 O O ON RN 38 SAC A AS AS saa EE ae a 40 Da E AY I EETA A A E AA a Id deta 41 Limitations for Version O Za int A A i ias 41 Appendix Optimizing the Server for 64 bit Java VersiON cooococinocccinnccnonoccnnnancnonononnnononnnoncnnnncrnnncncnannnoo 42 New Features 1m Version Ol La 43 Creating screen images from Natural MapS oooonoccnoncconnconnnonnnonnnonononnnonnncnn nono no nono nnnncnnncnn nan nn nn cra nena crac carac rn crias 43 Simplified HTTPS SSL Configuration nare nenien i E E E EE E E ERE EE E e Ee 49 IPVO SUPDO di A A A cs cadl 52 Specifying a Folder where the Java Client Log File will be Saved ooooonccnnnccnnconocnocnnoonnooncnononnnononoconoconocanccnn nano 53 Logging Messages Improvements ia la ia le a pees eset 53 Proxy Servlet Improvements eiee engens ieee eneee NEE EERE EEE E E EE NE sd EE EEE ERE EEEE GEARTS 54 Updated JIS Perl to Version 5 12 2 0 inea oen init irrita 54 Sesston D mp IMproye ments A a eee eet 54 ACCESS LOBO a ee ee ae 54 Pa
68. efault username password is jisadmin jisadmin Software AG Secure Login to JISAdminServlet When JAM is running as an applet the login to JAM is secured and requires a username and password required when accessing http lt host gt lt port gt JISAdminServlet The username and password can be specified in the jacadasv ini file under the HTTP section using the JAMUsername and JAMPassword keywords The value of the JAMPassword can be written as an encrypted password Generate the encrypted password using the batch file located in lt JIS installation folder gt JacadaFiles utils web jetty encodePassword bat If the JAMUsername and JAMPassword are not specified in the ini file jisadmin is used for both the username and password Note When accessing JAM via Internet Explorer you are required to enter your user name and password twice Example for generating an encrypted password 1 From a command prompt execute C XHTMLV9 utils web jetty gt encodePassword bat mypass UBS lxrellzclimiailua lso Ls MD5 a029d0df84eb5549c641e04a9ef389 e5 2 Add the following setting to jacadasv ini RENTA JAMUsername myuser JAMPassword 0BF 1xfd1zt11luhalugglzsplxfp JIS Administrator Command Line Operations The standalone version of JAM now provides command line interface for performing operations such as shutting down the server suspending connections of new users resuming activity on the server and checking the status of the server
69. eiver ExternalData Method RepairDBConnection Parms iclocsastOOe LO SO 17 orarie E n SIE y MUST O NE SISMO EDG GER 3 DoMethod Receiver 0 Method ExecuteQuery Parms select from sections If Cond 3 1 0 DoMethod Receiver ExternalData Method RepairDBSession Parms 0 3 DoMethod Receiver 0 Method ExecuteQuery Parms select from sections Endlf Do Times 1000 4 DoMethod Receiver 0 Method Next Parms If Cond 4 FALSE Break Else 5 DoMethod Receiver 0 Method GetStringByColumnIndex Parms 1 DoMethod Receiver System Method DebugPrint Parms 1 row 3 Endle EndDo DoMethod Receiver 0 Method Close Parms Limiting the size of the server log files The server can now create a new log file each time the size of the current log file exceeds a predetermined limit The current log is renamed using a revision number The maximum size for the current log before a new log is created is set via the setting RtDebugFileMaxSize When RtDebugFileMaxSize 0 logging is always performed to a single log file unlimited in size There is also a setting for the maximum number of files that a server process is allowed to create The RtDebugMaxFiles setting specifies the number of log files that the server can create
70. entSSLOnly 1 setting on the server side This will force the Java client to use SSL Note the following configurations will prevent the client from communicating with the server JavaClientSSLEnabled 0 and lt PARAM name UseSSL value true gt or JavaClientSSLOnly 1 and lt PARAM name UseSSL value false gt Note The communication method Ports or HTTP s used by the Java client now depends only on the value of the UseHttp Applet parameter The UsePorts Applet parameter has been deprecated Therefore when lt PARAM name UseHttp value true gt is set the Detailed Description of Version 9 2 1 51 52 client will use HTTP S communication Otherwise it will use the default port communication which can now be encrypted using SSL Note The combination of the settings lt PARAM name UseSSL value true gt and lt PARAM name UseHttp value true gt is possible but makes no sense in most configurations It will cause the communication between the client and the proxy servlet to use HTTP or HTTPS and communication between the proxy servlet and the server to use SSL Browser Certificate Warning when Connecting to the Server The JettyKeyStore generated automatically by the server contains an auto generated certificate which is not trusted by any official certificate authority Therefore when connecting to the server using HTTPS the browser will issue a warning message There are two alternatives for e
71. eps below must be performed 1 Set PFType STATIC as explained above before importing the Natural map 2 Import the Natural map and compile it into a screen image using the Create Screen Images or Maintain Screen Images wizards 3 When creating the new subapplication from the Natural screen image in the Select Screen Layout step choose the WebLookNatFKeys screen layout or in the subapplication itself open Layout View and drag the section NatFKeys around the 4 Capture the screen representing the current Natural map in runtime and combine it with the subapplication created from the map in order to display the function keys together with their description Existing applications using knowledge base definitions developed in previous versions of JIS and which did not develop their own pattern definitions for matching Natural Fkeys should append the knowledge base definitions from the NATURAL GKEB file in lt JISRoot gt KB_3270 into their knowledge base list in the specific ini note this is an advanced operation which requires knowledge base administration skills Displaying function keys using the DYNAMIC option When using the DYNAMIC option the Natural parser generates prototype information for the JIS Dynamic FKeys feature During design time JIS uses the prototypes to identify the possible FKey patterns which may appear in runtime Therefore there is no need to capture and combine screens
72. erride the DOM manipulations Code example package appls XHTMLV9 xhtml user import com jacada jis runtime server frontend xhtml context import com jacada jis runtime server frontend xhtml general XhtmlConstants import com jacada jis runtime server frontend xhtml controls XhtmlControl IMSORE CLC WIC Clem y IMMOOIE TEVE Wer import com jacada jis runtime server frontend xhtml controls Window import com jacada jis runtime server frontend xhtml modifier StyleModifier description Appl java 2 public class Appl implements com jacada jis runtime server frontend xhtml extension IUserPageExtension COMBICICUCIEGIE 23 jouloilake Wool public void onPageLoad OnPageLoadContext context Window window context getWindow Vector vControls window getAllControls Software AG For me 1 Of 2 lt vcomezoles size ise A Get the control on the window XhtmlControl curControl XhtmlControl vControls get 1 curControl setForeground RED curControl setSize 100 10 curControl setLocation 1 1 Update the new style settings into the Page DOM Hashtable styleHash context getDataBlock getStyleHash for Enumeration Suylelasin leys 0 oli sMorelencaes 0 7 A Element key Element e nextElement StyleModifier updateStyleAttribute key Map styleHash get key this is an example of manipulating label nodes on
73. et from the client to the server can be done in two ways 1 Create a standard socket and then wrap it with an SSL socket this is the way the product has worked so far 2 Create an SSL socket directly this is more mainstream approach and is introduced in this version A new Applet parameter enables controlling which option to use lt PARAM name IsDirectSslSocket value true gt The default value is false selecting the first option maintaining backward compatibility The value true selects the new option Note SSL sockets which connect between either the proxy servlet to the server or the server to the mainframe are not affected by this setting SI 5086213 JIS 1248 The Properties Storage is a mechanism used for storing data locally on the client machine such as table column arrangement A problem with this mechanism arose when running more than one client session from the same Applet or application Until now each of these sessions created its own storage object on top of the singleton properties file This way changes made by one session were not reflected by other sessions so that for example one session could overwrite changes made by other sessions Now the same storage instance is shared between all sessions running in the Software AG same Applet and access to the singleton storage object is synchronized This way a change made by one of the sessions is immediately visible to all other sessions SI
74. ettings d The service log is automatically created in classes logs JBSService log In addition the log messages have been improved and time stamps have been added Backward compatibility The new implementation maintains backward compatibility with existing JBSToService command line options For example for an application named XHTMLV9 1 Create the service C XHTMLV9 bin gt JBSToService exe c Service name JISSvc Display name JIS Service Description Controls the running of a JIS Server Path to executable C XHTMLV9 bin JBSService exe 2 Service JIS Service now appears in the services control panel You can start and stop it using the standard services panel Remove the service C XHTMLV9 bin gt JBSToService exe r Using JAM as an Applet in JIS Standalone Server JAM can now run as an Applet also when using the standalone server The main advantage of this configuration is that it does not require opening any ports in the Firewall In previous versions when running the JIS server on Unix users had to either use an X terminal for running JAM or open several ports in the Firewall in order to run JAM from a Windows workstation This is no longer necessary To access the JAM Applet from the development environment use the following URL http localhost 8080 JISAdminServlet In production configuration replace localhost 8080 with your server address and port When running as an Applet JAM is password protected The d
75. ey Limitation This feature is not supported in the XHTML client Multiplying Default Control Size by a Pre Defined Factor When localizing strings the translated string is often longer than the original English string JIS previously had limited support for changing the width of the controls by a pre defined factor and this support has now been expanded to also support controls without data flow The width factor setting affects the width of the control in the following cases When creating a new control from a knowledgebase representation definition When creating a new control from a Floating representation definition When creating a new control using Add Control in design view When choosing Adjust size by text on an existing control in design view Detailed Description of Version 9 2 1 77 78 This feature changes the behavior of the various control types as follows Static Static Checkbox header enables sizing static controls without data flow Edit Edit Prompt Date Combobox Spin no change existing width factor already works Group box no change existing width factor already works Table headers adjusts the table column width only if the table header multiplied by the width factor is wider than the table column data area The assumption is that only table headers will be localized while data displayed within the table data area will not be localized Button PictureButton PushButton Link width facto
76. figure the root and integrator processes not to accept sessions This way we have 8 server processes serving sessions 1 1 1 8 Q Can you share some benchmark results A On a Windows 2008 64 bit machine using dual x5670 2 93 GHZ CPU 12 cores in total and 16GB Ram running Java 1 7 0_09 64 bit we were able to run 3 000 concurrent XHTML sessions with 35 000 screen transitions per minute CPU utilization reached 60 and memory consumption 15GB The server used the following settings GeneralParameters MaxProcesses 10 Sessions Software AG SpareSessionsPercent 0 StartupSessionsPercent 100 MaxProcessSessions 800 MaxMachineSessions 6400 VMCommandLine JavaMemory ms1200m mx1200m M1 Levell VMCommandLine Server JavaMemory ms128m mx256m 1 Integrator VMCommandLine Server JavaMemory ms128m mx512m 1 Levell Sessions MaxProcessSessions 0 zZ 1 Integrator Sessions MaxProcessSessions 0 Note that these figures depend on many factors such as the server operating system Java version project specific components and mainframe response times which may be unique to your specific application therefore we recommend load testing the server before deploying your application to production New Features in Version 9 1 2 Creating screen images from Natural Maps One of the major strengths of JIS is its ability to create screen images directly from host screen maps This provides many advantages over creati
77. g 1 Rew2 log clelauie Lolo le memenaso uo elelomie my evi Los The server continues logging into a newly created debug_1 log and so on Detailed Description of Version 9 2 1 73 74 For process 1 3 for example the log files would be named debug_1 3 log debug_1 3 revi log debug_1 3 rev5 log Java Client Log The Java Client log in now written by default to a log file named debug_ lt timestamp gt log in the TEMP folder on the local workstation and not just to the Java console This can be controlled using the Java Applet parameter DebugFile The possible values are lt PARAM name DebugFile value 1 gt to write log messages to the Java console only as in previous versions The drawbacks of this setting are that the log file size is limited and there is an increase in memory consumption lt PARAM name DebugFile value 2 gt to write log messages only to a file in the TEMP folder This approach has a drawback that only JIS log messages are written to the file and Java plugin messages are not written lt PARAM name DebugFile value 3 gt to write log messages to both the file and to the console default DebugTimeStamp When this setting is omitted from the Applet parameters a timestamp is added by default to the file name DebugLevel The existing log level 0 now provides log messages regarding errors and session dump information A new level has been added 1 to disable the log comple
78. g IE8 or higher to run a JIS XHTML application which is deployed to an application server it is not possible to open more than one JIS session from the same browser window It is not possible to run the JIS server using a 64 bit JRE Use 32 bit JRE instead The JIS common installation for J2EE deployment cannot be installed on a Windows 2008 64 bit machine When running the JIS server as a Windows service when stopping the JIS server from the administrator utility the service is still displayed as started in the Windows services panel Stop the service from the services panel to clear out this inconsistency Detailed Description of Version 9 2 1 61 New Features in Version 9 1 1 62 XHTML The XHTML client is now supported on Mac OS and Linux operating systems and Safari and Chrome browsers See the Recommended Configurations section for specific details as to which configurations are recommended and see the Limitations section regarding limitations when using these configurations Note In order to use the Mainframe function keys F1 F24 when using the Safari browser on Mac OS open the System Preferences dialog box select Keyboard and verify that the Use all F1 F2 etc checkbox is checked Server Changes The Server start up shutdown and restart times have been shortened In order to achieve this the following changes were made The Node Registry component no longer runs as a sep
79. g has been changed from O to 1 in order to provide better 5250 specification compatibility GUISys TN5250 SortFormatTable 1 SI 5076069 JIS 1170 Fixed disconnection which was related to the Many To One feature SI 5069196 JIS 1122 The problem that has been fixed was related to the following scenario a The user worked on screen X from library A b The host spontaneously sent a popup screen Y from library B so that the browser and server were then out of sync c When the user submitted the form for screen X of library A instead of getting the normal OutOfSync page the user received an HTTP 500 response SI 5074062 JIS 1155 The server became locked when the client used IE8 or IE9 with Jetty 6 1 default configuration This no longer occurs as Jetty has been upgraded in this release JIS 1166 The DoMethod Name is now fully supported for all component types It returns the name of the component as defined in ACE JIS 1167 The DoMethod SetModifiedFlag on a Static receiver caused a compilation problem SI 1057170 JIS 1247 It is now possible to set the machine redirection address to be configurable By default when a client is redirected to a different machine or to the same machine when using the ForceMachineRedirect 1 setting the machine address sent to the client is the internal localhost address of the server machine Sometimes such as when using network address translation you may require that the redirect
80. h Button Limitations The width factor settings only affects components which has no local modifications manual or using window layout The Adjust Size By Text function does not resize table headers After making changes to the Window Options dialog the user needs to click the lt Apply gt button in order for the changes to take effect New Features in Service Pack 9 0 4 Logging Improvements Logging functionality has been improved e The architecture parameter 32bit or 64bit is now written to the log e The current time zone is now written to the log e The time stamp written to the log now includes milliseconds Detailed Description of Version 9 2 1 79 80 e The AM PM marker has been removed and replaced with 24 hours time Simplifying JIS Windows Service Configuration Deploying JIS as a Windows service has been simplified When running the JBSToService exe utility after creating a JIS runtime installation folder for Windows do not run JBSToService exe from the JIS installation folder itself most of the default values are calculated correctly as follows a The code is able to automatically locate JBSService exe b The code cleans up and uses the command line from the existing jacadasv bat when launching the service there s no longer a need to clean up the signs c The default ini settings are read from the jacadasv ini of the runtime installation note that by default there s no need to specify the s
81. he extensions Only if you must continue using the extensions then set the following In the lt ApplicationName gt ini file Emulator LanguageDescriptorEnabled 1 LanguageDescriptorFactory appls lt AppName gt server user ILanguageDescriptorFactory In the HTML Launcher lt PARAM name LanguageDescriptorFactory value appls lt AppName gt user ILanguageDescriptorFactory gt Where lt AppName gt is the name of the JIS application lt PARAM name LanguageDescriptor value lt Language name from the Supported Languages table gt In addition if you are using an existing ChineseLanguageDescriptor class on the server and client you ll need to 1 Change the isLanguageSupported method as follows public boolean isLanguageSupported String language return language equalsIgnoreCase Chinese 2 In the ILanguageDescriptorFactory class replace occurrences of Chinese Simplified with Chinese Parameters This section provides a reference to the configurable parameters LanguageDescriptorEnabled Enables the Descriptor mechanism within JIS Once this parameter is set both the internal language descriptors and language descriptor extensions are enabled Detailed Description of Version 9 2 1 91 92 Configuration file lt ApplicationName gt ini Section Emulator Possible values 0 1 default 0 Example LanguageDescriptorEnabled 1 LanguageDescriptorFactory ini setting
82. he homepage is at http www softwareag com Made with IzPack http izpack org Step 2 Read the readme text and click Next Step 3 Accept the license agreement and click Next Step 4 Select the installation path and click Next Step 5 On Windows platforms setup the windows shortcuts and click Next Step 6 Wait for the installation to finish click Next Step 7 Installation finished click Done Installing the runtime on a remote machine 1 Make sure a supported Java JDK or Java Server JRE is installed on the target machine and that the Java command is in your machine path You may install the runtime using a Java JRE however the installed server cannot run using a Java JRE since it requires a server grade Java installation 2 Copy the Runtimelnstallation jar file located in the lt JISRoot gt appls lt AppName gt install folder to the target machine For Unix platforms use binary ftp when transferring the file 3 On the remote machine open a command window and type java jar Runtimelnstallation jar On a Windows machine the installer dialog is launched On a Unix machine if X Windows environment is configured the graphical runtime installation dialog is launched Otherwise command line installation is invoked with similar installation steps a Creating an installation kit To package the runtime installation into a distributable deployment pac
83. he server JIS 1025 There was a problem when deploying an application to WebLogic and using page size optimization OptimizeStyleAttributes 1 JIS 610 In previous versions the XHTML RedirectionProxy contained Sun specific code which prevented it from using the IBM JVM This has been fixed JIS 676 Deployment of J2EE application on weblogic 10 3 4 failed SI 5015800 It is now possible to include the underscore character in the name of a table component SI 1044586 An exception related to using the PrintString method after calling the Close method on an external output stream has been fixed JIS 1102 When using the Chrome browser redundant Keepalive messages were sent by the browser SI 1034309 In a window which included a tab component the tabbing order did not work correctly As a result of this fix the tab folder titles are no longer part of the tabbing order Detailed Description of Version 9 2 1 59 60 Server SI 5037488 The return value of the default UserRefreshSubApplication of the NO_ATTRS screen has been changed to False since returning True prevents the screen from refreshing causing various problems SI 5036973 When using the MaintainFormatTableEntryOn5250FieldSplit ini setting some fields were incorrectly displayed on the emulator screen JIS 629 In the jacadasv ini file the ProcessRespawnEnabled setting and the settings in ProcessCheck section are no longer supported as these caused stability and
84. i gt Process definition gt Java Virtual Machine Use this page to configure advanced Java TM virtual machine settings r IS Configuration Runtime General Properties Additional Properties Classpath Custom preperties Boot Classpath Verbose class loading FT Verbose garbage collection TT Verbose INI Initial heap size MB Maximum heap size e O Ran HProf HProf Argurnents O Dabug Mode Debug arguments agentlib jdwp transport dt_socket sever y suspend n address 7779 Generic JVM arguments DJacadaCommonDirectory D JISCommon_910_B39 Execuzable JAR file name Usability Improvements in the Generate Runtime and Run Application Wizards The Generate Runtime functionality has been improved to allow generating the runtime while the server is running enabling the user to continue using the existing runtime while generating a new version of the runtime Run Application Wizard Improvements After clicking Finish in the last screen of the Run Application Wizard JIS asks you whether you would like to restart the server Detailed Description of Version 9 2 1 67 68 Run Application The server is already running Would you like to restart it Restarting the server enables launching the updated application in a new browser window previously the server was not restarted and the application displayed in the browser did not reflect the changes
85. ianLanguageDescriptor extends ItalianLanguageDescriptor override here methods from the ILanguageDescriptor interface for example public boolean isDBCSLanguage return super isDBCSLanguage Recommendations When using LanguageDescriptors it is recommended to run the interface server with the default file encoding for the operating system and not use a specific encoding JIS clients were tested on a standard Windows XP SP2 operating system version not a language specific operating system with the specified languages enabled in the regional settings Java Client About Dialog Box About dialog no longer contains the now obsolete RTCP key information Serial No and Licensed To labels Host Print Transform Printing using Java Services When using the AS400 HPT Host Print Transform feature the print job is sent from the AS400 already formatted with all the necessary escape codes required for the print job formatting In previous releases of JIS the Java client sent this print job into a predefined parallel or serial port on the local PC The end user had to define port capturing on the local PC for the actual printer This feature adds the ability to use the Java print service APIs to implement the same behavior This way the user does not have to configure the port in advance Java takes care of this for you In addition HPT using the print service now supports the existing PrinterEmulationPageOrie
86. ication using the New Subapplication wizard the subapplication will be marked as host popup and the resulting host screen will include a popup border based on the window properties specified above Handling Function F Keys By default the Natural function key lines appear in the following form on the mainframe screen MESSE P IS P PP PY PP 2 EP O ISS Help EXC last Flip Canc However many variations exist including function keys PF13 to PF24 or different function key layouts such as F3 EXIT The various terminal commands which control the layout of the Natural function key lines are documented here http documentation softwareag com natural nat821mf tcom pcy htm PERCENT_YN In addition Natural maps do not provide information about the position and layout of the Natural function key lines in runtime As JIS relies on the function key information in the screen image in order to identify the screen in runtime and in order to define Buttons Menu items and Accelerator representations it provides two different options for displaying the function key lines in the generated screen image 1 STATIC the default Natural function key line shown above is displayed on the screen image without the function key s description The user needs to capture and combine an actual host screen in order to append the function key description to the screen image Use this mode only if your application always uses the
87. ified panel file names which need to be verified When this setting is specified only the panels specified by the setting are loaded by the application verifier and all other application panels are ignored ExcludePanelFiles semi colon delimited list of fully qualified panel file names which need to be excluded from the verification When this setting is specified all panel files are recursively loaded except files specified by this setting If IncludePanelFiles is specified ExcludePanelFiles is ignored The panel file paths specified by these settings are absolute panel file names or folder names If folder name is specified the setting applies to all panel files under this folder and all its sub folders the setting is case insensitive Example IncludePanelFiles c jis appls MYLIB1 1lib sdf mypanell pnl c jis appls MYLIB2 lib Software AG This setting will run the verifier by loading the panel mypanel1 pnl and all pnl files under folder MYLIB2 lib Simplified Web Application Deployment In previous versions of the product deploying a JIS web application to an application server required users to first install the common installation component and then specifically configure the application server to locate it This procedure was unnecessarily complex and error prone In addition the product administration application had to be deployed separately As of this release the only required components for application server deploymen
88. ifying the encoding of the localization resource file has been added ResourceFileEncoding This parameter is necessary when the encoding used when creating the resource file is different than the encoding used by the client workstation Examples To read a resource file encoded as UTF 8 This is the recommended encoding lt PARAM name ResourceFileEncoding value UTF 8 gt To read the resource file using simplified Chinese encoding lt PARAM name ResourceFileEncoding value gbk gt To read the resource file using simplified Japanese encoding lt PARAM name ResourceFileEncoding value sjis gt Text of dynamic menu items is now translated according to the resource file Text labels in the Help About dialog box can now be translated according to the resource file The following localization improvement has been made to both the Java Client and XHTML localization support The original string and the translated string can now include multiple appearances of the equal sign and the quotes sign ACE Creation of the runtime installation is only possible for platforms for which runtime was generated Runtime Installation It is now possible to install the JIS runtime installation on Windows to a path which includes spaces For example c program files lt company name gt lt product name gt This is currently not supported on Unix and AS 400 Detailed Description of Version 9 2 1 65 Java Client
89. ing parameter in lt AppName gt html files lt PARAM name DebugLevel value S prop debug level gt Add the following settings to Jacadasv ini Http Software AG ParameterizedTargets MYAPP html PropertiesFilePath home myuser server properties Create the file home myuser server properties and add the following line debug level 70 During runtime when the browser loads an Html page from the server the server will replace the parameters with their substitution values and send the response page back to the client The sequence of events to launch the Java client would be as follows 1 Browser requests to load an Html page 2 Server checks if the page appears in the list of parameterized targets 3 Server loads the Html 4 Server performs parameter substitution based on the parameter context defined in the page 5 Server writes the modified page back to the response 6 Client uses the response page to load the Applet Pass Through Gateway Note this is an advanced feature which requires good understanding of web technologies In order to closely integrate a JIS session with other web applications it is sometimes desirable to use the connection to the JIS session and the other web application over the same server address and port This can be accomplished by using the JIS server as a gateway to an external web application To define the gateway mapping add the GatewayMappings section to jacadasv ini a
90. ing the JIS session from a different address than the one used for loading lt AppName gt xhtml html is now supported 5122932 JIS 1516 JIS 1524 Timeout Redirect By default when a session is closed on the server due to idle timeout a message box is displayed to the user and the browser remains on the current page This was identified as a security risk since leaving the browser open on the current page may expose sensitive information On the other hand keeping the page visible allows for legitimate users to view information already entered but not submitted to the server Due to this trade off we have now introduced a new configuration jacadasv ini Http KeepAliveFailureAction redirect When set the client browser will redirect to the web server root address when a session is closed by the server ACE 5101893 JIS 1349 JIS 1350 Java Exception in Generate Runtime Problem related to sorting XML files during generate runtime has been fixed 5107008 JIS 1383 JIS 1385 runtime generation difference between gui and remote Generating the runtime using the command line interface now works correctly 5106317 JIS 1377 JIS 1414 Brown background color in color table changed to Yellow The color table background color definition which applies to the Yellow background color was incorrectly labelled as Brown This has been fixed 5111725 JIS 1420 JIS 1429 Deprecated Method used in ACE Deprecated methods were remov
91. ing the operating system path the installation now uses the time bound SendMessageTimeout Windows API instead of the SendMessage API to prevent the installation from freezing when the path cannot be updated JAVA Client JIS 647 When running the Java client as an application the parameters equivalent to the Applet parameters in the launcher Html are read from the file params txt located in the folder lt JISRoot gt JacadaFiles classes appls lt AppName gt user As the Applet Parameters were case insensitive and the parameters in params txt were case sensitive copying parameters between the two configurations led to confusing results Now the parameters in params txt are also case insensitive JIS 640 The Java client JavaDoc is now installed only when Java client is available in the CD Key SI 5042482 The font resource loading has been fixed SI 5055856 Sending a client reply message starting with the value Ox0C caused the session to disconnect JIS 628 The default value of the UseNewHTML Applet parameter is now set to false SI 5041270 The Java internal typeahead mechanism is now disabled SI 5059124 Since we introduced the ability to log information to the file system by default all log messages are written to both the Java console and the client log file in the temp folder However some exception stack traces and the client session dump were only written to the file and not to the console This has been fixed and now all exce
92. ion 2 Make sure the UseEventDispatchThread parameter is not set to false if necessary remove the parameter or change the parameter to lt PARAM name UseEventDispatchThread value true gt 3 Make sure the EnableKeyboardBuffering parameter is set to true starting from this release the default value is false lt PARAM name EnableKeyboardBuffering value true gt 4 Verify that keyboard buffering has been enabled by checking for the following debug print in the client log KeyboardBufferingManager is enabled Applet parameters related to Keyboard Buffering The following parameters influence how keyboard buffering functions Parameter Default Description Value UseEventDispatchThread true Set to true to enable keyboard buffering EnableKeyboardBuffering false Set to true to enable keyboard buffering Set to false to disable keyboard buffering KeyboardBufferingResetKey Escape The reset key code Pressing the specified key resets the playback buffer Valid values can be obtained using KeyEvent getKeyText lt Virtualkey code gt KeyboardBufferingResetKeyModifier Shift Reset key modifier Valid codes can be obtained using KeyEvent getKeyModifiersText lt Virtual modifier gt HideKeyboardBufferingToolbar true Set this value to false to display a toolbar which displays the status of the keyboard buffer The following limitations influence how the keyboard
93. irectories such as skipping DDS files installation files and configuration files All the files are included in the package including configuration files Changes in Unpack When unpacking an application existing files are automatically replaced The configuration files the files asked about in the last step of the wizard are unpacked according to the settings chosen the last time the wizard was run from ACE Detailed Description of Version 9 2 1 99 Example buildapp xml The following example demonstrates various operations such as opening an application generating a runtime creating a runtime installation and packing and unpacking an application lt Ace gt lt OpenApplication Name TEST1 gt lt GenerateRuntime Type Java XHTML Platform Windows Solaris 0S390 AS400 AIX Linux NewAndModified 0 gt lt OpenApplication gt lt OpenApplication Name TEST2 gt lt GenerateRuntime Type Java XHTML Platform Windows Solaris Linux AIX AS400 0S390 gt lt CreateRuntimeInstallation DeploymentType Standalone Platform Windows Runtime XHTML InstallFileSize 1024 gt lt Wise Launch 1 ExecuteFile C Program Files Wise InstallMaster Demo wise32 exe InstallationDirectory C TEST2 ImageFile gt lt Wise gt lt CreateRuntimeInstallation gt lt CreateRuntimeInstallation DeploymentType J2EE Server weblogic tomcat websphere gt lt Libraries List MODELS g
94. irefox Windows Chrome Mac OS X Safari iPad iOS Safari Mobile Standalone Server The JIS standalone server has been tested in the following environments Operating System Java version Windows 2003 Oracle 1 7 0 Windows 2008 Oracle 1 7 0 Solaris 10 and 11 Oracle 1 7 0 AIX 6 1 and 7 1 IBM 1 7 0 RedHat Linux AS6 Oracle 1 7 0 Detailed Description of Version 9 2 1 Application Server Deployment The runtime of the JIS XHTML client has been tested for deployment in the following environments Application Server Java Runtime Operating system or Web Container Environment WebSphere 8 5 5 IBM JRE 1 7 Windows 2003 Tomcat 8 Oracle JRE 1 7 Windows 2008 OS400 Components The DDS compiler has been tested on the following operating systems e 05400 V6R1 e 05400 V7R1 Upgrade Instructions The structure of the launcher page for the Java client lt AppName gt html has changed Sites which customized the launcher page need to adjust their customized page to the new structure of the Applet tag Make sure to incorporate the following changes 1 Modify the archive attribute to the following value archive cst clbase jar APPL ARCHIVE 2 Add the following Applet parameter to support pack200 archive format lt param name java_arguments value Djnlp packEnabled true gt Retirement of Product Components As of release 9 2 1 the following product components are
95. kage follow these steps Windows only e Copy the files Runtimelnstallation jar RuntimeInstallation exe to the root folder of your installation kit e Make sure that Java 7 JDK is installed on the target machine This can be configured as part of your deployment procedure but it s not part of the runtime installation Detailed Description of Version 9 2 1 11 12 e Launch the installer by launching Runtimelnstallation exe from the installation kit Installer customization The installation metadata files in folder lt JISRoot gt appls lt AppName gt install can be customized to modify the installer look amp feel The following files can be customized install xml standard IzPack installation script you may modify this file to customize your installation shortcutSpec xml for Windows installations defines the shortcut menus generated by the installation For further instructions about the structure of these files consult the IzPack documentation at lt JISRoot gt JacadaFiles utils IzPack doc izpack pdf manual pdf Add your application specific license agreement to license txt Add your application specific readme messages to readme txt Once you are done with your customizations Use the Create Runtime Installation wizard to generate a new installer which will automatically incorporate your changes File override policy When installing a new runtime installation on top of an existing runtime installation the
96. key String iterator next String value String vars get key do something useful Rebranding The software and product documentation has been rebranded to suit Software AG standards New Features in Service Pack 9 0 3 Changes in the Product Name As a result of the acquisition of the Jacada application modernization product line by Software AG we have begun the process of updating the product name to suit the company standards The product name is now JIS and we have begun to implement this throughout the product This has not yet been implemented in the tutorials and in the documentation Runtime Installation Improvements The runtime installation process now enables installing and deploying JIS automatically on UNIX platforms At the end of the Wise installation process an ANT script will be invoked to transfer the files to the UNIX machine and configure the JIS server Two optional new dialog boxes in the installation process enable implementing this feature Refer to the runtime installation process in the documentation for details UNIX Machine Prerequisites FTP access enabled Detailed Description of Version 9 2 1 87 88 Telnet access enabled Unzip command installed Changes in the installation process In the following screen when selecting to automatically transfer the installation to UNIX by FTP you will be required to enter the IP address or name of the UNIX machine where the JIS server is t
97. lWindow extends appls JIS_1416 original ApplSubApplWindow ArrayList lt GUILink gt linkComps new ArrayList lt GUILink gt Override public void setControl Component comp int tabindex super setControl comp tabIndex if comp instanceof GUILink linkComps add GUILink comp Override public void serverDataReady super serverDataReady for GUILink link linkComps String image classes appls JIS 1416 images normal jpg String imageRollover classes appls JIS 1416 images rollover jpg link setImages image image image image imageRollover 5115348 JIS 1455 JIS 1470 Screen hanging A deadlock related to focus management of checkbox component has been fixed 5138380 JIS 1595 JIS 1599 Infinite refresh loop When launching multiple sessions by auto generating the Applet tag using JavaScript the resulting sessions may enter an infinite loop where focus is switched between sessions This has been fixed JIS 1614 Security exception which prevented the client from establishing socket Software AG connection to the server when using Java 1 7 0_55 and 1 8 0_05 has been fixed JIS 1600 Permission problem caused by setting the frame icon when using Java 1 8 0 has been fixed by disabling this functionality for unsigned code Xhtml Native calendar widget is now supported on Android mobile devices 5118397 JIS 1486 JIS 1487 JavaScript permission problem Launch
98. le values are C or U meaning C Computer name as specified by the COMPUTERNAME environment variable on Windows operating system U User name as specified by the Java user name system property 3rd parameter deals with the case where the parameter value when inserted into the device name template exceeds the 10 characters device name limit Detailed Description of Version 9 2 1 37 take the longest prefix of the substitute value take the longest postfix of the substitute value Example Assuming lt PARAM name DeviceNameTemplate value DEV c gt and computer name MCLYAFO1 the device name created by the host would be DEVMCLYAFO lt PARAM name DeviceNameTemplate value DEV c gt and computer name MCLYAFO1 the device name created by the host would be DEVCLYAFO1 3 The following 5250 enhancement http tools ietf org html rfc4777 section 7 enables to recover from a device name collision by allowing the emulator to specify an alternate device name JIS now supports this emulation feature so that when a device name collision is reported by the host JIS will modify the device name according to the device name template provided by the client or runtime ini and send the modified device name to the host until finding a free device name or until the retry limit of 10 retries is exceeded When the retry limit is exceeded a QPADEVxxxx device name is assigned Limitations When the generated device
99. liminating the warning 1 Manually import the server certificate into the browser This is a browser specific procedure which tells the browser to trust the server certificate Each browser uses its own methods for importing the certificate 2 Generate a certificate signing request and have it signed by a certificate authority recognized by the browser and Java versions Since JIS relies on standard Java security architecture this should be a standard process which we do not cover in this document SSL connection between the server and the host It is no longer necessary to import the host certificate into the Java Keystore in order to initiate an SSL connection to a secured port defined on the host The following ini setting should be used in order for JIS to initiate a secure connection GUISys TN3270 or GUISys TN5250 SecureHostConnection 1 This new setting replaces the old setting which is currently still supported for backward compatibility SocketImplFactory cst server comm CSTSSLSocketFactory IPv6 Support JIS now supports using Internet Protocol version 6 for all runtime components including the client browser standalone server and mainframe All IP addresses can now be specified using the IPv6 address format Note When using the XHTML RedirectionProxy and specifying server address using IPv6 address format the address must be surrounded with square brackets Example lt Settings gt lt JacadaServerAddress gt
100. ll a Java JDK on the remote workstation To connect using Visual VM Execute jvisualvm exe from the JDK bin folder From the File menu choose Add JMX Connection and specify the address and port of the server process then click Ok A new node representing the server process is added to the Remote node of applications tree Double click the new node to attach to the server process JConsole Execute jconsole exe from the JDK bin folder Click the Remote Process radio button specify the address and port of the server process then click Connect Note attaching JMX monitoring tools to a production server is generally safe since these tools are designed to add little overhead However some actions performed by these monitoring tools may incur additional load on the server therefore use these tools with caution Remote Debugging Warning do not attach a debugger to a production system as this may considerably impact performance This feature should be used exclusively for development and QA In order to attach a remote debugger to a server process a unique port has to be allocated for each server process To configure remote debugging add the following jacadasv ini setting VMCommandLine RemoteDebugStartPort lt port number gt Software AG As explained in the server remote management section each Java process spawned by the server allocates a different port for remote debugging where the port number is increase
101. load these classes when using its default configuration To configure the Java JRE to load unsigned classes during development set the Java Control Panel security level to Medium or add the local server address and port to the exception list See the Java Control Panel security tab for more information Packaging application resources into Jar files The Makejar utility now supports packaging application specific class files and resources into signed Jar files and packaging these Jar files using pack200 into highly compressed archives The same mechanism used by the MakeJar utility is also used by the IzPack installer to package application resource when generating the runtime installation The MakeJar utility is invoked by executing the makejar bat under the lt JISRoot gt JacadaFiles utils makejar folder By default it will package an unsigned Jar file with the client application resources Optionally provided the necessary information it will also sign the Jar file using a digital signature in the form of a Java keystore provided by the customer In order to digitally sign the generated Jar files Makejar relies on the following jacadasv ini parameters under the makejar section e jarsigner a flag to activate the Jar signing utility Values 0 1 default 0 e Keystore fully qualified path to a standard Java Keystore file containing the code signing certificate e storepass the keystore password this password c
102. lue in the example above is interpreted by the code as If the server sends Y translate it to O when sending to the host If the host sends O translate it to Y when sending to the server A similar consideration applies to the unchecked setting and for the intermediate setting when using a 3 state checkbox The new settings expect their value to be formatted as a comma separated list of replacement tokens similar to the checked setting in the example above Logging and Monitoring Improvements The following improvements have been made in the message and exception logging e Better logging for the internal thread pool e Improved display of the host screen in the log e Removal of redundant debug filters e Improved the layout of the Debug panel in the JIS Administrator e In the JIS Administrator runtime configuration dialog the property description at the bottom of the panel now includes the name of the section and key of the corresponding ini setting Detailed Description of Version 9 2 1 35 36 Optimizing the Mechanism which Searches and Identifies Popup Host Screens A host popup is a host screen which represents a popup and whose relative location on the host screen is not fixed Host popups are identified by their borders regardless of their relative location on the host screen When a host screen image sent by the host does not match a converted host screen the screen interpreter component tries to identify it as a ho
103. maller the number of threads available for the Java process Use the Detailed Description of Version 9 2 1 63 64 following rule of thumb if for a given server process Stat Thread peak increases above 2000 consider allocating more Java processes on the server machine New system status attributes JIS Administrator Windows Internet Explorer gt http flocalhost 28080 I1SAdminServlet vs Xx w e 88 6315 Administrator x LOCALIZE Music Box Factory SLOCALIZE Music Box Factory fh B mp i Page iQ Tools 9 CJ System Status Log Properties Sessions Debug License O Bio 64 21 4 HAA Infversion Processes TotalSessions Type stat average response time ms stat transaction count stat transaction per minute 23 Server Monitor ica Runtime Configuration Local intranet R100 The JIS administrator now monitors the total number of transactions performed by the server at any given moment A transaction is defined as the unit of work starting by a client action or host action and ending when the complete response is written to the client In most cases a transaction consists of a single Mainframe screen transition stat average response times ms the average server response time in milliseconds The response time is measured from the time a client request was received by the server and until the response has been fully
104. meters have been added to the application INI file e DynamicCalculateWidth When set to 1 the server calculates the width of each page in the print job resulting in a better layout of each page Note that this may cause a non homogeneous look to the whole job since different pages may have different font sizes due to a difference in the actual text width e IgnoreEMAtStartOfLine in the TN3270 section When set to 1 the printer emulation suppresses new line and carriage return characters when they appear in the data stream following the Mainframe End of Medium signal New Features in Service Pack 9 0402 110 Enabling reconnecting to a database after the connection or session fails When using external data methods to connect to a database by default all sessions in a given server process reuse the same JDBC connection If this connection fails every session using this connection may not be able to connect to the database To recover from a connection failure the following new methods are available Software AG RepairDBConnection and RepairDBSession The following example shows the usage of these methods Actions Query wita close Trigger 17001 WaitIndicator True ScrambleName False MoveMode MoveNon DES o 0 DoMethod Receiver EXTERNALDATA Method AllocDBSession Parms Wcliges asa O08 0 90 17 Ue p Lores MS MS ISSN If Cond HO FAIL 0 DoMethod Rec
105. morerei AAA A ee A 114 New methods for setting colors of selected CellS oonnonnininnnnnnnioccnoncnonaconoconnconnconnnonn cono nono conocio nn ccoo nc rocio cn nccn ccoo 114 4 Software AG Installation amp Upgrade Information Supported Platforms Windows Server 2003 Standard and Enterprise Edition 32 bit Windows Server 2008 Standard and Enterprise 32 bit Windows Server 2008 Standard and Enterprise 64 bit Windows Server 2012 Standard and Enterprise 64 bit Windows 7 Professional Ultimate and Enterprise Edition 32 bit Windows 7 Professional Ultimate and Enterprise Edition 64 bit Windows 8 1 Professional Ultimate and Enterprise Edition 64 bit Solaris SPARC 10 64 bit Solaris SPARC 11 64 bit AIX 6 1 Power 64 bit AIX 7 1 Power 64 bit Red Hat Enterprise Linux 6 for x86 64 bit Note When a vendor no longer supports an OS version Software AG will discontinue support for this OS version effective immediately Recommended Configurations Software AG provides support for Java versions browser versions and application server versions supported by their respective vendors Being so when a vendor no longer supports a Java version browser version or application server version Software AG will discontinue supporting that version as of the next JIS service pack level delivered by Software AG Although it may be technically possible to run a new version of JIS using an unsupported version Software AG cannot continue
106. mp Access Log The NCSA access log contains a record of all inbound client requests that the embedded Jetty web server handles All of the messages written to the access log are in NCSA format which is a standard format used by web servers and supported by common log analyzing tools The access log complements the product server log and makes it simpler to identify problems such as 1 Response errors 2 Slow response times 3 Sessions jumping between servers 4 Cookie related problems Example localhost 0 0 0 0 0 0 0 1 13 Nov 2011 15 28 15 0200 GET XHIMLV9 xhtml html HTTP 1 1 304 0 Mozilla 5 0 Windows NT 5 1 AppleWebKit 535 2 KHTML like Gecko Chrome 15 0 874 106 Safari 535 2 0 localhost OSO020s0sOsO0s el Il3 New 2Ollsil Se 26215 0200 Ween Xhtml JacadaApplicationName XHTMLV9 amp Language fr HTTP 1 1 200 9142 Software AG http localhost 28080 XHTMLV9 xhtml html Mozilla 5 0 Windows NT 5 1 AppleWebKit 535 2 KHTML like Gecko Chrome 15 0 874 106 Safari 535 2 12063 localinosic OsOsOsOsOs sOsil ls New ZOLLs 15 2862 0200 eau XhtmlCSS JacadaApplicationName XHTMLV9 amp SessionId 1638907054 LibraryName XHTMLV9 amp Subap plName CSS LOGIN CrcCode 1288698078S6JBS 8126b2c9836be51cae537e50f369fa0029 afc7977727 4d0 HTTP 1 1 200 4282 http localhost 28080 Xhtml JacadaApplicationName XHTMLV9 Language fr Mozilla 5 0 Windows NT 5 1 AppleWebKit 535 2 KHTML like Gecko
107. n Indicates on which line of the screen image to position the message line The possible values are FIRST and LAST default LAST Model Type indicates the screen model of the screen image default 2 MapFileEncoding specifies the encoding used by the Natural map source file By default the operating system default encoding is used Note When importing maps from NaturalONE specify MapFileEncoding UTF8 SkipWriteCommands Select this in order not to generate maps that are called with the NATURAL WRITE command possible values are O and 1 default 1 Limitations The function key lines are always displayed in their default location two lines above the bottom of the screen lines 22 23 with screen model 2 for example assuming that Natural uses the terminal command YB Software AG The positioning related terminal commands YT Ynn and Y are not supported and will cause the screen not to identify in runtime Function key lines and message line inside a popup window are not supported The message line is assumed to be in the last line of the screen Terminal command MB or the first line of the screen Importing Natural maps from AS 400 applications is not supported Natural Maps and JITGUI The default JITGUI subapplication has been enhanced to automatically recognize the Natural default function keys layouts F1 F12 and F13 F24 Simplified HTTPS SSL Configuration Improving the Keystore Configuration In order f
108. n the server using a 64 bit Java version the following pre requisites are required e The server machine operating system should be 64 bit enabled Software AG e A 64 bit enabled Java runtime environment JRE must be installed on the server machine You can download the 64 bit JRE from http www oracle com technetwork java javase downloads index html by choosing an x64 JRE release for your server operating system e In the Jacadasv ini VMCommandLine JavaVM lt path to the 64 bit Java executable gt e Every application specific 3 party component which is not part of the JIS server distribution such as JDBC drivers external Jar files etc must be updated to a 64 bit enabled version We strongly recommend running the Application Verifier and making sure it completes successfully before deploying an application to production Application Verifier As a result of changes in the infrastructure it is necessary to verify that the JIS server Screen Interpreter component produces the exact same output when given the same input in this version as in previous versions We recommend that you run the Verifier Utility immediately after installing the new version of JIS and report any problems back to customer support The Verifier works by loading screen definitions from existing application panel files pnl created during the development of the application and verifying that the C and Java code used by the previous and new version respec
109. nabling this feature may impact significantly on scalability since it requires the client to maintain an open request an open thread to the server for the entire session New Features in Service Pack 9 0A06 Support for Keyboard Buffering Many host emulators enable keyboard keystrokes to be buffered so that users can continue typing without waiting for the host screen to refresh After the host screen is refreshed the content of the buffer is played back as if it was typed at that moment The Java client keyboard buffering feature requires an updated runtime license Contact Software AG to obtain the runtime license file Place the license dat file in the lt JISRoot gt JacadaFiles classes folder Activating Keyboard Buffering After installing the new license key that enables keyboard buffering you must change parameters in the html file that launches the application to activate the feature The following parameters influence how keyboard buffering functions Table 1 1 Parameters for keyboard buffering Parameter Default Value Description UseEventDispatchThread true You must set this parameter to true to use keyboard buffering When set to true all server requests are dispatched on the event AWT dispatch thread EnableKeyboardBuffering true This parameter must be set to true to use keyboard buffering Set to false to turn off keyboard buffering KeyboardBufferingResetKey Escap
110. name contains characters which are not valid device name characters the host replaces these characters with the sign The Substitution parameters only work when using a signed version of the Java client Emulator Trace Utilities Integrated into JIS The following command line utilities are now bundled as part of the JIS installation in the installation root folder e TracePlayer bat used to be Sendtrace plays a pre recorded emulator trace file e TraceProxy bat used to be tntrace records an emulator trace file for a 3rd party emulator e TraceViewer bat used to be traceView provides visual analysis of an emulator trace file Detailed Description of Version 9 2 Fixes Server JIS 1263 DBCS related infrastructure changes 38 Software AG 1 The Java client protocol now communicates all String values using UTF8 encoding This means that the Java version used by both client and server must support the UTF8 encoding 2 The DBCS host screen and DBCS data is now printed correctly to the server log and can be viewed using text editors which supports UTF8 such as notepad When using the Java client with the Chinese language descriptor on Windows 7 you can use the following font definitions for best results Host screen font lt PARAM name EmulatorFontName value MingLiu gt JITGUI font lt PARAM name CourierFontType value MingLiu gt SI 5073798 JIS 1156 The default value of the following ini settin
111. nd define a list of mapping settings in the following form mapping logical name resource path gateway to url Where mapping logical name is an arbitrary string representing a descriptive unique identifier of the mapping resource path is the prefix added to the JIS web site address to identify a mapped resource gateway to url is the URL address from which all requests to the resource path should be served Example To enable JIS sessions to access information from a web site such as http www w3c com over the same server address and port Add the following mappings GatewayMappings w3c main w3c http www w3 org w3c css 2008 http www w3 org 2008 w3c 2009 2009 http www w3 org 2009 w3c standards standards http www w3 org standards w3c consurtium Consortium http www w3 org Consortium w3c participate participate http www w3 org participate Then assuming that the JIS server listens on localhost 8080 you can access the w3c web site using the following URL http localhost 8080 w3c Detailed Description of Version 9 2 1 15 16 Under the hood the server is using an internal proxy servlet which accepts client requests to the context path URL resource path and forwards them to the target web site gateway to url The server then reads the response from the target web site and writes it back to the client browser In case the target web site contains relative links starting with a the context p
112. nd lt context gt is one of the following literal strings explained below prop system header param cookie Context values explanation Name Description Prop Name of a property in a standard Java properties file loaded by the server The name of the property file in which this property is defined is determined by the following jacadasv ini setting Http PropertiesFilePath lt file name gt System Name of a Java system property obtained using the Java API System getProperty invoked by the server Header Name of an Http header sent by the client when requesting the launcher page The Http header value replaces the token in the launcher Html Param Name of GET or POST parameter sent by the client when requesting the launcher page The Http header value replaces the token in the launcher Html Cookie Name of a cookie sent by the client when loading the launcher page from the server To define the list of launcher Html pages affected by this feature in the jacadasv ini Http section set the value of the setting ParameterizedTargets to a semicolon separated list of resources on which parameter substitution should be performed Only these resources are affected by parameter substitution Example Setting the value of the DebugLevel Applet parameter inside lt AppName gt html based on the value of the property debug level in the Java property file home myuser server properties Set the follow
113. nd a user with write permissions username controlRole password controlRole To change the default usernames and passwords edit the classes jmxremote password and classes jmxremote access files and make the necessary changes Connecting using Java code Refer to a number of Java code examples Appendix A which demonstrate how to use JMX code to administrate the server All examples contain pure Java code and do not rely on any product or 3 party Jar files XHTML Page Size Optimization Improvements The page size optimization feature was first introduced in JIS 9 0 4 in order to reduce the page size generated by JIS refer to the JIS 9 0 4 release notes for more information The following improvements have been made to the optimization process Software AG The optimized CSS for sub applications which contain dynamic controls such as the JITGUI sub application is now generated every time the sub application is accessed and not only the first time it is accessed The optimized CSS is now generated after the server side XHTML extensions finish executing so that it reflects changes made to the page by code extensions It is now possible to instruct JIS to generate a new optimized CSS for sub applications where the page structure has been modified using a code extension This is done by calling the context reOptimizeSubApplication api from the onPageLoad extension public void onPageLoad OnPageLoadContext context cod
114. ne c Program Files x86 Internet Explorer iexplore ex Software AG Maintaining Backward Compatibility By default now the server loads native resources such as dlr files using a Java class loader instead of as platform specific memory mapped files This prevents the server from locking the resources thus allowing to generate runtime while the server is running It is possible to change the default behavior in runtime to maintain backward compatibility Use the following jacadasv ini setting GeneralParameters LoadNativeResourcesUsingJava 0 When using this setting you will not be able to generate runtime while the server is running Restarting the JIS Server A new mechanism enables restarting the JIS server Restarting the server is useful when updating a new version of the application or in order to reload configuration changes which require restarting the server This Restart command can be invoked in the following ways Typing RESTART in the server console Windows system32 cmd exe C JIS91_b29 gt C JIS91_b29 JacadaFiles utils jrei6 bin java Djava security polic y C JIS91_b29 JacadaFiles classes jacadasy policy classpath C JIS91_b29 Jacad aFiles classes C JIS91_b29 JacadaFiles classes cst jacadasvy jar cst server modu le ServerStarter Server Module Copyright lt C gt 1997 2616 Software AG Loading interface server please wait Server ready STARTED restart Waiting for all processes to exit
115. ng the screen images from screen captures Starting from release 9 1 2 JIS now supports creating screen images directly from Software AG Natural map files by integrating the Software AG Natural parser component into the JIS codebase Natural map files are first converted into JIS SDF standard maps and then to JIS screen images JIS supports creating screen images from the following Natural map formats e NSM format this is the map file source itself which can be imported from the mainframe or from a NaturalOne project e NCD format this map format is generated using the Natural SYSOBJH utility As Natural map files do not contain information required for creating function keys and popup window borders JIS provides additional mechanisms for adding this information to the generated screen images Importing Natural maps The process of creating screen images from Natural maps is very similar to the process of creating screen images from other Mainframe map formats such as BMS or MFS Detailed Description of Version 9 2 1 43 Create Screen Images Wizard Select Screen Images Type You must now select the source type For the screen image that you want to create Screen images type Next gt Natural map files define host application screens ACE will use this information to create Captured screen images Since Natural maps contain useful information about a screen s fields C pms when available use it in preference to screen captures a
116. nguage descriptor for all sessions Configuration file lt ApplicationName gt ini Section GUISys TN3270 RuntimeLanguage There is no longer a need to specify a specific server side language since the server now supports all languages Configuration file lt ApplicationName gt ini Section Emulator Detailed Description of Version 9 2 1 Supported Languages JIS Language Descriptor to codepage mapping Language Class Name EBCDIC ASCII Is Double Descriptor Prefix Codepage Codepage Byte Default N A Cp037 Cp1252 Albanian Albanian Cp870 Cp1250 Belorussian Belorussian Cp1025 Cp1251 Bulgarian Bulgarian Cp1025 Cp1251 Chinese Simplified Chinese GB935 GBK Yes Chinese Traditional ChineseTraditional Cp937 Big5 Yes Croatian Croatian Cp870 Cp1250 Czech Czech Cp870 Cp1250 Danish Danish Cp1142 Cp1252 English UK EnglishUK Cp1146 Cp1252 English USA EnglishUS Cp1140 Cp1252 French French Cp1147 Cp1252 German German Cp1141 Cp1252 Greek Greek Cp875 Cp1253 Hungarian Hungarian Cp870 Cp1250 Italian Italian Cp1144 Cp1252 Japanese Japanese SJIS MS932 Yes Korean Korean Cp933 Cp949 Yes Macedonian Macedonian Cp1025 Cp1251 Norwegian Norwegian Cp1142 Cp1252 Polish Polish Cp870 Cp1250 Portuguese Portuguese Cp037 Cp1252 Romanian Romanian Cp870 Cp1250 Russian Russian Cp1025 Cp1251 Serbian Serbian Cp10
117. ns when typing to the host A rare problem of typing the wrong information to the host screen has been fixed F5115354 JIS 1457 JIS 1471 Can t see all node in Admin console A problem presenting node names in the administrator when deployed to WebSphere has been fixed Software AG JIS 1473 Add shutdown hook when server console is disabled When running the server as a background process on UNIX the server n command line flag is specified so that the server console won t block the command window When using this mode a shutdown hook is now registered so that shutting down the server for example using the jam x shutdown command would terminate all server processes 5129821 JIS 1551 JIS 1561 Directory Traversal Security problem The embedded Jetty web server was updated to version 8 1 14 in order to resolve a security problem JIS 1322 Application Verifier fixes The application verifier now handles gracefully the following user errors 1 Application does not exist 2 Application exists but has no panel files In addition if the application name is specified in lower or mixed case the name is automatically converted to upper case 5099911 JIS 1334 JIS 1337 Message handling problem A problem in the message handling mechanism has been fixed 5099911 JIS 1334 JIS 1338 Toolbar subapplication A problem related to the compilation of the toolbar subapplication GS_BAR has been fixed 5124921 JIS 1526 JIS
118. ntation and PrinterEmulationPaperType Applet parameters Exposing the XHTML Page DOM for Java Extensions This feature exposes thepage DOM for project specific extensions from the OnPageLoad event handler of Appl java Detailed Description of Version 9 2 1 95 96 A new OnPageLoadContext API public Document getXhtmlDonm This should be used to retrieve the existing page DOM and change it for project specific requirements The DOM retrieved by getXhtmiDom does not reflect style changes made by the existing project specific XHTML extensions In order to reflect changes made by existing XHTML extensions you need to add the following code to the onPageLoad method public void onPageLoad OnPageLoadContext context Existing Xhtml extensions Update the new style settings from the Xhtml extensions into the Page DOM Hashtable styleHash context getDataBlock getStyleHash for Enumeration styleHash keys e hasMoreElements Element key Element e nextElement StyleModifier updateStyleAttribute key Map styleHash get key get the already modified DOM and further manipulate it Document xhtmlDom context getXhtmlDom Another important note is that while you are modifying the component style inside the DOM object you have to clone the modified component see example otherwise the JIS internal code will re apply the styles set in the code extension and ov
119. o be installed the name and password of a user who has permissions on the machine to connect using FTP and Telnet and the postfix of the shell command prompt string to be used by the UNIX machine S JIS Server Installation Transferring to Solaris Y Automaticlly transfer the files to the Solaris Server Note his procedure requires HIFP and elnet access to the Solaris Server Solaris server address it 000 Solaris server username ba Solaris server password Shell Command Prompt e g gt Cancel The screen which follows the above screen is the Application Configuration screen where you are required to select whether to replace the configuration files or to preserve existing configuration files 2 JIS Server Installation Application Configuration Application configuration New installation replace configuration files Update installation preserve existing configuration files Note The new installation procedure is only available for Solaris AIX and Linux Software AG Simplifying the Printing Emulation Configuration XHTML The printing emulation configuration for JIS XHTML has now been simplified and default values are provided for most parameters The following parameters now have defaults which are suitable for most configurations and no longer need to be defined in the lt ApplicationName gt ini ENSA SORRE WorkRootURL WorkRootDirectory SpoolDirectory XSLTforXMLtoHTML
120. o be painted public void setSelectionBackground Color color To set the foreground color in which selected cells are to be painted public void setSelectionForeground Color color To discover if the default background color for selected cells has been changed by setSelectionBackground or any other method public boolean isDefaultSelectionBackground To discover if the default foreground color for selected cells has been changed by setSelectionForeground or any other method public boolean isDefaultSelectionForeground To discover the current background color of selected cells public Color getSelectionBackgrounad To discover the current foreground color of selected cells public Color getSelectionForeground The following APIs are now marked deprecated since they only control the selection background color but not also the foreground color public void setSelectionColor Color color has been replaced by setSelectionBackground color color public boolean isDefaultSelectionColor has been replaced by public boolean isDefaultSelectionBackground public Color getUserSelectionColor has been replaced by public Color getSelectionBackground A good place to use these APIs is by overriding the setContol or createGUIControls methods Software AG Example Detailed Description of Version 9 2 1 115
121. oadtest or modify the classpath in order to compile the application 2 It is no longer necessary to add application specific code to user Applet java and user JacadaStarter java in order to use the Applet Every Java client application can now become a loadtest application using only Applet parameter changes and server side navigation changes Backward compatibility note Extension code that was added to src appls lt AppName gt user Applet java used to initialize the loadtest applet in previous versions has to be removed from the code since it will no longer compile and its functionality is now part of the core product This includes the following code in Applet java if isLoadtest LoadtestController lc new LoadtestController this add lc BorderLayout CENTER Lo mt 0 6 return Detailed Description of Version 9 2 1 33 Support for Keyboard buffering Many host emulators enable keyboard keystrokes to be buffered so that users can continue typing without waiting for the host screen to refresh After the host screen is refreshed the content of the buffer is played back as if it was typed at that moment Prior to this release keyboard buffering required a specific runtime license Starting from this release this feature is an integral part of the product and no longer requires a separate license To enable Keyboard Buffering for the Java client 1 Open the HTML file that launches the applicat
122. ols ATL 28026 When you require adding a leading 0 in front of a single digit number in a spin box control perform the following appls lt APPLNAME gt user ApplSubApplwindow java public void setControl Component comp int tabIndex super setControl comp tabIndex if comp instanceof GUISpin GUISpin spin GUISpin comp spin setInputRestrictor new NumberInputRestrictor O Support for monochrome terminals ATL 28319 Added support for monochrome terminals Set the following in the runtime ini file to configure a model 5 monochrome terminal GUISys TN5250 TerminalType IBM 3477 FG SSL Connection ATL 29082 It is now possible to enable the SSL connection between the server and the host by simply configuring the cst server com CSTSSLSocketFactory class to be the socket factory implementation For example GUISys TN5250 SocketImplFactory cst server com CSTSSLSocketFactory Software AG Refer to the Appendix for further details SSL connection limitations The built in CSTSSLSocketFactory solution does not support 1 Client side of SSL encryption 2 ProxyServlet to server encryption 3 Server side of client to server SSL It s only designed to solve the secured Telnet use case All other combinations will still need to use extensions of the socket factory Changing XHTML Message Boxes ATL 27839 A new feature has been added which enables manipulating the text of a message box or
123. ontent of jar C 3IS921B29 JacadaFiles utils IzPack bin panels InfoPanel jar Adding content of jar C 3IS921B29 JacadaFiles utils IzPack bin panels LicencePanel jar Adding content of jar C 3IS921B29 JacadaFiles utils IzPack bin panels TargetPanel jar Adding content of jar C JIS921B29 JacadaFiles utils IzPack bin panels ShortcutPanel jar Adding content of jar C 3IS921B29 JacadaFiles utils IzPack bin panels InstallPanel jar Adding content of jar C 3IS921B29 JacadaFiles utils IzPack bin panels FinishPanel jar Building installer jar C JIS921B29 appls TEST921 install Runtimelnstallation jar Begin packaging Copying the skeleton installer Copying 10 files into installer Merging 7 jars into installer Writing Pack 3 TEST921 End packaging Packaging time 4 1 seconds Runtime installation C JIS921B29 appls TEST921 install Runtimelnstallation jar created Once the packaging is done the installer window is launched automatically If you do not wish to proceed with the runtime installation on the local workstation click Quit The installation files are created in the following path lt JISRoot gt appls lt AppName gt install The runtime installation is now ready to deploy to a remote machine To continue the installation on the local workstation Step 1 click Next Software AG di IzPack Installation of TEST921 Saf x Welcome Step lof 7 Welcome to the installation of TEST921 1 0 T
124. or the JIS server to use Https and SSL when communicating with the client the server has to have access to a Java keystore in which the private key and the server certificate are stored In previous versions the process of creating the keystore was manual using the keytool command line utility Now the JettyKeyStore file the private key and a test certificate are generated automatically the first time the server is started thus providing the ability to use HTTPS and SSL out of the box with minimal additional configuration Upon startup the server checks if one of the following flags is enabled in the jacadasv ini General JavaClientSSLEnabled 1 or Http SupportHTTPS 1 If so the server looks for a file named JettyKeyStore in its classpath If this file exists the server loads it and uses it as its keystore This allows users to continue to use their existing keystore or create a keystore with unique properties which cannot be created automatically When the file does not exist which is always the case for a new installation the server generates a new keystore file in the lt JISRootDir gt JacadaFiles classes folder with the name JettyKeyStore and creates an X509 server certificate based on information provided in the jacadasv ini KEYSTORE section The KEYSTORE section contains a number of settings which provide the information necessary for creating an X509 certificate Domain represents the network DNS name of the
125. orts communication which is the default communication method can now setup SSL communication without writing Java extensions When starting the Server for each server process two ports will be created for SSL communication in addition to the two existing ports used for plain text communication Furthermore plain text communication can be disabled thus forcing the user to use the SSL option The following jacadasv ini settings control the SSL configuration JavaClientSSLEnabled enables the SSL communication with the Java client Possible values 1 O default value 1 JavaClientSSLOnly when set disables plain text communication ensuring that the Java client uses SSL communication Possible values 1 O default value 0 SSLServerPortRange determines the ports used for SSL communication The default range of values that can be used for a single process configuration is 1200 1201 The port range needs to be large enough to allow each server process to allocate two SSL ports just like the allocation process for the plain text ServerPortRange By default both SSL and plain text ports are open on the server side To configure the Applet to use SSL communication do one of the following Set the Applet parameter lt PARAM name UseSSL value true gt Possible values true false default value false Other clients not using this Applet parameter can still communicate using plain text Alternatively set the JavaCli
126. ote If the regular expression defined in a selection rule didn t match the control name the control s string will not be written to the resource file i e the less specific selection rule will not be evaluated for this control Note All examples below assume the controls have data flow in ACE Strings of controls without data flow are written to the resource file no matter whether or not they match the selection rules Example 1 The following are examples of the LocalizationExpressions section in the Specific ini file LocalizationExpressions LOGIN PictureButton S LOGIN A11 M PictureButton R ES In this example PictureButton control strings in the LOGIN sub application will be written to the resource file if their name starts with the letter S All other controls in the LOGIN sub application will be written to the resource file if their name starts with the letter M PictureButton controls in all sub applications other than LOGIN will be written to the resource file if their name starts with the letter R All other controls that are not PictureButton type in all other sub applications other than LOGIN will be written to the resource file regardless of their control name Example 2 LocalizationExpressions AAT ME 31 DDS 5 In this example all control strings that do not start with the prefix DDS will be written to the resource file and localized in runtime according to the user s locale
127. pattern definitions based on these attributes Now the user interface has been added for these character attributes The new user interface is only enabled for the Horizontal group and Vertical group pattern definition types A new tab was added to the Pattern Definitions View dialog box Parameters Extended Info Set location Type Horizontal Group all Include Exclude Text color 19 o C Blaci y Background color C C Black y Underline e Cc o C Reverse image O Each line in the dialog represents an attribute that could be set for this definition All the definition will have no effect on pattern matching this is the default value Include the pattern definition will match only if the matched location on the screen includes the attribute definitions Exclude the pattern definition will match only if the matched location on the screen does not include the attribute definitions Software AG The color combo boxes are disabled when the corresponding All radio buttons are checked Limitations When matching patterns according to the Reverse image attribute define Include Reverse image and Exclude Underline Detailed Description of Version 9 2 1 Detailed Description of Version 9 1 2 Fixes 58 Note The number at the beginning of each ticket item represents the external support system incident or internal tracking number Installation SI 1033305 When updat
128. pdates the View Host Screen page to present the current host screen and reflect changes to the Show Line Numbers and Show Attributes checkboxes Save button saves a screen image file on the server machine The screen image is saved as a panel file in the logs folder of the server The View Host Screen page displays the path to the saved file on the server machine Download button downloads a screen image file in panel format to the client workstation Print button prints a textual representation of the screen image to the workstation printer Note Screen image files are saved as pnl files This panel file type is used for creating screen images from a screen capture in the design environment During development the Save and Download actions differ only in the path where the screen image file is saved However in production configuration using the Save button for saving the file on the server side provides the system administrator additional information Software AG about the subapplication name session number and process id of the screen image from which the file was saved Simplify Redirection Proxy Configuration The function of the XHTML RedirectionProxy servlet is to expose the multiple processes used by the server using a single Http s port to an external client Historically this servlet was designed to be deployed separately from the server itself into an external servlet engine such as Tomcat However
129. ptions and the client session dump are logged both to the Java console and to the client log SI 5061479 When adding a custom copyright message to your application in ace ini or ace400 ini which includes the ASCII OxA9 character the symbol was not displayed correctly in the Java client Help About dialog also causing problems localizing the copyright message SI 5056228 This issue is regarding the code sample in Java_Client pdf page 264 Methods for Controlling the Java Client Application Software AG Make sure that any updates to the Java client window are performed using the AWT event dispatch thread so that the code sample on page 268 inside the run method should look like this EventQueue invokeAndWait new Runnable Dolte vorc wady i login userField setText guest login passwordField setText foobar SI 5058523 All HTTP communication is now run within privileged action context XHTML Client SI 5057726 In a Y N checkbox when the value on the host was Y the checkbox was still displayed as unchecked JIS 599 When using OptimizeStyleAttributes 1 folded tables were not displayed correctly JIS 1043 Line and border colors in Safari were incorrect JIS 1038 The page size optimization feature did not work correctly with the redirection proxy SI 1033559 Submitting a page while the focus was on a Combobox or on a label within a table did not always send the correct focused control to t
130. r is calculated based on the current button text Radio group in order to determine the default component size the width factor is multiplied by the longest Radio item Tab header no change Tab headers already have a setting similar to width factor named Converter AddTabX The AddTabX setting can be used to increase the width of the tab header by a given number of pixels The width factor settings can be configured in the Window Options dialog box in a new tab named Control Sizing The Control Sizing tab includes previously supported control sizing parameters as well as the newly supported parameters The new parameters include radio group width table header width and button width The new setting Resize components without data flow was introduced in order to maintain backward compatibility By default the checkbox is unchecked so that components which have no data flow will not be resized Select this checkbox so that the various width factors will also affect the controls which have no data flow Software AG Window Options Eg Control Algorithms Control Sizing Control Editing window Algorithms Grid Attributes Resize components without data flow i Edit width Factor 121 il Static width factor 100 Radio group width factor Table header width Factor Button width Factor Group Box width factor 100 T Edit height factor 138 Group Box height Factor 100 xl Resize Pus
131. rRedirection 1 Proxy Servlet to Server Direct Communication The JISProxyServlet which is used for Http tunnelling of the Java client communication to the server is now part of the server itself Each server process can also serve as a JISProxyServlet In previous versions even though both the proxy session and server session were running in the same server process the communication between them was managed using socket Software AG communication In our recommended configuration this works well the proxy servlet is running as part of the integrator process 1 0 and communicates with the other server processes using sockets with localhost address However when scaling the server to over 1000 concurrent sessions this architecture has the following limitations 1 each proxy session creates two sockets to the worker process and spawns two threads to listen on these sockets This creates a large number of threads which may exhaust the resources of the Java process or the server machine itself 2 When the server is under heavy load garbage collection cycles start taking significant time If one of the processes is performing a lengthy garbage collection cycle and the other process is waiting for information the result is EOFException and SocketException errors causing sessions to disconnect To improve the scalability of this architecture we have now introduced a new behavior triggered by the following jacadasv ini setting JISPro
132. ration xml file and the old ProxyConfigurationFile jacadasv ini setting to locate it the settings in this file are still in use However we recommend moving the existing proxyConfiguration xml settings to the jacadasv ini RedirectionProxy section and deleting the proxyConfiguration xml file The sequence of looking up the parameter values is 1 proxyConfiguration xml 2 RedirectionProxy section in jacadasv ini The actual settings being used in runtime can be monitored by looking up the RedirectionProxy configuration message in debug_1 0 log at debug level 50 or higher If specific settings do not exist in both of these files then the following defaults are used Server name set to the IP address of this server Port number set to the port of the root process All other parameters are set to their default values Following this enhancement the only jacadasv ini settings required for setting up the integrator process 1 0 as a redirection proxy are GeneralParameters MaxProcesses lt Value larger than 2 gt Detailed Description of Version 9 2 1 17 18 M1 Integrator Sessions MaxProcessSessions 0 Having these two settings in your jacadasv ini will enable the RedirectionProxy on the Http s port used by the integrator process Secure Single Signon Implementation using Redirection Proxy JIS XHTML now supports a secure mechanism for passing user credentials from the client browser to the mainframe Pre requisites e
133. rent types of errors that may occur and how to handle them Error Type Reasons for Error What to Check Syntax errors in Malformed XML i e XML tags e Verify the syntax of the buildapp xml not closed XML Children tags appear outside of e Verify that the XML parent tags conforms to the DTD Missing values in XML missing attributes Logical errors in e Trying to generate a runtime e Manually execute the buildapp xml that is not allowed for the same operations from application by the CDKey the ACE UI e Creating a runtime installation before the application was ever compiled We recommend performing the operations the first time manually using ACE in the same order as in the buildapp xml and verifying that they work properly before using the automatic mode Limitations The following known limitations exist e The feature is certified only for the following product flavors e JIS XHTML for 5250 e JIS Java for 5250 e JIS XHTML for 3270 e JIS Java for 3270 e The main window of ACE is still visible in automatic mode e The operation Create J2EE Runtime Installation requires that you Generate Runtime for the application and all of its libraries at least once from within ACE Otherwise you get the following Perl error Error Key libraries not found in section program at AAperllgen HierarchyFile pl line 69 Workaround Generate the runtime in automatic mode then edit the runtime INI lt application gt ini and ad
134. s a selection rule The structure of the rule is SKey SValue Using Key define the sub application name SubApplicationName and control type ControlType Control types can be one of the following values All GroupBox Frame TabFolder DynamicGroup Dynamiclteration PushButton CheckBox RadioButton RadioGroup CheckBox OwnerDrawPushButton PictureButton Link Static Table Edit Window Prompt EditMultiline Tabs Menu MenuItem or CheckboxMenultem The format of the Key token can be one of the following SSubApplicationName ControlType SSubApplicationName All Detailed Description of Version 9 2 1 75 76 SControlType All The format of the Value token is a standard Perl regular expression for matching a control s name A comprehensive introduction to Perl regular expressions can be found here http perldoc perl org perlre html Regular Expressions Order of Evaluation When more than one selection rule matches a control name the order of evaluation is as follows A selection rule for a specific control type in a specific sub application takes precedence over a selection rule set for All control types in a specific sub application A selection rule for All controls in a specific sub application takes precedence over a selection rule set for a specific control type in all sub applications The All definition all control types in all sub applications is used if no other selection rule matches a control N
135. s an example of the required properties Property name Description Default value lt Map name gt IS WINDOW TRUE specifies that the current map FALSE represents a window lt Map name gt WINDOW BASE This property is equivalent to the 1 1 DEFINE WINDOW command BASE clause Only the BASE operand3 operand4 format is currently supported The BASE TOP BOTTOM LEFT RIGHT and BASE CURSOR options are not supported lt Map name gt WINDOW SIZE This property is equivalent to the AUTO DEFINE WINDOW command SIZE clause The options SIZE operandi operand2 and SIZE AUTO are supported The SIZE QUARTER option is not supported lt Map name gt WINDOW FRAME This setting is always 3 characters Blank border long The 1st character represents the corner character The 2nd character represents the horizontal border and the 3rd character represents the vertical border lt Map name gt WINDOW TITLE This property is equivalent to the No title DEFINE WINDOW command TITLE clause lt Map name gt WINDOW COLOR _ This property is equivalent to the The neutral DEFINE WINDOW command FRAMED color NE Detailed Description of Version 9 2 1 45 46 CD frame color clause The list of possible color values is specified in http documentation softwareag com natural nat821mf parms sp_cd htm 2 In the Create Screen Images Wizard select the relevant Natural map file representing the Natural popup window content When creating the new subappl
136. s are not digitally signed In order to eliminate this message during development reduce the Java Plugin security level to Medium or add the server address and port to the Exception site list as shown below These configurations are accessible from the Java Control Panel Security tab General I Update I Java ES Y Enable Java content in the browser Security Level a gt High minimum recommended Medium Java applications identified by a certificate from a trusted authority will be allowed to run Exception Site List Applications launched from the sites listed below will be allowed to run after the appropriate security prompts http localhost 8080 A https localhost 8443 gt Edit Site List Restore Security Prompts Manage Certificates Now restart your browser and launch the Java client Applet again You ll now receive the following confirmation dialog Do you want to run this application An unsigned application from the location below is requesting permission to run Location http localhost 8080 More Information Click Cancel to stop this app or RUN to allow it to continue Software AG Click the lt Run gt button to launch the Applet The XHTML client has been tested with the following operating system and browser versions Operating System Browser Windows IE 8 1E11 Windows F
137. s in Version 9 2 1 Runtime Installation The discontinued Wise Installation Studio product which used to be the JIS recommended tool for creating the runtime installation is no longer supported by its vendor We have now introduced a new runtime installation procedure based on the IzPack product IzPack is a widely used tool for packaging applications on the Java platform IzPack is open source Apache license and free IzPack is now part of the JIS product installation so there is no need to purchase a 3 party tool By using IzPack we provide the same level of functionality and configuration of the Wise runtime installation but at no additional cost and with simpler installation procedure The IzPack installation supports the following existing Wise functionality Graphical user interface Full installation and library update Windows and Unix installation Configurable installation scripts which customers can re brand Creation of menu shortcuts on Windows platforms Creation of Windows executable NuURWNFH In addition IzPack also supports 7 Headless and X Windows based installation on Unix platforms 8 Readme and license agreement dialogs 9 Packaging and signing the Java client Jar files as part of packaging the runtime installation Limitations 1 The runtime installation wizard will no longer generate a text file with the list of files to install 2 Installing the runtime on AS 400 is no longer supporte
138. s jrodefaults ini classes license dat classes proxyConfiguration xml classes proxyHttp xml classes ServerConfiguration dtd classes ServerConfiguration xml classes JettyKeyStore classes cst jacadasv jar 4 The ResourceBase property now defaults to the RtRootDir property Backward compatibility In this release action definition names specified in ServerConfiguration xml such as Xhtml or FreeSession are case sensitive they were case insensitive until now JIS recognizes action names as they are written in ServerConfiguration xml or as all upper case or as all lower case For example the action FreeSession can also be used as FREESESSION or freesession Detailed Description of Version 9 2 1 83 84 Running the JacadaProxyServlet as part of the JIS Server The Java client can now communicate directly with the JIS server using HTTP S without having to deploy the JacadaProxyServlet to an external Servlet engine The Servlet is now run using the embedded Jetty 6 1 servlet engine To configure a client to connect to the server using HTTP add the following Applet parameters lt PARAM name UseHttp value true gt lt PARAM name UsePorts value false gt In addition a new html page lt ApplName gt JavaClientHttp html is generated during Generate Runtime The page contains the necessary definitions for the Java client to connect to the server from which it was downloaded via HTTP S The embedded Prox
139. s possible to run more JIS sessions per process During our internal loadtests we found the sweet spot of sessions per process when using 64 bit Java to be between 500 and 800 sessions per process In addition the XHTML RedirectionProxy and the Java client JISProxyServlet become more scalable and can serve thousands of concurrent sessions per server Refer to the Appendix for further recommendations as to how to fine tune your server configuration The trade offs of using 64 bit Java vs 32 bit Java With regards to single session response times you shouldn t notice much difference 64 bit Java consumes roughly 50 more memory under the same load compared to 32 bit Java therefore if your server machine is tight on memory consider increasing the amount of physical memory installed on the server machine The product is still shipped with a 32 bit Java version for the following reasons 1 some development machines still use 32 bit operating systems and therefore cannot run Java 64 bit 2 The Application Verifier component loads 32 bit only resources in order to compare the inner workings of the new version of JIS with previous 32 bit only versions The ability to run the server using 64 bit required a complete rewrite in Java of the remaining server components which were written in C and were not 64 bit compatible This internal change is one of the most significant changes made to JIS since version 9 0 has been released in 2005 In order to ru
140. s that can be invoked via JIS Administrator command line interface Shutdown Restart Suspend Resume and Status Connecting to the server using a JMX client application You can connect to the JMX server using via the client or using Java code Detailed Description of Version 9 2 1 71 72 Connecting via the client JConsole New Connection New Connection Local Process Name sun tools jconsole JConsole com jacada jis runtime tools sndtrace SendTrace t v 4 lt cst server module ServerModule d70 a1 D Program Files eclipse plugins org eclipse equinox launc cst server module ServerStarter d70 com jacada jis runtime server util NodeRegistry d70 al Remote Process service jmx rmi indijrmi localhost 2100 jmxrmi Usage lt hostname gt lt port gt OR service jmx lt protocol gt lt sap gt Username controlRole Password eooo o el Connect Cancel Log remotely to service jmx rmi jndi rmi lt hostname gt lt rmi port gt jmxrmi where hostname is the IP address or hostname of the running JIS server and the port is the port configured in the server registry node this is the first port specified by the jacadasv ini GeneralParameters RegistryPortRange ini setting Enter a username and password Two users are defined by default a read only user username monitorRole password monitorRole a
141. s the screen image type lt Back C MFS Cancel Note Before continuing to the next step please make sure that you have copied your source files to a directory of your choice on the PC Natural Help C SDF 1 In the Create Screen Images Wizard in the Select Screen Images Type step select Natural 2 In the Select Source files screen select Natural map source files to compile NCD where each file represents one or more maps NSM where each file represents a single map 44 Software AG Creating Popup Windows from Natural Maps The Natural map does not contain information as to whether the map should be displayed as a popup window in runtime and what the popup window s borders should be Therefore in order to support creating screen images for host popup windows the border of the window must be defined Popup windows in Natural are defined using the DEFINE WINDOW command http documentation softwareag com natural nat82 1mf sm definewi htm JIS uses properties similar to the ones used by the Natural DEFINE WINDOW command to display the pop up window border in design time as close as possible as to how it would be displayed by Natural during runtime 1 In order to achieve this the following properties need to be specified per window map in the natural_parser properties file in the lt AceRoot gt folder Define the following properties for each window map The existing properties file provided with the product provide
142. security risks SI 5061285 There was a memory leak related to JMX when running the server using Java 1 5 JMX is now only enabled when using Java 1 6 and above JIS 1075 In the JIS Administrator the parameter transaction per minute sometimes displayed zero even though the server was actively executing transactions Innovator SI 5015378 The table selection was not removed even when the table was not in focus Software AG Limitations Limitations for JIS version 9 1 2 When creating a screen image from any SDF during design time the field colors used by the color table are always considered to be Green regardless of the real field color If you use a screen capture the color table works correctly In runtime the color table is correct JMX is not supported when running the server using Java version 1 5 XHTML host printing You need to click twice on the Connect Disconnect button in order to connect disconnect the printer from the host When running the Java client un signed Applet and the JISAdminServlet an Exception related to the crossdomain xml file is logged to the Java console When running the JISAdminServlet the online help dialogs are no longer available When clicking on the X button to close the server console window though the window is closed not all server processes are terminated We recommend that you always close the server using the QUIT command or using the JIS administrator When usin
143. src SApplicationRootDir appls TABLE resources testl js gt lt script gt New Features in Service Pack 9 0A00 XINIT keyword in BMS maps now supported The screen image creation process now supports the presence of the XINIT keyword in a BMS file without codepage considerations The XINIT keyword in BMS maps allows the mapfield to be initialized to a hexadecimal value A character with a value less than 0x40 is considered to be a terminal control character and is replaced with a blank Maximum permitted size of ACE method increased The maximum number of lines in a single Ace method has been increased to 2048 Until now the limit was 512 lines Detailed Description of Version 9 2 1 113 114 Print setup dialog can be skipped When printing the current window the Java client always shows the Printer Setup dialog allowing the user to choose various printing options including page type page orientation print destination and so on You can now eliminate the display of the printer setup dialog if you so choose To eliminate the display of the printer setup dialog add the following parameter to the html page lt PARAM name ShowPrintDialog value false gt The default value is true New methods for setting colors of selected cells New APIs have been added to the Java client GUITable component for setting the background and foreground colors of selected cells To set the background color in which selected cells are t
144. st popup and only if it fails it identifies it as JITGUI Normally host popup screens are sent by the host so that the cursor is positioned inside the popup borders The screen interpreter uses the cursor position as a starting position for locating the popup borders In rare cases the host popup is sent by the host with the cursor positioned outside of the popup border In this case JIS tries to simulate various cursor positions for locating the popup borders The drawback of this approach is that when the screen is not a host popup valuable time is wasted In order to try and optimize the way popup host screens are searched for and identified when the host cursor is not positioned inside the popup window border a new set of parameters have been added These parameters enable defining a more exact way to search for the host popup borders on the host screen and also offers the option not to search for popup borders at all The behavior is controlled by the following new runtime ini setting in the ExtendedPopupBorderSearch section Enable 0 1 when set to 0 no cursor positioning will take place and as a result a host popup is only identifiable if the cursor is inside the popup border Set the value to 0 if your application makes extensive use of JITGUI and if you are sure every host popup includes the cursor inside its borders O will be the default for new applications otherwise the default value is 1 to maintain backward compatibility S
145. stallation and before deploying the application ear file add the jar files placed in the common installation lib folder into the application server s classpath As of JIS 9 0 4 the jar files are jacadasv jar Tidy jar sac jar cssparser 0 9 5 jar Adding jar files to an application server s classpath is an application server specific procedure Please consult your application server documentation Specifically adding jar files to the WebSphere application server is documented in the XHTML user guide Software AG Upgrade to Jetty 6 1 The embedded Jetty web server bundled with JIS has been upgraded to version 6 1 19 In addition a few more configurations have been introduced 1 The ability to use HTTPS only and disable the HTTP port Use the following jacadasv ini setting HTTP SupportHttpsOnly 1 2 The ability to disable directory browsing Directory browsing is enabled by default Use the following jacadasv ini setting to disable it HTTP AllowDirectoryBrowsing 0 3 The ability to hide some of the server resources from the client HTTP ProtectedResources classes MyFile1 txt classes MyClass class When trying to access these resources from a URL such as http myserver 8080 classes MyFile1 txt the client will receive 404 response The following resources are protected by default classes http xml classes jetty jmx xml classes jacadasv ini classes jacadasv policy classes jcedit res classe
146. t lt AdditionalFiles gt lt File Name c temp debug_1 log Target WEB INF Lib gt lt File Name text2 Target WEB INF classes gt lt AdditionalFiles gt lt CreateRuntimeInstallation gt lt OpenApplication gt lt Pack File c temp packtest jpk Name TEST2 Libraries AGGitentoncehiles 07 gt lt Unpack File c temp myapp jpk Type Java Target MYAPP InputDirectories DDS SDF Screens OutputDirectories MakeExe Runtime Install IncludeExtraFiles True Existing Replace ConfigurationFiles A11 gt lt Unpack gt lt Ace gt For the complete DTD which describes all possible attributes refer to the Buildapp DTD Logging When running ACE in automatic mode the following log is created remote log in the ACE root folder The log begins with the contents of the buildapp xml file The remote log reports the progress of the operations listed in the buildapp xml file In addition information is also logged to the standard logs created by the Generate Runtime and Pack Unpack Wizards 100 Software AG Error Handling When there is an an error in any of the operations in the file processing will terminate immediately This prevents the accumulation of several problems one on top of the other For instance if generating the runtime fails then creating a runtime installation might create an installation of the previous version The following table describes diffe
147. t are the application ear war file generated by the Application Server runtime installation since there is no longer a common installation and administrator application The administration utility is now bundled inside the application ear war file and can be launched by adding admin to the application URL A new wizard step in the create runtime installation wizard selects the directory to which the configuration files are extracted and log files are written Create Runtime Installation Wizard Select Web Application Root Directory Select the directory where you would like to place your web application s configuration Web application resource directory and log files The web application will create this directory on the machine running the application fe 1ISCommon server Configuration and log files are automatically created in this directory when initializing the web application Make sure the directory path is valid for your selected platform and that it has write dadi x In previous versions this step was performed by the common installation This step is optional If the selected folder is left empty the code will by default create the resource files and server logs in the application server s temporary folder The Web application resource directory entered is written into the RootDir servlet parameter in the application s web xml During the deployment of the web application to the application server it will creat
148. tartRow first cursor row position default 5 RowStep number of characters to advance the row with each attempt default 7 StartColumn first cursor column position default 27 ColumnStep number of characters to advance the column with each attempt default 27 Client Specific Device Name Assignment This enhancement enables generating AS 400 device names which are based for example on the user name or computer name of the workstation running the Java client It therefore enables associating an AS 400 device name with the workstation from which the connection originated thus enabling better trace ability for the host administrator JIS behavior before this enhancement Software AG When connecting a display session not a printer device to an AS 400 the display session was assigned a device named QPADEVxxxx where xxxx is a unique value assigned by the AS 400 When connecting a display session specifying a device name using the LUName ini setting such as MYDEV then by default if the device name is not in use it will be assigned to the session but if the device is already in use i e device name collision occurred the session will be disconnected by the host and automatically reconnected without specifying a device name thus getting a QPADEVxxxx device name The enhancement is divided into the following tasks 1 Passing the device name from the client to the server to override the LUName ini setting value 2
149. te However Windows 8 based mobile devices are still limited to using IE10 In JIS XHTML our approach is to render pages for IE11 using the same codebase used for Firefox Chrome and Safari Going forward this allows us to introduce new Html5 features into the product without duplicating our efforts on two different code bases IE vs non IE However this implies that pages rendered by 1E11 look slightly different than pages rendered using older versions of IE IE10 is still supported using the old IE codebase However when working in default mode some table and date control functionality is not supported Our recommendation to customers is as follows Xhtml client IE11 is fully supported for both desktop and Windows Mobile devices IE10 on desktop should be used in compatibility mode IE10 on Windows Mobile devices can be used as long as no tables and no date controls exist IE9 and earlier we ll support these versions as long as they are supported by Micrososft but no new features will be introduced for these versions Java client In general the version of IE has little impact on the Java Plugin running the JIS Java client We will support any IE version as long as it s supported by the Java Plugin itself Server Remote Management JMX based tools such as Oracle s JConsole and Visual VM can be used to monitor the Java process CPU utilization memory allocation garbage collection and thread usage By default these tools
150. tely just like debug level 0 in previous versions XHTML JavaScript Client Log The XHTML client logging feature is able to log debug messages from the JavaScript used by the browser to the JIS server log This mechanism now has the following improvements e The default level is now 1 and is automatically activated there is no longer a need to send the ClientDebugLevel URL parameter in order to activate it e JavaScript exceptions and their stack trace are now written to the Server Log by default e It is now possible to print complex messages which contain HTML text e It is now possible to print messages to the server log during the loading of the page e It is now possible to send the same message text more than once e The message text no longer appears in the thread name making the text in the server log easier to read e Messages are written to the log in the order that they are sent from the client Software AG Keyboard shortcut for Java client Print GUI The Java Client ALT P keyboard shortcut now enables printing the active window for all windows including pop up windows Use the following example to customize the default keyboard shortcut For example the following settings will change the Print GUI shortcut key to Ctrl Shift X lt PARAM name PrintGuiKeyModifier value Ctrl Shift gt lt PARAM name PrintGuiKey value X gt Localization Improvements Localizing Dynamic Control Strings JIS suppor
151. thods from the lt subapplication gt sa file or CGUIMESS RECOM app eae dom param id trigger id of the method as written in the Ss EfoyOlwGe LOM Ci sa file param wait true to lock the current thread s execution until VEINS ACEON ALS also exception IllegalStateException if the method is invoked from the CommServer thread S public void activate int id boolean wait Printing A number of changes were made to the way printing is handled Support for portrait and landscape printing Detailed Description of Version 9 2 1 109 The Printer setup dialog for the Java and XHTML clients now supports printing both portrait and landscape printouts Enabling specifying margins You can now specify the margins in the Printer setup dialog instead of using the default one inch margin Enabling specifying the paper size You can specify the paper size in the Printer setup dialog or in the applet parameters using the PrinterEmulationPaperType setting lt PARAM name PrinterEmulationPaperType value A4 gt lt PARAM name PrinterEmulationPaperType value LETTER gt Improved handling of underlines in print output Underlining in a print output now works For example characters are no longer misaligned Enabling printing to any printer You can now print to any printer defined on the network and not just to the default printer New printer parameters The following para
152. tion Software AG In addition Java now supports the pack200 compression algorithm which compresses Jar files to up to 30 of their original size The following changes were implemented in the product to adapt the Java client deployment procedure to take advantage of these changes 1 The old clbase jar clbase signed jar and clfull signed jar were replaced with a single client Jar file named clbase jar This file is equivalent to the old clfull signed jar and is digitally signed by Software AG In addition the product now includes the clbase jar pack gz file which is a compressed pack200 package generated from clbase jar 2 Similarly the administrator utility jar file jam jar is now digitally signed and a pack200 compressed package jam jar pack gz is distributed 3 The product now generates only a single lt AppName gt html Java client launcher file pointing to the clbase jar file 4 The archive attribute of the Applet tag now contains the APPL_ARCHIVE token During the packaging of the runtime installation this token is replaced with a list of Jar files generated by the new IzPack runtime installation The runtime installation generates and optionally signs a Jar file per application library Running the Java client in the development environment The generate runtime process generates Java source code based on the designed subapplications and compiles it into class files Since these class files are unsigned JRE 1 7 0_51 will not
153. tively both produce the exact same output Any problems are reported in the form of an exception error report into the server log file debug_verify log Pre requisites for running the Verifier 1 Full application generate runtime must be completed successfully after installing the new version 2 The 32 bit Java installation under lt JISRoot gt JacadaFiles utils jre must be used for running the server This is the default configuration 3 Use the verifier in the development environment not on a runtime installation To activate the Verifier from the command line type the following jacadasv v lt AppName gt Where lt AppName gt represents the name of the application you would like to verify The verification process will first iterate recursively over all the application and library folders and enumerate all the panel files It will then load the panels one by one and compare the identification results and pattern matching calculated by the new Java code to the ones calculated by the old C code If it finds a difference it will stop running and report the problematic panel file name More diagnostic information is printed to the debug_verify log file Detailed Description of Version 9 2 1 29 30 The Verifier will halt when finding a problem Report this problem to customer support and include the following information e debug_verify log e The pnl file for which the exception was generated e A full jpack of the application
154. torage Changes to the table component including column resizing and reordering can now be saved locally on the user s machine Changes made by the user during the session lifetime will be saved to the disk when a session ends and reloaded when a session starts In addition the user may save the current state using the File gt Save Storage menu item and restore the default state using the File gt Clear Storage menu items To enable the persistent storage feature add the following Applet parameter lt PARAM name PersistentClientStorage value true gt The persistent storage feature also requires working with the signed Applet and JDK 1 4 and above The persistent storage information is saved in a file named JacadaClientProperties xml created in the user s temporary files directory Table column reordering This feature allows interactive table column reordering during runtime by using the mouse to drag and drop columns In order to enable table columns reorder during runtime ales Make sure that the Drag columns checkbox is checked in the table control style tab in ACE 2 Add the following Applet parameter lt PARAM name AllowTableColumnDragging value true gt The column order initially defaults to the column order specified in ACE When the client persistent storage feature is enabled the new column order is saved for the specific client machine Note the following limitations e Folded table columns c
155. ts localization by means of externalizing static strings defined during design time into a resource file The process is explained in chapter 4 of the Java client user manual Until now the localization feature had a limitation that only static strings i e strings of components which do not have data flow in runtime were written to the resource file StringResource res The current enhancement adds support for selectively writing dynamic strings of controls i e strings of controls which have data flow into the resource file The dynamic strings that are to be written to the resource file are determined using selection rules These rules define where to search and what to search for using regular expressions When the control name matches the regular expression defined in the selection rule the control s string is written in the resource file Note that the general localization setup and procedures were not changed by this feature Localization of Control Strings in Design Time Dynamic control strings which match one of the selection rules are written to the StringResource res file during the runtime generation process The strings written are the strings which appear in design time as they appear in ACE design view Configuring the Selection Rules In the Specific ini LocalizationExpressions section of each library define rules to determine which control strings will be written in the resource file Each line in this section define
156. ttern Matching according to Character Attributes eeeeceeseeeseeeseecsseceaeceseceseceseeeseesseeeeeessaeeeaeeeaeeenaeenaees 56 Detailed Description of Version 9 1 2 Fixes esc ssac ccasscspalaesassbigenszeysuadeasesecededaadaqav besiavediadagh aesnaedquadeaeenets 58 Installation ida io oi cots bled ean a ir 58 JANMA Client oust O Ae alt Sat we et ae Ra ates Sat eles Wella oa ace acetate fact Act Glia Selina tee 58 XHTML Clic Iii iets eee peg Lele ae ek 59 DOLVEL EAA EEA TE eek ae ec ack eens tca st eases A sbeebs tacos ooh yest s Aiba ers Bites be eaubha act pueeaaees EA aeed 60 IN NR A NRO 60 Limitations ir idad diia 61 New ESatutesia Vet ona a 62 AIM A E A A oe A Pade ee a Lae Rapa a aes 62 DELVE CHANGES 2 OR O 62 Monitoring Improvements ir E R E E E E E E E N S 62 Localization IMpPr vements nerra ieie A dt A AAA RA E GA OER 65 AGE E A E E S E E E AE 65 2 Software AG Java Client Improyement cosilla 66 New iP A Version AA a Nr a ea a cae NIL an a LOMO ce tt eset 66 WebSphere 7 Support aii wails el Sai eee ee a A ee ae ee eee 66 Usability Improvements in the Generate Runtime and Run Application Wizards oooconnccnincnnncnnoncnnncnnnccnnnos 67 Restarting the JIS Serveis ori pai o 69 JMX SUpPOLtcaccess AA A A A A aera en ee 70 XHTML Page Size Optimization Improvements eee eeeescecssecssecesecsseceseceseceseesseesseessaeeeaeeeaeecsaecsaeesaecaeenaees 72 DELVE LOS isn A a era a ae ae eat cet 73 Java Chen LO gs pirita lil cdubesed ae
157. tween the standalone server and J2EE deployment In the standalone server the URLs start with classes for example src classes js jacada js href classes appls NRT xhtml CSS kb_IE css while in J2EE deployment the URLs start with the name of the application for example src NRT js jacada js href NRT appls NRT xhtml CSS kb_IE css Software AG All URLs created by the server code are automatically adjusted based on the server type standalone or J2EE However URLs added through user extensions java extensions javascripts htmls etc should be changed as follows to ensure that the same code base will function properly for both the standalone server and a J2EE server e In XHTML java extensions Use an API method that returns the correct URL prefix for the standalone server it returns classes and for the J2EE server it returns lt APPLNAME gt Get the application root dir Vv return String classes for standalone server lt APPLNAME for J2EE Server y public String getApplicationRootDir e In javascript extensions Use javascript similar to the following window addExternalJavaScriptFile context getApplicationRootDir appls TABLE resources test js e In the XHTML html extensions Use the template word ApplicationRootDir which is changed to classes or to lt APPLNAME gt as follows lt script language JavaScriptl 2 type text javascript
158. ubapplication variable value to a user variable while the subapplication is still alive and then access the user variable from the UserDestroySubApplication system triggered method SI 5080361 JIS 1197 When using Java client with the lt PARAM name RunInsideBrowser value true gt parameter and closing the session using the TotalExit method the browser displays an empty gray border instead of displaying the actual termination message JIS 1260 When installing a Unix runtime using the FTP option on Windows 7 the FTP command is blocked by the Windows firewall even when FTP is enabled You are required to either e Install the following Windows hot fix http support microsoft com kb 2754804 or Execute the following command on the Windows workstation netsh advfirewall set global StatefulFTP disable Detailed Description of Version 9 2 1 41 Appendix Optimizing the Server for 64 bit Java Version 42 Here are some best practices related to migrating the server from a 32 bit Java version to a 64 bit Java version Note The recommendations below are relevant only for a 64 bit Java version and not for a 32 bit Java version If you are not sure which version of Java you are running consult the Java Data Model debug print in the server log Q How much memory should I allocate for each server process when running using 64 bit Java A In general we recommend that every JIS process will be able to allocate at least 200MB
159. ully logging off the mainframe session In addition UserDestroyApplication is now invoked in case of abnormal session termination For example in case a Java client user closes the browser instead of closing the session window 5077748 JIS 1175 JIS 1389 WriteUserVariable amp GetUserVariables resulting in null UserDestroySubApplication is a system trigger method invoked by the server just before destroying a subapplication window when moving to another subapplication UserDestroySubApplication now has access to the destroyed subapplication variables Previously when using the system triggered method UserDestroySubApplication to access a specific variable using an expression line or using the GetVarValueByName DoMethod the variable value was retrieved from the current subapplication not from the destroyed subapplication 5094537 JIS 1285 JIS 1331 Running the server on Oracle Linux The server is now able to run on an Oracle Linux platform using the same procedures used for deploying the server to a RedHat Linux platform JIS 1360 JISAdminServlet requires entering user credentials twice This has been fixed 5085737 JIS 1224 JIS 1375 Security mismatch for password Clear text password is no longer logged when using the ANALYZER filter 5108408 JIS 1393 JIS 1397 Unexpected Host Screen occurs when using RemainInScreen True Screen interpreter related problem has been fixed JIS 1461 Data switched between sessio
160. void setSessionAttribute String name Object value Returns the object bound with the specified name in this session or null if no object is bound under the name Ey public Object getSessionAttribute String name Loading resources from an XHTML extension ATL 27368 It is now possible to load resources from an XHTML extension This method allows to read resource using ApplicationResourceLoader could be used in prop and J2EE server return InputStream Lav public InputStream getResourceAsStream String resource Software AG For example package appls DEMO1 xhtml user import com jacada jis runtime server frontend xhtml context import com jacada jis runtime server frontend xhtml general DocumentBuilderProvider import java io InputStream import org w3c dom Document import org w3c dom NodeList import cst debug Debug public class Appl implements com jacada jis runtime server frontend xhtml extension IUserPageExtension public Appl public void onPageLoad OnPageLoadContext context Document staticXml null String xmlFilePath appls context getLibraryName xm1 context getSubApplName xml InputStream is context getResourceAsStream xmlFilePath try staticxml DocumentBuilderProvider getDocumentBuilder parse is catch Exception e context setSessionAttribute staticxXml staticXml do some pro
161. xyServlet IsOverrideConnectPort 1 When using this setting the proxy servlet creates the server session in the same process on which it is running and communicates with the server session using direct calls instead of using socket communication This enhancement improves performance and prevents disconnects caused by garbage collection since all communication is performed by the same server process In addition the number of threads per session is reduced This configuration can be used in two scenarios 1 Single process server 2 Multiple process server behind a load balancer where the load balancer is responsible for distributing the sessions between the worker processes Limitations in multiple processes configuration connecting a client to the root process still uses socket communication Make sure clients connect directly to the worker process 1 1 1 n Support Underline and Strike through Font Attributes The Strikeout and Underline properties in the ACE Font and Color dialog are now supported by the Java client Once defined in ACE these properties will automatically affect the font decorations used by the Java client In XHTML the Strikeout and Underline properties cannot be used together for the same component In case both are specified only the Underline property is used Solaris KSSL To support encrypted communication between the browser and the server the server is using Java S
162. yServlet always works in non persistent mode The request used for sending messages from the server to the client is closed by the server and opened by the client after specific protocol messages This ensures that the client does not keep an open connection to the server for long periods of time Configuration When using the embedded ProxyServlet the following jacadasv ini settings replace settings which were configurable in the web xml when deploying the ProxyServlet as a standalone component JISProxyServlet HideException hide exceptions thrown by the ProxyServlet from the client default 0 EnableTestServlets enables the test servlets for researching communication problems default 0 GetClientIPFromHttpHeader allows to retrieve the client IP from an HTTP header default 0 ClientIPHttpHeaderName the name of the HTTP header from which to read the client address default is empty Logging The embedded ProxyServlet writes log messages to the standard server log There are no longer jac lt sessionid gt log files Backward compatibility You can still package the standalone JacadaProxyServlet classes and deploy them to your desired servlet engine However it is recommended to start planning their migration to the embedded proxy servlet The HTTP communication mode is optional You can still use the standard ports communication The HttpDebugLevel applet parameter is now obsolete Software AG Reduction of the

Contents of Version 9.2.1 - JIS Mobile Demo

Contents

Download Pdf Manuals

Related Search

Related Contents