Redeploy the Java EE ODI Agent in WebLogic

1. In WLS Console, navigate to Deployments and select oraclediagent from the list. Click on the Delete button at the top of the table to delete the deployment of the oraclediagent enterprise application. Click on Activate Changes.
2. Still on the Summary of Deployments page, click on Lock and Edit and then click on the Install button.
3. On the Application Install Assistant, provide the path to the oraclediagent.ear file. This path should be <ODI Home>/setup/manual/oracledi-agent. Select oraclediagent.ear using the radio button displayed:

4. Click Next. Accept the default selections on the screen:

 

5. Click Next. Select the ODI Managed Server as the deployment target:

6. Click Next. Accept the defaults on the Option settings page:

7. Click Next. Review the choices and then click Finish.

8. Click on Activate Changes.
9. On the Summary of Deployments page, select the oraclediagent enterprise application and then click on the Start button: Servicing All Requests. (Click Lock & Edit, if necessary). 

The oraclediagent should successfully start.

Error while starting OBIEE servers- [Security:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied

Error: While starting obiee servers i got below error

Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied

<Nov 2, 2011 3:22:38 AM CDT> <Critical> <Security> <BEA-090403> <Authentication for user  denied>

<Nov 2, 2011 3:22:38 AM CDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user  denied

weblogic.security.SecurityInitializationException: Authentication for user  denied

        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)

        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)

        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)

        at weblogic.security.SecurityService.start(SecurityService.java:141)

        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

        Truncated. see log file for complete stacktrace

 

Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User  javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied

        at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:250)

        at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)

        at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        Truncated. see log file for complete stacktrace

Cause: This error is because of the corrupt or missing boot.properties. 

Solution:

a. Open boot.properties file (location would be <bea_home>/user_projects/domains/<domain>/servers/<admin server name>/security)

b. Add the following in the boot.properties

username=<weblogic admin user name>

password=<weblogic admin password>

c. Restart the server.

Node Manager associated with machine MACHINE_NAME is not reachable.

Issue: The managed WebLogic servers are unable to be started up using the Node Manager inside the WebLogic Administration Console.

 Error: For server MANAGED_SERVER_NAME, the Node Manager associated with machine MACHINE_NAME is not reachable.

Solution:

1. Make sure all managed WebLogic servers are shut down.

2. Shut down the AdminServer.

3. Stop the Node Manager. In Windows, this can be done by stopping the Windows service (if installed) or closing out of the Command Prompt window running startNodeManager.cmd.

4. In the file system, delete the following files for each managed server:

a)      %DOMAIN_HOME%servers%MANAGED_SERVER_NAME%datanodemanager%MANAGED_SERVER_NAME%.state

b)      %DOMAIN_HOME%servers%MANAGED_SERVER_NAME%datanodemanager%MANAGED_SERVER_NAME%.lck

c)       %DOMAIN_HOME%servers%MANAGED_SERVER_NAME%datanodemanager%MANAGED_SERVER_NAME%.pid

5. Start up the Node Manager.

6. Start the Admin Server using either a startup script or WLST.

 After applying the steps above, you should be able to start the managed servers from the Admin Console.