shell script for automating Start OAM,OID weblogic domain for SSO

#!/bin/bash

su oracle -c “screen -dm -S OIDInstance /u01/Oracle/Middleware/oid_instance/bin/opmnctl startall”
sleep 30
su oracle -c “screen -dm -S OHSInstance /u01/Oracle/Middleware/Oracle_WT1/instances/instance2/bin/opmnctl startall”
sleep 30

su oracle -c “screen -dm -S NodeManager /u01/Oracle/Middleware/wlserver_10.3/server/bin/startNodeManager.sh”

sleep 30

su oracle -c “screen -dm -S OIDAdminServer /u01/Oracle/Middleware/user_projects/domains/OIDDomain/bin/startWebLogic.sh”
sleep 30
su oracle -c “screen -dm -S ODSManagedServer /u01/Oracle/Middleware/user_projects/domains/OIDDomain/bin/startManagedWebLogic.sh wls_ods1”
sleep 30

su oracle -c “screen -dm -S OAMAdminServer /u01/Oracle/Middleware/user_projects/domains/OAMDomain/bin/startWebLogic.sh”
sleep 30
su oracle -c “screen -dm -S OAMAServer /u01/Oracle/Middleware/user_projects/domains/OAMDomain/bin/startManagedWebLogic.sh oam_server1”
sleep 30
su oracle -c “screen -dm -S EBSAccessGateAdminServer /u01/Oracle/Middleware/user_projects/domains/EBSAccessGate/bin/startWebLogic.sh”
sleep 30
su oracle -c “screen -dm -S EBSAccessGateManagedServer /u01/Oracle/Middleware/user_projects/domains/EBSAccessGate/bin/startManagedWebLogic.sh new_ManagedServer_1″

 

MYPATH_LOCATION=”/u01/Oracle/Middleware/user_projects/domains/”
/bin/echo “OS Server Restarted and start up script run at: $(date +’%Y-%m-%d %I:%M:%S %p’) ” >> $MYPATH_LOCATION/restartOSServer.log

oracle.security.jps.service.idstore.IdentityStoreException: JPS-01520: Cannot initialize identity store at starting OBIEE

set listen address for weblogic server

