TS 71 WebLogic

WebLogic Test Specification

Author: Radim Roska, Jiri Skrivanek
Version: NetBeans 7.1
Last update: 22-th September 2011
Introduction: This test specification is focused on testing NetBeans support for WebLogic application server.
Comments: NetBeans supports WebLogic version 10. You must run NetBeans on JDK higher than 1.4 when testing WebLogic.

Contents


Test suite: Register WebLogic

Purpose: To verify a WebLogic server instance can be easily added/removed and used within the IDE.
Setup: Install WebLogic server (see AppServersInstallation).

  1. Register WebLogic
    1. In Services view perform Add Server action on Servers node
    2. In the opened dialog choose server Oracle WebLogic Server and click Next
    3. Till you specify server location there's hint message "Please enter installation directory of Oracle WebLogic Server".
    4. Specify correct location, where WebLogic is installed. Click Next.
    5. Default domain should be selected in the combo box.
    6. Type in default password "welcome1" for default user name "weblogic"
    7. Click Enable JPA and check it is successfully enabled. In Classes tab should be correct jar and also in project libraries.
    8. Click Disable JPA and check it is successfully disabled.
    9. Click Finish button.
    10. Right-click WebLogic node in Services view and click Remove item.
    • EXPECTED RESULT: All operations works fine. When WebLogic is registered to the IDE, its node appears as sub node of Servers node in Services View. After Remove action WebLogic node disappears from Services View.
  2. Server manager
    1. Open main menu item "Tools|Servers".
    2. In opened dialog try to add and remove WebLogic server.
    • EXPECTED RESULT: Works as in the first case.


Test suite: Managing WebLogic

Purpose: To verify a WebLogic can be controlled from IDE.

  1. WebLogic server instance
    1. Add WebLogic server node.
    2. Perform Start action on WebLogic server node.
    3. Check Output window, there should be server log displayed. And a welcome page should be opened in browser. If start fails in VirtualBox with message "Reply from SOCKS server has bad version", try to 'unset GNOME_DESKTOP_SESSION_ID' and set no proxy in IDE.
    4. Check server node icon in services view has changed.
    5. Perform Refresh action on WebLogic node.
    6. Perform Restart action on server node.
    7. Perform Stop action.
    8. Verify it has really stopped by opening server URL in browser. (e.g. http://localhost:7001 - port may be different)
    9. Perform Start in Debug Mode.
    10. Perform Start in Profile Mode.
    11. Close output window. And perform View server log operation.
    12. Perform View admin console action.
    13. Perform Properties action.
    14. Stop server.
    15. Most of these actions can be performed from output window as well. Verify whether it works.
    • EXPECTED RESULT:
      • Following options should be available after right click on server node: Start, Start in Debug mode, Restart, Stop, Refresh, Remove, View Admin Console, View Server Log, Properties
      • Server responds to the operations correctly. Icon in Services view is changing with server status. Appropriate string (e.g. "Starting WebLogic Server") appears in the status bar when operation is performed. Server log is displayed when it should be. Performing View admin console actions runs browser with web configuration tool and so does view JMX console.


Test suite: Deployment

Purpose: To verify a web project can be deployed to server using IDE.

  1. Deploying Web Application
    1. Create Web Application. Be sure to select WebLogic in New Web Application wizard.
    2. Run new application while server is down. Server has to start automatically.
    3. Application welcome page should be displayed in new tab of your browser.
    4. Change "Hello World!" in index.jsp and call Deploy operation. Refresh your browser when its done.
    5. Go to Services view and expand all children under WebLogic server node.
    6. Right-click deployed web application and choose Stop.
    7. When it is stopped choose Start.
    8. Right-click deployed web application and choose Open in Browser (bug 220153).
    9. Right-click deployed web application and choose Undeploy.
    10. Perform Debug operation on Web Application.
    11. Again index.jsp should be displayed in your browser.
    12. Check deployment descriptor - weblogic.xml in Configuration Files.
    • EXPECTED RESULT: All operations run successfully. After deploying changed application result in browser has to be changed too.
  2. Deploying Enterprise Application
    1. Create Enterprise Application project. Again be sure to select WebLogic. Create some Session Bean in EJB Module.
    2. Perform all steps in test case "Deploying Web Application" this time with Enterprise application.
    • EXPECTED RESULT: All operations run successfully.
  3. Data Source Creation
    1. Start New Persistence Unit wizard for previously created web application.
    2. In Data Source combo box select New Data Source.
    3. Select default database connection and provide arbitrary JNDI name.
    4. Click OK and finish the wizard.
    5. Check Server Resource|datasource-1-jdbc.xml file is created in web project.
    6. Go to Services view and refresh "Resources|JDBC|JDBC Resources" node under WebLogic server node
    7. Check newly created data source appears under this node.
    • EXPECTED RESULT: All operations run successfully.
  4. Message-Driven Bean
    1. Follow wiki page Using WebLogic JMS from NetBeans.
    • EXPECTED RESULT: All operations run successfully.
  5. OWSM Support (see NewAndNoteworthyNB71#Web_Services)
    1. Open new file wizard
    2. Choose "Web Services|Web Service"
    3. Finish the wizard
    4. Right-click NewWebService node and choose "Edit Web Service Attributes".
    5. There is "OWSM Policies" tab if server supports it. The policies are located in the oracle_common/modules/oracle.wsm.policies_11.1.1/wsm-seed-policies.jar file inside its middleware directory. It is true for JDeveloper bundled WL server. It could be not true if you use standalone WL server distribution.
    6. Change policies and click OK
    7. Check WS java class contains java annotation with name(s) of policies
    8. Create new web service client
    9. Create new servlet
    10. Right-click in editor and choose "Insert Code...|Call Web Service Operation"
    11. Select operation and click OK
    12. Check OWSM related code is generated.
    • EXPECTED RESULT: All operations run successfully.


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo