Reinstall your client side java webstart. if you still face the same problem Search for the files starting with frog.jar and rename it. Before renaming the files you have to stop your j2ee engine.
Go to Administration tab in Java Engine - go to respitory tab - Javau2122 Web Start -go to Initialization status and see whether it is OK
As you know that, I just install Java 2 SE v1.4.2_15 also DEV system is running fine, only problem in QA and PR system
If I installed Java JRE6 which is included webstart, after that nothing works at all same messages comeup, you told me try to found frog.jar I couldn't found that file in my local hdd
can you please tell me how to check j2ee engine stop or running, is that i can found visual admin. ???
from menu: Administrator -> J2EE Instance (local) -> send soft shutdown -> with restart
Also in Administrator -> J2EE Cluster (Global) -> send soft shutdown -> with restart
If i do that, does will efect somewhere ?
-
If i go through SXMB_IFR - Start integration Builder web-screen and go administrator
and click Java Web Start Administration
Status: Initialization status shows: Okay, no problems detected so far.
in this screen has 3 options:
1. Re-initialization
This function will cause a re-collection of the client software at the next click on the startlink.
All jarfiles will be searched and provided in a global download area (sys.global.dir). Not previously signed jarfiles will be signed with a dummy certificate. A lock will be set, so that only one re-collection can happen at the same time
2. Re-initialization and force-signing
This function will cause the above re-collection and additionally a re-signing of ALL resources with a dummy certificate. The original SAP signatures of the jarfiles will be lost. It is recommended to use this function only in test systems. To get back the original SAP signatures the application has to be deployed again.
3. Delete lock
Delete lock This is a critical function. It is intended to be used ONLY if a previous re-initialization terminated abnormaly and the reconfiguration lock has not been deleted.
Use this function if you are sure that no re-collection thread is currently running, for example after a restart of the J2EE-server. If more than one re-initialization thread is running, problems may occur.
Also in Administrator -> J2EE Cluster (Global) -> send soft shutdown -> with restart
If i do that, does will efect somewhere ? ..... Try it and let us see whether the problem resolves, I hope you are doing in the Dev Environment. Regarding the Option - 2 & 3 are not advicable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.