[bi_server1] [WARNING] [JPS-01520] [oracle.jps.idmgmt] [tid: [ACTIVE].ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’] [userId: <WLS Kernel>] [ecid: 0000KdVfAivApIWFLzNM8A1K^prs000002,0] [APP: bicomposer#11.1.1] Cannot initialize identity store, cause: javax.naming.CommunicationException: 2001:0:9d38:90d7:280c:3b5:3f57:ebcd:9704 [Root exception is java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine].
[2014-12-19T01:32:16.695+02:00] [bi_server1] [ERROR] [] [oracle.adf.mbean.share.connection.ConnectionsHelper] [tid: [ACTIVE].ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’] [userId: <WLS Kernel>] [ecid: 0000KdVfAivApIWFLzNM8A1K^prs000002,0] [APP: bicomposer#11.1.1] Failed to get credentials for alias ADF and connection name bi-default[[
java.lang.RuntimeException: java.security.PrivilegedActionException: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01520: Cannot initialize identity store, cause: oracle.security.idm.ConfigurationException: javax.naming.CommunicationException: 2001:0:9d38:90d7:280c:3b5:3f57:ebcd:9704 [Root exception is java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine].
at oracle.adf.share.security.providers.jps.JpsUtil.getDefaultIdentityStore(JpsUtil.java:386)
at oracle.adf.share.security.providers.jps.JpsUtil.getDefaultIdentityStore(JpsUtil.java:363)
at oracle.adf.share.security.providers.jps.JpsUtil.getUserUniqueIdentifier(JpsUtil.java:272)
at oracle.adf.share.security.providers.jps.JpsUtil.getUserUniqueIdentifier(JpsUtil.java:233)
at oracle.adf.share.security.providers.jps.CSFCredentialStore.getCurrentUserUniqueID(CSFCredentialStore.java:1245)
at oracle.adf.share.security.providers.jps.CSFCredentialStore.fetchCredential(CSFCredentialStore.java:481)
at oracle.adf.share.security.providers.jps.CSFCredentialStore.fetchCredential(CSFCredentialStore.java:645)
at oracle.adf.share.security.credentialstore.CredentialStore.fetchCredential(CredentialStore.java:187)
at oracle.adf.mbean.share.connection.ConnectionsHelper.getCredentials(ConnectionsHelper.java:208)
at oracle.adf.mbean.share.connection.ReferenceHelper.getCredentials(ReferenceHelper.java:325)
at oracle.adf.mbean.share.connection.ReferenceHelper.createReference(ReferenceHelper.java:290)
at oracle.adf.mbean.share.connection.ConnectionsRuntimeMXBeanImpl.registerBean(ConnectionsRuntimeMXBeanImpl.java:494)
at oracle.adf.mbean.share.connection.ConnectionsRuntimeMXBeanImpl.createConnection(ConnectionsRuntimeMXBeanImpl.java:572)
at oracle.adf.mbean.share.connection.ConnectionsRuntimeMXBeanImpl.configObjectReloaded(ConnectionsRuntimeMXBeanImpl.java:773)
at oracle.adf.mbean.share.connection.ConnectionsRuntimeMXBeanImpl.postRegister(ConnectionsRuntimeMXBeanImpl.java:1084)
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doPostRegister(OracleStandardEmitterMBean.java:551)
at oracle.adf.mbean.share.AdfMBeanInterceptor.internalPostRegister(AdfMBeanInterceptor.java:223)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doPostRegister(AbstractMBeanInterceptor.java:204)
at oracle.as.jmx.framework.generic.spi.interceptors.DefaultMBeanInterceptor.internalPostRegister(DefaultMBeanInterceptor.java:87)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doPostRegister(AbstractMBeanInterceptor.java:204)
at oracle.security.jps.ee.jmx.JpsJmxInterceptor$4.run(JpsJmxInterceptor.java:523)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.jmx.JpsJmxInterceptor.internalPostRegister(JpsJmxInterceptor.java:539)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doPostRegister(AbstractMBeanInterceptor.java:204)
at oracle.as.jmx.framework.generic.spi.interceptors.DefaultMBeanInterceptor.internalPostRegister(DefaultMBeanInterceptor.java:87)
at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMBeanInterceptor.internalPostRegister(ContextClassLoaderMBeanInterceptor.java:167)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doPostRegister(AbstractMBeanInterceptor.java:204)
at oracle.as.jmx.framework.generic.spi.interceptors.DefaultMBeanInterceptor.internalPostRegister(DefaultMBeanInterceptor.java:87)
at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doPostRegister(AbstractMBeanInterceptor.java:204)
at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.postRegister(OracleStandardEmitterMBean.java:516)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegisterInvoke(DefaultMBeanServerInterceptor.java:1035)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:974)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$27.run(WLSMBeanServerInterceptorBase.java:714)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.registerMBean(WLSMBeanServerInterceptorBase.java:709)
at weblogic.management.mbeanservers.internal.JMXContextInterceptor.registerMBean(JMXContextInterceptor.java:445)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$27.run(WLSMBeanServerInterceptorBase.java:712)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.registerMBean(WLSMBeanServerInterceptorBase.java:709)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.registerMBean(WLSMBeanServer.java:462)
at oracle.as.jmx.framework.wls.spi.security.PrivilegedMBeanServerInterceptor$1.run(PrivilegedMBeanServerInterceptor.java:55)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at oracle.as.jmx.framework.wls.spi.security.PrivilegedMBeanServerInterceptor.registerMBean(PrivilegedMBeanServerInterceptor.java:60)
at oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack.contextInitialized(ADFConnectionLifeCycleCallBack.java:111)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.security.PrivilegedActionException: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01520: Cannot initialize identity store, cause: oracle.security.idm.ConfigurationException: javax.naming.CommunicationException: 2001:0:9d38:90d7:280c:3b5:3f57:ebcd:9704 [Root exception is java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine].
at java.security.AccessController.doPrivileged(Native Method)
at oracle.adf.share.security.providers.jps.JpsUtil.getDefaultIdentityStore(JpsUtil.java:381)
… 85 more
Caused by: oracle.security.jps.service.idstore.IdentityStoreException: JPS-01520: Cannot initialize identity store, cause: oracle.security.idm.ConfigurationException: javax.naming.CommunicationException: 2001:0:9d38:90d7:280c:3b5:3f57:ebcd:9704 [Root exception is java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine].
at oracle.security.jps.internal.idstore.util.IdentityStoreUtil.getIdentityStoreFactory(IdentityStoreUtil.java:189)
at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmFactory(AbstractIdmIdentityStore.java:273)
at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.initStore(AbstractIdmIdentityStore.java:157)
at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.getIdmStore(AbstractIdmIdentityStore.java:132)
at oracle.adf.share.security.providers.jps.actions.IdmStoreAction.run(IdmStoreAction.java:46)
… 87 more
Caused by: oracle.security.idm.ConfigurationException: javax.naming.CommunicationException: 2001:0:9d38:90d7:280c:3b5:3f57:ebcd:9704 [Root exception is java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine]
at oracle.security.idm.providers.stdldap.TestConnectionPool.execute(LDIdentityStoreFactory.java:1026)
at oracle.security.idm.providers.stdldap.LDIdentityStoreFactory.setupConnPool(LDIdentityStoreFactory.java:620)
at oracle.security.idm.providers.stdldap.LDIdentityStoreFactory.setup(LDIdentityStoreFactory.java:333)
at oracle.security.idm.providers.ovd.OVDIdentityStoreFactory.<init>(OVDIdentityStoreFactory.java:59)
at oracle.security.idm.providers.wlsldap.WLSLDAPIdentityStoreFactory.<init>(WLSLDAPIdentityStoreFactory.java:45)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at oracle.security.idm.IdentityStoreFactoryBuilder.getIdentityStoreFactory(IdentityStoreFactoryBuilder.java:128)
at oracle.security.jps.internal.idstore.util.IdentityStoreUtil.getIdentityStoreFactory(IdentityStoreUtil.java:185)
… 91 more
Caused by: javax.naming.CommunicationException: 2001:0:9d38:90d7:280c:3b5:3f57:ebcd:9704 [Root exception is java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine]
at com.sun.jndi.ldap.Connection.<init>(Connection.java:209)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:116)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2678)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:296)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at oracle.security.idm.providers.stdldap.TestConnectionPool.run(LDIdentityStoreFactory.java:1006)
Caused by: java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.<init>(Socket.java:375)
at java.net.Socket.<init>(Socket.java:189)
at com.sun.jndi.ldap.Connection.createSocket(Connection.java:351)
at com.sun.jndi.ldap.Connection.<init>(Connection.java:186)
… 13 more

