on 04-14-2008 4:21 PM
Hi all,
We are using integrated ITS. I created an internet service based on a SAPGUI transaction created beforehand, without selecting "ITS mixed mode". Then I created an HTML template from one SAPGUI screen of the transaction, choosing "Business HTML" as the "Generating style". I modified the template so that it is nothing like the SAPGUI screen, but a new look and feel, and published the complete service. However, whenever I test the service, the UI is always bringing up the webGUI screen that simulates the SAPGUI screen (with gray-blue backgroud and yellow input fields, etc). I have tried to clean the browser cache, and through SITSPMON, clean the system wide template and MIME cache. But the webGUI look and feel persisted whenever I start the service, either from the SICF or from "test service" from SE80. The parameters for my internet service are as follows:
~AUTOSCROLL 0
~GENERATEDYNPRO 1
~LISTSCROLLING 0
~POPUPS 1
~STYLE DHTML
~TRANSACTION Z_SERVICE
Can someone give me some pointers as to what I could do to bring up the new buinsess HTML codes in the template? (I have even tried to make it a blank HTML, but the webGUI still came up when I start service.)
Thanks !!
Jay
Edited by: Jay Yang on Apr 14, 2008 8:34 AM
Edited by: Jay Yang on Apr 14, 2008 8:37 AM
Hello Jay,
Where are the templates? Are they located in the service name > Theme 99 or somewhere different? Maybe you need the ~sources or ~theme parameter in SICF Gui Settings.
You can also do a webgui trace via SM50 to see where the ITS is looking for the templates.
Edgar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Edgar,
Thanks for the hint. My template is under the normal path of (from SE80)
ITS Services > Z_SERVICE > Theme 99 > HTML Templates > ZMyTemplate
In SICF, I defined the parameters for the service
~AUTOSCROLL 0
~GENERATEDYNPRO 1
~LISTSCROLLING 0
~POPUPS 1
~STYLE DHTML
~TRANSACTION Z_SERVICE
~FLICKERFREE 0
~DISCONNECTONCLOSE 0
~COOKIES 1
~THEME 99
I didn't define ~sources, because there is only 1 service(?). Could you give me some pointers as to where the template is published to (if I don't get the access the ITS server file system) and how to trace SM50 for that information as you suggested.
Thanks!!
Jay
Hello Edgar,
I changed the ~GENERATEDYNPRO to 0, and tested the service again and a short dump occured for " ITS_TEMPLATE_NOT_FOUND". so I am more convinced that the publishing of my template failed somehow. But I have been modifying and publishing some other services (in other packages) without problem. Could the "publish" site be different from one service to another?
Thanks!
Jay
Hello Jay,
please check your settings, especially for Publishing - where are your templates published to? And where do you expect them to be stored? If you are using an integrated ITS you probably publish the files to the local filesystem whereas the server expects them internally stored in the database.
After publishing you also must invalidate the template cache -> TX SITSPMON.
With best regards,
TJ
Hello Jay,
The only suggestion left is one that others have already left, clear the template cache in transaction SITSPMON.
The trace is easy to do, just go to SM50, set the trace level to 2 for DIA processes and only component WEBGUI. Run the Zservice and then find which workprocess was used, if you use ~generatedynpro 0 then the error page should have something like "w: 0" for workprocess 0. You can then view the trace by selecting the process number in SM50 and then choosing the "display file" button or in the menu Process > Trace > Display File. (The same traces can be seen via transaction ST11).
Edgar
did you try invalidating the ICM cache from SMICM txn?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.