im running multiple servers on weblogic domain.
Is it possible to run different ojdbc drivers on servers?
adding classpath under server start configuration doesnt work, also deploying with application and deploying on server as a library doesnt overrride default.
Thanks for help
First, basic checklist...you do use NodeManager don't you (server start tab won't do anything if you don't). Also, you made sure the new driver name is configured in the JDBC datasource (I'm assuming the driver is for a datasource right?)
Deploying in the app shouldn't do anything since the datasource object is created prior to deployment.
You might want to take the old ojdbc6.jar, for JDK 6, and ojdbc5.jar, for JDK 5, out of the directories to make sure they're not seen anymore.
Also, where in the classpath did you put the new path ? When you add another path you should always put it in the beginning (after patches though)
Related
I'm using CAS 5.2.4, deployed on Tomcat 9.0.8, running on Windows 10. I want to connect to LDAP, but I don't know where the cas.properties has to be placed.
I have already placed it in :
C:\etc\cas
C:\etc\cas\config
'tomcat'\cas\etc\cas
'tomcat'\cas\WEB-INF\classes
Ok, the problem was that I changed the property spring.profiles.active, I set it as production, now I change it, again, to standalone.
When the stand alone profile is active CAS search extra configurations in /etc/cas/config in particular the file standalone.properties.
When the production profile is active CAS doen not search more configuration files, except if the spring cloud is configurated.
Are you running 5.2.4 or 5.3.4? Given there is no such thing as 5.3.4, you may want to correct the question.
Also note that tomcat 9 is officially not supported.
Properties by default go to c:\etc\cas\config on Windows, which is the same path as /etc/cas/config on Linux. The initial "/" on windows is translated to be the root drive, which for you might be "c:".
I just downloaded glassfish 4.1.1 (previously I had 4.1). Last time I upgraded I remade my security realm and DB connections. This time I'm wondering if there is an easy way to move those from the previous version used to my new one.
Just downloaded Glassfish 4.1.1 myself and will face the same problem. I will first try the following workaround: Copy the relevant part from the C:\glassfish4\glassfish\domains\domain1\config\domain1.xml (or whatever your domain is called or where it is located) and paste it into the according spot in the new domain1.xml. Provided the relevant external resources exist (databases, LDAP, etc..) and the respective datasources or other glassfish resources exist as well, this should do the trick.
Start by searching your old domain1.xml for any name that you yourself introduced, such as the name of the realm or the datasource. Copy that relevant piece of XML, make a safety copy.
Then look where to fit it into the new domain1.xml.
Funny that security realms cannot be added via a glassfish resource via the NetBeans new-Menu, whereas connection pools and other stuff can. And it all is merely copied into the domain1.xml.
I need to disable basic auth on weblogic server, which can be done by adding <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials> into config.xml in a weblogic domain.
I'm deploying a web service to weblogic directly from IntelliJ Idea and every time I start deploy, the config.xml is replaced by a new one, so I cannot change config manually. I guess I need to pass some extra arguments in IntelliJ's run configuration. Does anyone has any experiences with this?
It was my mistake. I tried to modify config.xml and forgot my server is still running. According to this page I think it's pretty obvious why this happens. So, it has nothing to do with IntelliJ Idea.
Caution: Do not edit configuration files for a domain that is
currently running. Because Oracle WebLogic Server rewrites the files
periodically, your changes will be lost. Depending on your platform,
you also could cause Oracle WebLogic Server failures.
I would like to move a GlassFish domain from a GlassFish v3.x server (running Java 6) to a new server running GlassFish v4.x (running Java 8). The old configuration uses JNDI, JMS, a webservice, etc...
What is the best approach to handle this ? Can I just copy the domain folder to the new server ? Or do I have to export the config and restore it on the new server ?
Thanks
Right now we are doing the same thing in my company.
We were trying a few things like exporting domains, upgrading them or just coping the domain, unfortunately none worked ...
The only solution that worked without problems was coping the "important"
parts like resources from glassfihs 3 domain.xml to glassfish4 domain.xml.
Coping the full domain.xml content or file wont work..
Im trying to work in my project, when I change files it changes the file inside the directory that I imported the projects into my workspace. But the changes aren't showing up on the server because the server is using the folder inside .metadata/webapps/myapp etc
what have I done wrong here?
Sounds like you're deploying to the integrated Tomcat server. The deployment is normally to the .metadata/.me_tcat/webapps/myapp folder. Is this what you meant? If not then I suggest you remove the deployment and then deploy again and let the deployment location default. The folder .metadata/.me_tcap is simply where the integrated Tomcat installation looks for applications when it starts up.
You can check the deployment location by looking in the servers view. Expand the integrated Tomcat server. The deployment location for your project is shown there.
The deployed location should be kept in synch with your code. If that's not happening, it may be that the changes you're making are the kind that require a redeployment. I'm not sure what the conditions are for propagating changes but I guess there might be some situations where changes can't be picked up automatically in this way. The changes should be picked up on a redeploy.
To check, create a new web project, which will create some default configuration and a default index.jsp file. Deploy this to the integrated Tomcat server. Now make a change in the index.jsp file and save it. Check if the change is made in the deployment location, or simply run the server and check that your new index.jsp gets displayed.
For more help, I suggest you post to the forums at www.myeclipseide.com/forums