solution

update listen address for admin server and bi server by console and restart all (admin ,bi.bi coponents)

the Node Manager associated with machine local Machine is not reachable. ssl issue solved

the Node Manager associated with machine local Machine is not reachable

this is a generic error

at my case

nodemanger log file contain the following error
<Sep 17, 2014 6:33:32 AM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer localhost.localdomain – 127.0.0.1 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer localhost.localdomain – 127.0.0.1 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:154)
at java.io.BufferedReader.readLine(BufferedReader.java:317)
at java.io.BufferedReader.readLine(BufferedReader.java:382)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:745)

to solve this error we should disable hostname verfication set it to none unde ssl tab advanced at server configuration at weblogic gonsole

In Node Manager startup scrip (startNodeManager.sh), add this entry to JAVA_OPTIONS:
-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false

In Admin Server startup script (startWebLogic.sh), add this entry to JAVA_OPTIONS:
-Dweblogic.security.SSL.ignoreHostnameVerification=true

Restart both nodemanager and Admin server.

weblogic The DBMS driver exception was: IO Error: Socket read timed out solved

exception: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out

 

exception while creating connection for pool “soa-mds”: IO Error: Socket read timed out>

this was Linux DNS problem and it solved by removing /etc/resolv.conf file.

BEA-300033

<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:
      username=weblogic
      password=welcome1
    • Save
    • Restart the Weblogic Node Manager

How to deploy application to weblogic application server 10.3g

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.

  1. Check the box next to the Web application you want to deploy to Tomcat and hit the ‘Export’ button.
  2. In the File Download dialog that appears, click the Save button.
  3. In the ‘Save as type:’ section, choose All Files.
  4. 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)
  5. 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.
  6. In the Change Center section of the console, click the ‘Lock and Edit’ button to open the server instance for changes.
  7. In the Domain Structure section of the console, find the ‘Deployments’ link and click on it.
  8. You will see a Summary of Deployments. Here is where you will deploy the war file. Find and click the ‘Install’ button.
  9. 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’
  10. 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’.
  11. Click ‘Next’ again to accept the defaults in this next pane, then click ‘Finish’.
  12. 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.’
  13. 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.
  14. 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
  15. 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:

  1. In the Domain Structure section of the console, click ‘Deployments’.
  2. In the Summary of Deployments page, click on the name of the deployed Web application.
  3. 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.