The product versions described in this chapter mainly use the same modules. Even if workflow processing is sometimes driven by the application and sometimes by the Internet pages, the two architectures only differ in one control. The Contents Std control is used for control from the Internet pages. Parame- terization enables an application Step to be activated. For each of the possible 20 return codes a link to another Internet page can be specified. The Contents ATM control, which is used for the Web-Extensions/ClassicLink, has a far simpler design. In this case, it is only the page timeout that will normally need to be specified.
Similarities and differences Selecting the product version
The component of the Graphical Service, CCDialog.exe, is identical in all versions. All controls, apart from the two Contents controls, are used in both architectures. The Web-Extensions/ExtraLink version does not have its own control, as it uses the other two versions.
The handling of input fields, input checks and list boxes is identical in all archi- tectures. In the case of Web-Extensions/ClassicLink there are no menu buttons, as each button in this architecture responds to the interface with a return code, while menu buttons are configured for links to Internet pages.
The method for calling external Internet pages differs in the two architectures. In the case of Web-Extensions/HyperLink, it is only necessary to configure a link in a menu button or selection button. With Web-Extensions/ClassicLink, an extension must be made to the Transaction Framework in order to load the first external page (see also section ’Loading external Internet pages’ on page 32). Configuration of the Restart Manager is identical in all architectures (see also section ’Restart Manager configuration of Web GS’ on page 584).
The chapters that follow contain many references to differences between the architectures. The pictograms below indicate the sections containing archi- tecture-specific configurations or features. All other chapters apply to all the architectures.
This pictogram indicates chapters which describe configurations for the architecture Web-Extensions/ExtraLink
This pictogram indicates chapters which describe configurations for the architecture Web-Extensions/ClassicLink
This pictogram indicates chapters which describe configurations for the architecture Web-Extensions/HyperLink
Web-Extensions/ExtraLink © S iem e n s N ix dor f In fo rm at io n s s y s te m e A G 1 995 P fad: d: \P ro T opa s \Web -E x te ns ions \D o c u \B o ok \T ra d it io nel lS ta rt e n .f m
Web-Extensions/ExtraLink
This chapter describes how Internet solutions or simple Internet pages are called from an application that was developed with ProTo- pas modules. It is necessary to make extensions to the application modules in order to switch the interface of the Web Graphical Service to the foreground and to load the first Internet page.
Let us start one Step earlier: For performance reasons, the Web Graphical Service must be started together with the application or, preferably, prior to the application so that the Standard Graphical Ser- vice overlays the Web Graphical Service. This is necessary so that the Web Graphical Service is initialized and ready to accept the inter- face functions.
To load the Web Graphical Service and to keep it in the background the Startpage must not contain any of the ProTopas/Web-Extensions Controls. Nor- mally in an Web-Extensions/ClassicLink or Web-Extensions/HyperLink archi- tecture the Startpage must contain the Contents STD/ATM Control. In this case, if the Standard Graphical Service should display the startup sequence, the startpage can contain any background, but none of the controls. To advice the Web Graphical Service not to wait for loading the Startpage additionally the fol- lowing parameter has to be set to ’1’.
HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ ProTopas/CurrentVersion/ÁctiveX/
GraphicalService/ PCView
DontWaitForPCContentsOnOpen = 0x00000001 This Parameter must be activated on Web-Extensions/ClassicLink or Web- Extensions/ExtraLink!
Restart manager configuration
To work with Standard Graphical Service and Web Graphical Service, which both have the same framework name CCDialog, Web Graphical Service has to get another Framework name. In addition to the Standard Graphical Service, the Web Graphical Service must be started seperately in the Restart Manager section. As an input parameter, the new name of the Web Graphical Service has to be added:
Web-Extensions/ExtraLink HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ ProTopas/CurrentVersion/CCOPEN/ RESTART/ application1 CCDialog=C:\PROTOPAS\BIN\CCDialog.EXE,4,0,6,,, WebDialog
Web Graphical Service registers itself with this new name in ProTopas. This means, that all frameworks, which base on Web Graphical Service have to be started later than Web Graphical Service in the Restart manager section. Those frameworks are at least HTML Dialog Control, Check Framework and Transac- tion Framework. So it is the best to split up the application Parameter in application1 and application2, where application1 keeps all the parameters from application without HTML Dialog Control, Transaction Framework Pre- sentation Framework and Standard Dialog Framework, which keeps
application2. application1 may be started before Web Grafical Service and application2 after. HKEY_LOCAL_MACHINE/SOFTWARE/Wincor Nixdorf/ ProTopas/CurrentVersion/CCOPEN/ RESTART application1 application= C:\PROTOPAS\BIN\FwLoadPm.EXE,4,1,21,,,CCPresFW CCDialog CCTransactionFW HTMLDialogControl HKEY_LOCAL_MACHINE/SOFTWARE/Wincor Nixdorf/ ProTopas/CurrentVersion/CCOPEN/ RESTART application1 Programs=CCBase,CCBaseCtrl,application1, CCDialog,Appl_Check, application2,CCStart Data Dictionary configuration
The next problem is, that all Data Dictionary entries, which were registered for CCDialog have to be changed to WebDialog (name of the input parameter for CCDialog.exe). This may be done by calling
\ProTopas\Bin\CCRcConv \ProTopas\Conf\DatadictEx- traLink -t DataDict -b -U
Web-Extensions/ExtraLink © S iem e n s N ix dor f In fo rm at io n s s y s te m e A G 1 995 P fad: d: \P ro T opa s \Web -E x te ns ions \D o c u \B o ok \T ra d it io nel lS ta rt e n .f m
Changing the Transaction Framework
Inlude additionally the PCDialog.xpp and add a Proxy for WebDialog Class definition in the .hpp header file:
...
#include PCDialog.xpp #include CCDialog.xpp ...
private:
PCDialog myWebDialog; // proxy of Web Dialog CCDialog myDialog; // proxy of Std Dialog ...
Implementation in the .cpp program file: ...
// open the dialog frameworks myWebDialog.Open();
myDialog.Open(); ...
Two functions have been created for the switch to the foreground and, subse- quently, back to the background (see also section ’CCDialogFW.Activate’ on page 339).
z Activate(): Switches the Web Graphical Service to the foreground z Deactivate(): Switches the Web Graphic Service to the background. At the point in the application at which the Internet pages are to be called, the call first switches the Web Graphical Service to the foreground and then loads the Internet start page:
Implementation in the .cpp program file: ...
// Call ChangeLanguage to bring Web Dialog into a // mode, that it loads the next Internet page into // full screen mode and needs no content control // at next page
myWebDialog.ChangeLanguage(CurrentLanguage);
// Deactivate Std Dialog myDialog.Deactivate(); // Bring Web Dialog to top
Web-Extensions/ExtraLink
myWebDialog.Activate();
// Load Internet Startpage
rc = myWebDialog.DoDialog(’Start’); ...
This program section then waits until the Web Graphical Service responds with a return code. Meanwhile, the Web Graphical Service is active and it is not the self-service application that is responsible for handling the dialogs but usually a Web server. Following the return of the Web Graphical Service this is deacti- vated and the Standard Graphical Service again moved to the foreground. Implementation in the .cpp program file:
...
// Deactivate Web Dialog for SOP Requests myWebDialog.Deactivate();
// Bring Std Dialog to top myDialog.Activate();
// Check the returncode if (rc != CCDIALOG_ERROR) {
// Proceed in your code
rc = myDialog.DoDialog(’Menu’) ...
} ...
The Internet page Start.htm does not contain a control but only a script which calls the first page of the Internet solution.
Syntax of the HTML page script:
<SCRIPT ID=clientEventHandlersVBS LANGUAGE=vbscript> <!-- Sub window_onload() window.navigate("http://www.wincor-nixdorf.com") End Sub --> </SCRIPT>
On the last page of the Internet application, workflow processing must be returned to the application. Like the start, this is also executed in the script, by navigating to an Internet page consisting of a certain syntax:
Web-Extensions/ExtraLink © S iem e n s N ix dor f In fo rm at io n s s y s te m e A G 1 995 P fad: d: \P ro T opa s \Web -E x te ns ions \D o c u \B o ok \T ra d it io nel lS ta rt e n .f m
<SCRIPT ID=clientEventHandlersVBS LANGUAGE=vbscript> <!-- Sub window_onload() window.navigate("PCEvt:RC=0") End Sub --> </SCRIPT>
Syntax for sending return codes to the application
Identification that navigation is not taking place but that a return code is being sent to the application:
PCEvt:RC=n (n = 0 to -7, cf. description of return codes in the CCDi- alog.xpp)
The handling described above permits external Internet pages to be displayed. In addition, the Internet pages that are to be loaded must be declared to the Web Graphical Service (see also section ’AllowList’ on page 292).
Configuration of the start page
Originally the start page has to contain a Contents ATM Control, otherwise the Web Graphical Service does not return from the Open() function (see also sec- tion ’Starting the Web Graphical Service’ on page 303). In the Web-Exten- sions/ExtraLink architecture, it is often not possible to have a Contents ATM Control on the start page, because the Web Graphical Service will be switched to foreground when the Contents ATM Control is activated. Normally it should wait for activation in the background. So the parameter DontWaitForPCCon- tentsOnOpen (see also section ’DontWaitForPCContentsOnOpen’ on page 621) has to be set to 1. In this case no Contents ATM Control must be present at the start page.
Activating first page in Web-Extensions/HyperLink after Activate() If the main application is programmed in Web-Extensions/HyperLink architec- ture, and the second application is a Web-Extensions/ClassicLink application with web interface, and both applications shall not base on each other, there may be a problem to reactivate the Web-Extensions/HyperLink application at the end of the other. For this reasons, there is a parameter, which starts the first page after Activate() function call from Web-Extensions/ClassicLink appli- cation. This parameter is
Web-Extensions/ExtraLink HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ ProTopas/CurrentVersion/ÁctiveX/ GraphicalService/ PCView ActivatePageURL = C:\ProTopas\Web\English\restart.htm In this page the Contents STD Control may start the next Step, so the Web- Extensions/HyperLink application may continue.
Configuration of the High Level GS to work with SNIKEYCODES = 0 As mentioned in chapter Configuration of the softkeys (see page 586), the Parameter SniKeyCodes has to be set to 0. The High Level Graphical Service needs a special configuration to work with this setting. In the \ProTo- pas\Conf directory you will find a SetupHlgsKeys.cmd job, which is updating the Keys configuration for the High Level GS. Please update the con- figuration for the High Level GS, if you want to use it toghether with the Web GS.
Web-Extensions/ClassicLink Value of a softkey © S ie m en s N ix d orf I n fo rm a ti ons s y s tem e A G 19 95 P fa d : d :\ P ro T opas \W eb- E x te n s io ns \D o c u \B o o k \A us ta us c h Ob erf lae c h e. fm
Web-Extensions/ClassicLink
In this product version, the dialogs that were created for the ProTopas High Level Graphical Service are converted to Internet pages. In the best scenario, it is not necessary to make any changes to the corre- sponding application. This chapter refers to some of the special features of dialog conversion.
A dialog normally consists of numerous parameters which describe the appearance of a screen mask. When converting these to Internet pages, it is preferable to note the contents of the masks during runtime and subsequently to use an Internet page creation tool such as Microsoft’s FrontPage to implement them manually. An automatic conversion tool does not exist. The implementation rules of the High Level Graphical Service applies to appli- cations which are to be newly created and which require the ProTopas Script FW to control workflow processing, as described in the application Development Tutorial in the chapters Adding a Graphical User Interface and Adding Customer Input. Besides, this manual contains an extract from the
programming interface of the High Level Graphical Service - only the part which is identical to the Web Graphical Service (see also section ’Dialog Framework’ on page 322). The differences between the two Graphical Services are dealt with in the following chapters.
The Contents ATM control is used in this architecture. The Contents STD control is not applied here. All other controls are used together with all WebExtension architectures.