So I have a couple MQs set up in WASv8.5. I have tested these and they work fine, now I need to test some functionality. In order to do this I downloaded the "New" MQJExplorer and I noticed the ability to load JNDI from a context. Now since the Websphere instance is running locally can I just hook directly into the Websphere Context? I tried selecting Websphere Application Server and it gives me an address box starting with
iiop://
I tried using...
iiop://localhost
but that didn't work and neither did
iiop://localhost:9064
I tried looking about iiop and I couldn't really find how to enable it on WebSphere. How can I make this work?
Make sure the port is Bootstrap Port and also you may try adding providerURL under WAS console: Environment > Naming > Name Space Binding.
Related
I don't see any issues when I run the server and client on the local worksapce(via eclipse). However there are issues if the client is executed from a different machine than on server or executed from exported client product(i.e. Eclipse rcp).
I also read article on JNDI and various online blogs. Please let me know if I am missing anything obvious. Trying to get the remote client working for couple of days now. :(
Object returnValue = context.lookup("ejb:GeoEE/GeoEJB/UserRegistrationService!com.geo.request.ejb.IUserRegistrationService");
above line returns Object in local environment and null in case of remote or exported client.
Replace "ejb:" to "/"
If not set, use this properties to init context(replace server and port):
java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
java.naming.provider.url=http-remoting://127.0.0.1:8080
jboss.naming.client.ejb.context=true
I'm having issues getting the status of an Application on a specific Application Server inside of IBM's WebSphere product. I can get into the wsadmin scripting console, and issue:
print AdminApp.list("WebSphere:cell=MYCELL,node=NODE01,server=WPS00")
and get a list of applications installed on the AppServer itself, however, when I issue the command:
print AdminApp.isAppReady("Application01")
its obviously looking through the whole cell. Then I attempted to use:
print AdminControl.completeObjectName("WebSphere:type=Application,name=Application01,*")
it won't return anything because its in partial start. So I tested this against an application that was already fully running, and it showed all of my mBeans that it corresponded to. Specifying a server in the completeObjectName option doesn't work even with the fully running application.
How do I reliably get the status of an application on a specific application server so I can restart just what needs to be restarted and not the application across the whole AppTarget?
AdminControl.queryNames("WebSphere:type=Application,name=yourappname,*")
will return one mbean for each instance of the app that is running.
Each mbean's object name will include the node and server name.
To query an app's status on a specific server, add the Nodename and servername to the above queryNames call. Getting an mbean back means it's running, getting nothing back means it's not.
Try this:
AdminControl.queryNames("type=Application,name=Application01,cell=MYCELL,node=NODE01,server=WPS00,*")
Put the '*' to get you all the attributes defined for the mbean and remove WebSphere from the string.
We are facing server hang issue at start up if one of Database not available. I have looked into weblogic documentation and find we can overcome this issue by setting up 'JDBCLoginTimeoutSeconds' property on ServerMBean.
I have googled it and mostly found ways to configure thru code or xml configuration. We don't want to make any code change and do not have direct access to server xml configuration. So just wanted to know if there is a way to setup this property thru Admin Console.
Using the WebLogic console, open the datasource configuration. Then on the Connection Pool tab, set the Initial Capacity to 0. This will prevent WebLogic from doing an initial check on the database during startup. The server will start properly even if the database is not available.
Can we create multiple servers in the websphere application server profile
Usually the default is server1 gets created , when you create the stand alone instance.
Yes, you can via wsadmin scripting, check details here:
Creating a server using scripting
however by default to configure and install app on that server you will need to use console installed on server1 or scripting, so it is a bit troublesome. That server will also share some configuration settings with server1 e.g. security settings.
If you want more isolation it is usually easier to just create another Application Server profile, from the same WebSphere installation (using Profile Management Tool, or manageprofiles script).
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.