i installed a standalone WebSphere portal server, how can I change the class loading policy of the portal server ?
When i log into admin console, i don't have the option to change it.it is blacked out.
Do i have you use jacl scriopts ? Can i
Thanks,
K
As far as I remember, WebSphere Portal consist of some applications and services deployed on WAS. Did you tried to change classloader policy of wps.ear? Maybe you have more specific problem? jacl do the same actions as in admin console
You can access Websphere_Portal profile from WAS console and change it.
Select the server Server Types>WebSphere application servers>WebSphere_Portal there you can see the Server-specific Application Settings > Classloader policy When you select Single the Class loading mode will be enabled.
Related
I can not access the web interfaces of obiee. Any suggestions or solutions?
"www".localhost:7001 should just be localhost:7001.
Also, OBIEE runs on the /analytics deoloyment. /console is the WebLogic administration console.
You must use the correct URL:
Use this URL:
http://localhost:7001/analytics
instead of:
http://www.localhost.com:7001/console
Please check whether your URL is apt or not.
Because what I think it should be localhost:7001/em or localhost:7001/console which is Enterprise Manager and Weblogic Console respectively.
And for OBIEE web page, we use analytics that is nothing but localhost:9704/analytics or localhost:9502/analytics
Solely depends on your OBIEE configuration.
Hope it would be helpful.
Based on your screenshot it appears as if you are attempting to access weblogic console. I would make sure that node manager and Admin Server are both started and running. On Windows os, click on the start menu and type NodeManager/Start Weblogic and it will give you the shortcut icons.
Once those two have been started you should be able to login to weblogic console and to ensure that admin/managed servers are both running.
If you did an enterprise installation of OBIEE11g, the default port for analytics should be 9704 unless you manually configured to use a different port number.
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.
I have created a simple MVC3 site that displays data from a table in an Azure database. I have created a cloud service to run the site in and can publish it successfully. I have also run the site successfully in the Azure emulator.
My problem is that when I select the page that displays the data there is an error as I get the default error page. I think I have the db connections set correctly but I cannot see any logs. So my questions are:
Where are the IIS logs? I would like to see what the error is.
Are there any other logs/diagnostics that I can use to see what the problem is?
Thanks.
By default the only place where something might be logged is in the Windows Application Event Log. You'll need to Remote Desktop to the cloud service instance (Connect from the Instances page in the Azure Management Portal) and then open Event Viewer.
The IIS logs themselves should be available too although as per normal IIS logs these won't contain exception details. Use IIS Manager > Application > Logging when logged on to the instance to find the location.
As suggested by Magnus, you should use something like Windows Azure Diagnostics and/or ELMAH and/or log4net to log exception and diagnostic information to somewhere accessible for troubleshooting.
I suggest you use Windows Azure Diagnostics to collect your logs.
You can read all(setup and usage) about it here:
http://msdn.microsoft.com/en-us/library/windowsazure/gg433048.aspx
What are the business reasons (advantages/disadvantages) of running a websphere 6.1 App server as a windows service? I mean what are the factors governing this decision?
The other thing I notice is that when I restart the service...and I click something on the admin console, it does n't give me the login page. What is happening here?
You should give this article a read:
http://www.ibm.com/developerworks/websphere/techjournal/1010_supauth/1010_supauth.html
Can you elaborate on the restarting the service and not receiving the login page issue. I am not sure i understand your query here.
What happens when you click on the console after restarting?
HTH
Manglu
To my knowledge - the main reason for choosing to run WebSphere as a Windows Service is that whenever the server goes down for whatever reason, and then is restarted, if not running WebSphere as a service you will need to actually log on to the server and manually start WebSphere. (startServer.bat, startManager.bat, startNode.bat etc).
So for any environment where uptime is an issue on the Windows platform, choose windows service. If you are just installing a development/test environment...not needed.
I am new to WebSphere application server. I need to make minor changes on the server.
I don't know how to launch the Admin console.
Assuming that the default ports are used you can access the console from http://localhost:9060/ibm/console