I am upgrading weblogic 10.3.5 to 12.1.1, and to d so, I am using weblogic upgrade wizard.
I started with upgrading security providers using command - java -classpath /localdata/weblogic/server/lib/weblogic.jar weblogic.Upgrade -type securityproviders
But it displays "Upgrading old security providers to new 10.3 providers", while I am running it from weblogic 12.1.1 and want to upgrade to this version.
Logs printed are :
Calling Wizard framework for upgrade: args2: [-mode=gui, -file=wcf/plugin_gui_wizard.xml, -log=stdout, -p:plugin:plugin.executionPlan.file=weblogic/upgrade/upgradesecurityproviders/execplan.xml, -p:plugin:I18N_PLUGIN=weblogic/upgrade/i18n_upgrade, -p:plugin:TARGET_VERSION=12.1.1.0]
I cross verified, on which version I am running upgrade wizard using java -classpath /localdata/weblogic/server/lib/weblogic.jar weblogic.version and it shows,
WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491
Snapshot is :
And snapshot from doc provided by Oracle (where it shows 12.1 wizard) is :
Note : If I proceed and select source directory as 10.3 mbeantypes and destination directory as 12.1 mbeantypes, wizard shows error as below for all jars (not showing all line) :
Not upgrading commo.dtd because either this is an out-of-the-box Oracle security provider JAR or this security provider JAR is already upgraded or this is not a valid archive file (may not be a .jar).
No security provider JARs have been upgraded.
and similar for other jars too.
Any idea what I would have missed? Am i following wrong approach?
Related
Started using Eclipse a week ago and today while i was creating a new server i got this error
Tomcat Installation Error
Error occurred installing server: https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.zip
https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.20/bin/apache-tomcat-10.0.20.zip
This is bug 580174, which is using a download URL for 10.0.20 that expired once Apache released Tomcat 10.0.21. You can manually download and unzip https://dlcdn.apache.org/tomcat/tomcat-10/v10.0.22/bin/apache-tomcat-10.0.22.zip and use the directory it creates as the installation's location.
This will be fixed in the 2022-09 release.
I have a web application that run on tomcat 8.5.34 and use the single sign on login with saml/onelogin api.
Here the specifications:
Amazon corretto Jdk 1.8.0_252
Apache tomcat 8.5.34
OS Windows 10
java-saml-2.4.0.jar and java-saml-core-2.4.0.jar
Everithing was fine until we upgrade the tomcat version to 8.5.69, from that version the redirect to our application stopped to work.
Here every attempt to fix the issue:
Upgrade the java-saml api --> fail
Upgrade the tomcat version till the last 9 release --> fail
Change the attribute classname in the tag CookieProcessor to the org.apache.tomcat.util.http.LegacyCookieProcessor --> fail
After all we found two solutions:
Downgrade the tomcat version (that is not possible in production server, we are migrating to tomcat 9)
Change the attribute sameSiteCookies in this configuration in context.xml <CookieProcessor sameSiteCookies="lax"/> from lax to unset, but this configuration involve my application in a security problem named CSRF attacks so i cant pass VAPT tests.
Now i am in a bottleneck, any suggestions?
Thanks to the all community.
I am trying to setup production redeployment on WebLogic 11 using WLST.
Applications, that I am using for that are standard oracle simple applications:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/12c/14-Redeployment--4465/redeploy.htm
As first, I've deployed simple.war from /tmp/deployversion1/simple.war, and it was deployed successfully.
That simple.war has MANIFEST.MF:
Manifest-Version: 1.0
Class-Path:
Created-By: Bill Bell
Weblogic-Application-Version: v1
Then, I've tried to deploy simple.war with v2 version. It has manifest:
Manifest-Version: 1.0
Class-Path:
Created-By: Bill Bell
Weblogic-Application-Version: v2
From the Oracle documentation, if manifest has a version inside of it, I may not provide versionIdentifier parameter for deploy/redeploy.
And it works for WebLogic 12.
My WLST code, thar doing the redeployment is:
redeploy(appName = 'Simple', appPath = '/tmp/deployversion2/simple.war')
After it I found, that application wasn't deployed, and in weblogic log:
<Dec 21, 2016 3:11:07 PM PST> <Error> <Deployer> <BEA-149091> <An attempt was made to deploy application 'Simple' with specified archive version 'v1'. However, the application archive as specified in the source has version 'v2'.>
But if I doing redeploy this way(versionIdentifier provided), it works fine:
redeploy(appName = 'Simple', appPath = '/tmp/deployversion2/simple.war', versionIdentifier='v2')
Also, it works if I doing deploy again, even without version:
deploy(appName = 'Simple', appPath = '/tmp/deployversion2/simple.war')
And, finally, it works if application is being deployed with weblogic.Deployer:
java weblogic.Deployer -adminurl http://localhost:7001 -user weblogic -password ******** -redeploy -source /tmp/deployversion2/simple.war -name Simple
So, I have few questions about it.
1) How can I do production redeployment using WLST for WebLogic 11 and WebLogic 12 with one script?
2) Why WLST redeploy fails, but weblogic.Deployer -redeploy works fine, if parameters are the same?
3) What the difference between deploy and redeploy, if deploy result for WebLogic 12 is exactly the same as redeploy result?
4) Can I use for WebLogic 11 deploy() instead of redeploy() to avoid BEA-149091 error?
Thanks.
Windows 7, java 8, Neo4j 3.0.0-M03, initial install of structr.
When I first try to run the program I'm getting this error:
SEVERE: Vital service HttpService failed to start: No resource provider available for servlet JsonRestServlet. Aborting
Reading the Google Groups the report is that structr is only good up to 2.2.6 - looking at the Neo4j Release Page 2.2.6 has been skipped - it goes from 2.1.8 to 2.2.8.
My question is what version should I use?
Also - is java 7 still a requirement? Looking at the Oracle website I'm seeing that 7 has been deprecated and won't be patched.
The most recent pre-built versions of Structr are built against and embed Neo4j 2.2.8.
To use with custom Neo4j versions, you can to build your own driver, see https://github.com/structr/structr-neo4j-driver. Should work with any 2.x version of Neo4j.
On the Java side, Java JDK 8 is a requirement.
I have a web application running on tomcat. I want to deploy it on a weblogic server but i get some problems.
Error(s) found in module 'BatchMonitoring'. Publish was cancelled. See "Problems" view for details.
Target runtime SpringSource dm Server (Runtime) v1.0 is not defined. at BatchMonitoring
Java compiler level does not match the version of the installed Java project facet. at BatchMonitoring
java.lang.IllegalArgumentException: Cannot find state with id 'displayError' in flow 'admin_main' -- Known state ids are 'array<String>['queryAll', 'mainForm', 'register']'
at org.springframework.webflow.engine.Flow.getStateInstance(Flow.java:348)
at org.springframework.webflow.engine.support.DefaultTargetStateResolver.resolveTargetState(DefaultTargetStateResolver.java:60)
at org.springframework.webflow.engine.Transition.execute(Transition.java:217)
at org.springframework.webflow.engine.impl.FlowExecutionImpl.execute(FlowExecutionImpl.java:391)
at org.springframework.webflow.engine.impl.RequestControlContextImpl.execute(RequestControlContextImpl.java:214)
at org.springframework.webflow.engine.support.TransitionExecutingFlowExecutionExceptionHandler.handle(TransitionExecutingFlowExecutionExceptionHandler.java:110)
at org.springframework.webflow.engine.FlowExecutionExceptionHandlerSet.handleException
Seems like you had problems with Java versions of what Tomcat is using(points to JAVA_HOME) at environmental variable and JDK of Weblogic. Also it would be good if you send some logs and exception messages.