Now run the project (click F9 or click Run Project icon then login). WebLogic Server 7.x is designed to start within JBuilder and permit you to see the running login.jsp in the
AppBrowser. See Figure 17 for details.
Figure 17: JBuilder running Struts application using WebLogic Server 7.x
Enter the user name as suds and password as borland. It is designed to show you the Login Successful message. Try entering some other information, and it should bring the normal login.jsp screen again for re-entry of user name and password.
Conclusion
JBuilder is a highly productive environment, and users can increase their productivity and reduce the project lifecycle by using JBuilder as a Java development platform. This paper is focused only on JSPs, servlets, and Struts applications. JBuilder has many other features which are designed to make the Web development a smooth experience for the developers. If you have JBuilder installed, try the tutorials available in JBuilder Help. Also refer to other white papers available on the Borland Web site for EJB and Web Services development.
Troubleshooting
Error 1: WebLogic Server cannot start: config.xml not found
Error description
<Info> <Management> <140013> <E:\bea\user_projects\.\config.xml not found>
E:\bea\user_projects\.\config.xml not found
Since no config.xml was found, the fileRealm.properties file will not be used.
Would you like the server to create a default configuration and boot?
(y/n):
When did this happen
I tried to run WebLogic Server from JBuilder and got this error from WebLogic 7.x http:7001 tab.
Cause
The Domain Directory provided in JBuilder Server Configuration may not be correct.
Solution
From the JBuilder menu bar, click Tools -> Configure Servers. Click WebLogic
Application Server 7.x from the left-hand pane, and click Custom tab from the right. Check the Domain Directory. An example of Domain Directory is E:\bea\user_projects\mydomain.
Error 2: Authentication for user <username> denied
Error description
<Critical> <WebLogicServer> <000364> <Server failed during
initialization. Exception:java.lang.SecurityException: Authentication for user username denied
When did this happen
I tried to start WebLogic Server 7.x within JBuilder and got this error from WebLogic Server 7.x http:7001 tab.
Cause
The username or password provided in JBuilder to configure with WebLogic Server may not be correct.
Solution
From the JBuilder menu bar, click Tools -> Configure Servers. Click WebLogic Application Server 7.x from the left, and click Custom tab from the right. Re-enter the correct user ID and password.
Error 3: Help viewer error on server in AppBrowser
Error Description
Help viewer error on server
Unable to open location: Document not found on server.
When did this happen:
I tried to run a JSP/servlet from JBuilder, and the AppBrowser shows this error.
Cause
The error confirms that the WebLogic Server is running properly, but the document JSP/servlet that you are trying to access is not found in the WebLogic server.
Solution
Redeploy the Web application and try to run the JSP/servlet again.
Error 4: Deployment of Web application failed
Error description ar on myserver because there is already a webapp named
ServletContext(id=5684736,name=TestWebApp,context-path=/TestWebApp) loaded from E:\Documents and
Settings\spati\jbproject\TestWebApp\TestWebApp, which is using the context path /TestWebApp.
When did this happen
I tried to deploy my Web archive from JBuilder to WebLogic by right-clicking the WAR file—> Deploy Options -> Deploy.
Cause
Seems like you have already deployed a Web application with the same name to WebLogic Server.
Solution
By default, JBuilder maps the project Web applications to WebLogic at runtime. This is called auto-deployment or exploded format deployment. Auto-deployment does not require any WAR or EAR files. WebLogic knows where to find the updated JSPs, servlets, and Java files.
But if you rather use the hot deployment (deploying archives), turn off the exploded format deployment. Click Project -> Project Properties. Click the Server tab. Click the
JSP/servlet service in the services list. On the right, de-select the option Map project webapps at runtime. Now you can deploy your WAR/EAR without any deployment conflicts.
Error 5: Unable to load performance pack
Error description
<Error> <socket> <000433> <Unable to load performance pack, using Java I/O instead.
Please ensure that wlntio.dll is in:
'E:E:/bea/weblogic700/server/bin'
java.lang.UnsatisfiedLinkError: no wlntio in java.library.path
When did this happen
This happened when I started WebLogic Server 7.0 within JBuilder 8. The error appeared within WebLogic Server 7.0 http:7001 tab, and the server didn’t start.
Cause
This error occurred because the VM parameters of Configure Servers are not correct.
WebLogic is unable to find the wlntio.dll because the path information for E:/bea/weblogic700/server/bin is not correct.
Solution
Click Tools -> Configure Servers ->. Click WebLogic Application Server 7.x from the left-hand pane and click VM Parameters from the right-hand pane. Make sure that -Djava.library.path has correct path information.
Warning 1: Deprecation warnings
Warning description
"TestJSP.jsp": Warning #: 368 : method putValue(java.lang.String, java.lang.Object) in interface javax.servlet.http.HttpSession has been deprecated at line 8
Warning #: 369: There have been deprecation warnings. Please consult the documentation for a better alternative
When did this happen
Whenever I compile/build my project, I get a separate build tab in the JBuilder message pane, and these warning messages show there. Also, this happens when I start my WebLogic Server within JBuilder and deploy my archives to WebLogic.
Cause
Some of the methods created by JBuilder Wizard are deprecated.
Solution:
From JBuilder main menu bar click Project | Project Properties |Build tab and uncheck Show Warnings and Show deprecations.
Warning 2: Servlet failed with ServletException
Warning description <Error> <HTTP> <101018>
<[ServletContext(id=6655097,name=TestWebApp,context-path=/TestWebApp)] Servlet failed with ServletException
javax.servlet.UnavailableException:
ServletContext(id=6655097,name=TestWebApp,context-path=/TestWebApp):
The server myserver is temporarily suspended at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
I have started WebLogic 7.x successfully within JBuilder. When I click Run Project ->
TestJSP from JBuilder toolbar, WebLogic Server starts within JBuilder but shows this error in the message.
Cause
Sometimes the JSP is activated before the initialization of WebLogic Server which causes this error.
Solution:
This is a harmless warning message and doesn’t effect anything. If you would rather not see this warning message, then open the WebLogic Console ( Tools -> WebLogic 7.x Admin Console), expand Servers > click myserver > from the righthand window, click Logging
-> change the Stdout severity threshold from Error to Notice. Click Apply.