on 09-22-2004 11:35 AM
Hi All,
I'm quiet new to SAP WAS.
I read in the documentation that JAVA IDE (SAP NETWEAVER DEVELOPER STUDIO) is added start on Release 6.30 (Please, correct me if I'am wrong).
If it so, how can I create J2EE application in Release 6.20. A brief explanation will be highly appreciated.
Thanks,
Edward (Indonesia).
Hi Kalle,
Thx, I have got the CD brom the Basis guy, and sucessfully installed it on my PC.
But when I try to execute Stand Alone Server, this error occured:
Loading core services:
Starting core service monitor ... done.
Starting core service p4 ... done.
Starting core service log ... done.
Starting core service dbms ... done.
Starting core service security ... done.
System Exception * Fail to start Naming. Exception is: java.security.AccessContr
olException: access denied (com.inqmy.lib.security.DomainsEnumerationPermission
ProtectionDomainEnumeration)
java.security.AccessControlException: access denied (com.inqmy.lib.security.Doma
insEnumerationPermission ProtectionDomainEnumeration)
at java.security.AccessControlContext.checkPermission(AccessControlConte
xt.java:269)
at java.security.AccessController.checkPermission(AccessController.java:
401)
at com.inqmy.core.policy.PolicyManager.getProtectionDomainStack(PolicyMa
nager.java:311)
at com.inqmy.core.service.context.container.security.DefaultProtectionDo
mainContext.getProtectionDomainStack(DefaultProtectionDomainContext.java:99)
at com.inqmy.services.security.domains.ProtectionDomainManagerImpl.getPr
otectionDomainStack(ProtectionDomainManagerImpl.java:96)
at com.inqmy.services.jndi.InitialContextFactoryImpl.getInitialContext(I
nitialContextFactoryImpl.java:72)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at com.inqmy.services.jndi.JNDIFrame.bindReferences(JNDIFrame.java:278)
at com.inqmy.services.jndi.JNDIFrame.start(JNDIFrame.java:176)
at com.inqmy.core.service.application.ApplicationServiceRunner.startFram
e(ApplicationServiceRunner.java:55)
at com.inqmy.core.service.container.ServiceRunner.run(ServiceRunner.java
:126)
at com.inqmy.core.thread.impl2.SingleThread.run(SingleThread.java:118)
Starting core service naming ... done.
Please Help.
Warm regard,
Edward.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Edward & others,
I have resolved the exception "AccessControlException" by unistalling JDK 1.4 and JRE 1.4.x on my client and installing 1.3.x version in place of 1.4 . Also set up variables: JAVA_HOME to the dir where 1.3.x jre was installed (C:\Program Files\JavaSoft\JRE\1.3.1_13) and also added the same to PATH (C:\Program Files\JavaSoft\JRE\1.3.1_13). Also added environment variable J2EE_HOME to the dir of my JDK (C:\j2sdkee1.3.1)
After this I had an issue with port 3011 being in use so I changed my sapj2ee config for p4 service to use port 3012.
sapj2ee now runs so I feel I am headed in the right direction . If anyone sees any better approaches and or any concerns regarding the approach taken by myself the please let me know.
Thanks,
Dan
Hi Dan,
It is better to use the JDK as JAVA_HOME and not the JRE normally put in Program Files for the browser plugin.
this is because the Engine by default tries to find the
javac compiler (for EJBs and JSPs) as %JAVA_HOME%\bin\javac which will not be found of course in
C:\Program Files\JavaSoft\JRE\1.3.1_13\bin.
Luckily the JDK installation is naughty enough to put a copy in C:\WinNT\system32 which is normally in the systempath so a javac will be found any way (in one of the other attempts of the Engine to invoke it) but this is for sure ambiguous.
The Engine requires JDK => it is better to configure it to use the JDK not the JRE.
Put C:\1.3.1_13 as JAVA_HOME (if you installed the JDK there).
Best Regards: Iavor
With the WAS installation bundle you get a client CD (it is a separate cd if I remember correctly) or you get it as well if you install the WAS locally.
So yes, you will install it locally and it will appear in Start --> Programs --> SAP J2EE engine 6.20 --> Tools
I'm sure you can also download it from service.sap.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Kalle & Achim,
Kalle, regarding your answer 'Just install the client part of the WAS 6.20 and you will get a tool called "deploy tool"', I have more questoins:
what is the client part of the WAS 6.20 should be installed so I can get the "deploy tool"?
Do I have to install it on my PC?
Once again, thanks in advance.
Edward.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Edward,
You don't need to do manual work to deploy J2EE applications (Servlets, JSPs or EJBs).
Just install the client part of the WAS 6.20 and you will get a tool called "deploy tool" that you can just add your classes to and it will pack them, generate any necessary server configuration definitions and finally after getting the connection parameters deploy the EAR for you.
Personally I think that the deploy tool is amongst the easiest J2EE deployment tools in the market!
Enjoy and come back if you get stuck on some details with the tool.
Cheers,
Kalle
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
iy you have j2ee-compliant applications, you should be able to create a .war-file (for web application) or a .ear-file (for en enterprise application) in a IDE of your choice.
you can deploy these files manually on your WAS6.20
kr, achim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
9 | |
9 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.