su oracle -c “screen -dm -S OIDInstance /u01/Oracle/Middleware/oid_instance/bin/opmnctl startall”
su oracle -c “screen -dm -S OHSInstance /u01/Oracle/Middleware/Oracle_WT1/instances/instance2/bin/opmnctl startall”
su oracle -c “screen -dm -S NodeManager /u01/Oracle/Middleware/wlserver_10.3/server/bin/startNodeManager.sh”
su oracle -c “screen -dm -S OIDAdminServer /u01/Oracle/Middleware/user_projects/domains/OIDDomain/bin/startWebLogic.sh”
su oracle -c “screen -dm -S ODSManagedServer /u01/Oracle/Middleware/user_projects/domains/OIDDomain/bin/startManagedWebLogic.sh wls_ods1”
su oracle -c “screen -dm -S OAMAdminServer /u01/Oracle/Middleware/user_projects/domains/OAMDomain/bin/startWebLogic.sh”
su oracle -c “screen -dm -S OAMAServer /u01/Oracle/Middleware/user_projects/domains/OAMDomain/bin/startManagedWebLogic.sh oam_server1”
su oracle -c “screen -dm -S EBSAccessGateAdminServer /u01/Oracle/Middleware/user_projects/domains/EBSAccessGate/bin/startWebLogic.sh”
su oracle -c “screen -dm -S EBSAccessGateManagedServer /u01/Oracle/Middleware/user_projects/domains/EBSAccessGate/bin/startManagedWebLogic.sh new_ManagedServer_1″
/bin/echo “OS Server Restarted and start up script run at: $(date +’%Y-%m-%d %I:%M:%S %p’) ” >> $MYPATH_LOCATION/restartOSServer.log
<NodeManager> <BEA-300033> <Could not execute command “getVersion” on the node manager. Reason: “Access to domain ‘myDomain’ for user ‘R040FFV7GI’ denied”.>
the credentials were generated during the domain creation and can be found in the Weblogic console at <domain> -> Security -> General -> Advanced -> Nodemanager Username
Instead of the default Weblogic generated Nodemanager credentials we wanted to try to configure a fixed name/password in the Weblogic domain and on each host.
In Weblogic console:
- Click on domainname in Domain Structure (left menu)
- Select Security -> General -> Advanced
- Configure the NodeManager Username with weblogic
- Configure the NodeManager Password with welcome1 (2x)
On each remote host:
- Navigate to the folder %DOMAINHOME%\config\nodemanager
- Edit the file: nm_password.properties
- Content should be set to:
- Restart the Weblogic Node Manager
Deploying the application to Weblogic Application Server
The deployment procedures below are for using Weblogic 9.1. The procedures for using different versions may vary.
In Manager, locate the existing Web application on the Applications page.
- Check the box next to the Web application you want to deploy to Tomcat and hit the ‘Export’ button.
- In the File Download dialog that appears, click the Save button.
- In the ‘Save as type:’ section, choose All Files.
- The default file name extension will be .zip. Change this to .war and save it to the file system. Click the ‘Close’ button when Save is complete.(For example: C:\temp\myapp.war)
- Start Weblogic Server. a browser will open to http://localhost:7001/index.jsp. Click the ‘Start the Administration Console’ button to open the Administration Console.
- In the Change Center section of the console, click the ‘Lock and Edit’ button to open the server instance for changes.
- In the Domain Structure section of the console, find the ‘Deployments’ link and click on it.
- You will see a Summary of Deployments. Here is where you will deploy the war file. Find and click the ‘Install’ button.
- Browse to the location on your file system where the .war file was saved. Click the radio button next to the .war file and click ‘Next’
- You want to deploy this module as an application. For the targeting style, make sure ‘Install this deployment as an application’ is selected. Click ‘Next’.
- Click ‘Next’ again to accept the defaults in this next pane, then click ‘Finish’.
- You will now get a summary list of the settings for the deployment. Click the ‘Save’ button. If everything went ok, you will see a message in green that says ‘Settings updated successfully.’
- Back in the Change Center section of the console, click the green ‘Activate Changes’ button. The application has been ‘prepared’, but not yet deployed at this point.
- Back in the Domain Structure section of the concole, find and click on the ‘Deployments’ link. In the Summary of Deployments, find your application, check the box next to it and click the ‘Start’ button. Select ‘Servicing all requests’. Click Yes to continue
- If the state of your deployment says ‘Active’, you have successfully deployed your Web application to Weblogic.
Testing your deployment from within the Weblogic Administration Console
You can test your application from within the Administrative Console by following the steps below:
- In the Domain Structure section of the console, click ‘Deployments’.
- In the Summary of Deployments page, click on the name of the deployed Web application.
- Select the ‘Test’ tab. Here, you’ll find the URL to the deployed Web application. Click the link to launch it in a separate browser window.
Download the WebLogic Server installation files from OTN or E-Delivery.
Make sure the JAVA_HOME refers to the proper Java installation:
$ JAVA_HOME=/oracle/jrockit-jdk1.6.0_24 export JAVA_HOME
$ PATH=$JAVA_HOME/bin:$PATH; export PATH
Check that the proper Java version will be used:
$ java -version
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1432-linux-x86_64, compiled mode)
If you are installing WebLogic Server on a 64-bit platform using a .jar installation program use the downloaded wlsversionnumber_generic.jar . Start the installation using the following command. Include the -d64 flag in the installation command when using a 32/64-bit hybrid JDK.
$ java -d64 -jar wls1035_generic.jar