I enabled the 'admin port' in the WebLogic Admin Console and now can't get back into the console to change it since I can't start the server.
When I try to start the server, I get this message in Eclipse:
[Stopped, User'principals=[weblogic, Administrators]' has administration role. All tasks by administrator administrators must go through an Administration Port.
When trying to access the console via browser, I get this message:
Console/Management requests or requests with specified to 'true' can >only be made through an administration channel.
This previous solution to this problem suggested modifying the <administration-port-enabled> element in the DOMAIN-HOME\config directory, but this element does not exist in my config.xml. Should I add it?
I have tried creating a new workspace and a new domain, but the problem persists.
Is there another way to disable the 'admin port' without using the WebLogic Admin Console or editing the config.xml file?
MW_HOME/oracle_common/common/bin
./wlst.sh
connect()
And Navigate to AdminServer and find the required Mbean
If not possible to connect, try with Offline Mode.
Related
I have an error when i try to start the Oracle BI server on Oracle VM VirtualBox. I am currently using SampleAppv607p-appliance.
This is my error.
/Servers/AdminServer/ListenPort=7001
Accessing admin server using URL t3://demo.us.oracle.com:7001
Starting AdminServer …
Admin Server Start Exception: Error occurred while performing nmStart : Error Starting server AdminServer : Received error message from Node Manager Server: [Server start command for WebLogic server ‘AdminServer’ failed due to: [Server failed to start up but Node Manager was not aware of the reason]. Please check Node Manager log and/or server ‘AdminServer’ log for detailed information.]. Please check Node Manager log for details.
Use dumpStack() to view the full stacktrace :
Reading domain…
/Servers/AdminServer/ListenPort=7001
Accessing admin server using URL t3://demo.us.oracle.com:7001
Requesting credentials …
Enter Weblogic login details at prompt
Please do help me. Thank you!
I'm guessing here, your database is probably not up. So confirm the Oracle DB in VM is up and start BI services.
Based on your logs it looks like you're starting the WebLogic Admin Server via the Node Manager. However, during startup of the Admin Server it prompts for the username/password of domain user (e.g. weblogic) but Node Manager is not passing anything.
To solve this, go to $DOMAIN_HOME/servers/AdminServer/security and create boot.properties file. Edit the file and enter the username and password on separate lines. The username/password was defined upon domain creation, so make sure you know what these values are. See example below:
username=weblogic
password=welcome123
Start the Admin Server again. This will automatically encrypt the contents of your boot.properties file.
It always helps if you check the logs, as they provide more information on the error. In this case, you can check the following logs at the $DOMAIN_HOME/servers/AdminServer/logs/ directory.
I'm looking to setup a Queue Manager Using WebSphere MQ V7 MQ Explorer.
After Creating my Queue Manager, normally I expect that some sub directories are automatically generated under it, "Queues", "Topics", "Channels" .. as illustrated in the photo below.
In my case, no sub directories are generated, as illustrated below in the second snapshot.
PS: the status of my Queue manager is : Running but disconnected from WebSphere MQ Explorer.
When I right-click on the QMgr Name and choose Connect, I get "An unexpected error (2063) has occurred (AMQ4999)"
Could you advise please about a possible cause of this behavior ?
Administrative tools -> Local Security Policy -> Local Policies -> User Rights Assignment -> Log on as a service -> Properties -> add your user here
Same problem with MQ v9 and i solved it this way.
Go to control panel – Administrative tools
Control Panel\All Control Panel Items\Administrative Tools
Local
Inside Local Security Policy
Enter your domain user name then click check names – finalize by clicking ok. Then apply.
Now the domain user can log on as a service – Now open the services running on your machine.
Double click on the MQ service – then go on log on tab
Then apply click okay button – from the restart your machine for the changes to take effect
Finally open WebSphere MQ Explorer as admin - queue manager should be able to connect
Same issue with MQ 9.0 installed on Windows 10 EE.
(Run as Administrator) secpol.msc /s
(open) Local Policies > User Rights Assignment > Log on as a service
then add your User. Same user should be used for "IBM MQ (Installation1)" (Properties> Log On), installation default (when you do not setup the Domain Policy during installation) is MUSR_MQADMIN.
(Maybe you can try to run "MQ Explorer" as MUSR_MQADMIN user, but it's password is automatically generated during the installation. It's possible to change it, but it doesn't seem to be a safer against the using local account to run the MQ service)
I have IBM RAD / WebSphere 7 installed locally. My web application I'm developing runs fine.
I'm trying to log into the WAS admin console.
In the "Servers" view, I right-click the server > Administration > Run Administration Console ... but I get a "webpage cannot be found" error page.
In Firefox, I attempt to browse to the admin console URL, I tried each of the following but no luck:
http://localhost:9091/ibm/console/logon.jsp
http://localhost:9091/ibm/console/
http://localhost:9060/ibm/console/
http://localhost:9060/admin
Any ideas what the URL is?
Or, alternately, if the admin console is not starting due to some error, is there a log file somewhere where I can find the error?
Any help is greatly appreciated!
Rob
The third of those would normally be the correct one, but the port number depends on what happened during the profile creation process. Find the profile directory and then look in the properties directory for the portdefs.props file. That will tell you what the correct port number should be.
It is possible to create a profile without the admin console application, in which case it will obviously never work. You could also try running wsadmin from the profile bin directory to see whether you can connect to the admin service that way.
Any errors from the admin console application will be reported in the normal log files in the profiles/profilename/logs/servername directory.
Hello I just enabled Legacy mode authorization in Jenkins and it seems that it has now locked me out of all the administrative privileges.
I need to create an admin account so that I can continue with Jenkins configuration. I have direct access to the server and have tried running this line from command line:
java -jar jenkins.war --argumentsRealm.passwd.jenkins=swordfish --argumentsRealm.roles.jenkins=admin Jenkins starts but I am unable to access it from the web when starting from command line.
I've also tried starting Jenkins through services.msc, which is how I typically start it, and passing it the parameters --argumentsRealm.passwd.jenkins=swordfish --argumentsRealm.roles.jenkins=admin. Jenkins starts and I am able to access it through the web, but unable to log in with the username.
Any ideas how get admin access back?
I deleted the entries related to security and authentication in the config.xml, restarted, and I am able to access again. I was able to add myself as an admin using matrix based security. Still not sure how to do it with legacy tho.
Recently, I had the same problem. I would try to login to jenkins (hosted on glassfish), and would encounter the same thing. Basically getting a glassfish error that the application was not available. If I cleared all temporary internet files from browser, browse to jenkins home page, I would be presented with the Jenkins login, and when I provided the correct userID and password, WHAMMO! Back to application not available.... This too was using matrix-based administration.
To fix:
Locate the config.xml of the userID that is experiencing problems, under "users" directory.
Deleted the "apiToken" tag under "jenkins.security.ApiTokenProperty" tag.
Bounced glassfish and was able to login again.
I am using Weblogic Server em console to restart a webserver, URL looks like this:
http://localhost:7001/em/
AdminServer is named 'AdminServer', I wish to restart this server instance,
I click on server in EM console then user menu option like this:
(Weblogic server>Control>Shut Down...) I get this error:
'No Machine associated with server AdminServer. Please associate a machine to this weblogic server using weblogic console first.'
Not able to understand what this means....
What am i missing here?
With Oracle WebLogic, a Machine represents... well, a physical machine (and you can associate Servers i.e. WebLogic instances to it). This is not a fundamental concept except when using Node Managers. In general, you create Machine(s), Server(s) and their association with the configuration wizard at domain creation time.
It is however possible to add a Machine from the console (Environment > Machines > New):
But you can't add a RUNNING Server to a Machine with the console, which will be a problem for the admin Server. So, I'd recommend to use the configuration wizard to extend your existing domain and add Machine(s).
Note that all this will only solve the "shutdown problem", restarting will involve Node Manager which is very likely not configured.