upgrade WebLogic from 10.3.2 to 12.1.1 - weblogic-10.x

1.Is it possible to upgrade the WebLogic application server version
from 10.3.2 to 12.1.1 with some utility (like an inplace upgrade)?
How much time it will take?
Is it possible to install new version prior to go-live with the same port number so that we can reduce the downtime requirement?
If same port number is not possible during installation, how easy to
change the port numbers during the go-live?

You can upgrade weblogic 10.3.2 to 12c...
Before upgrading you need to check the compatibility..
Please check the below link for more details...
http://docs.oracle.com/middleware/1212/wls/WLUPG/compat.htm
you can use the different port number while installing...But later you can change the port numbers which are same as 10.3.2
Once the application is good with other port numbers then you can change those ports as per your requirement on go live day...so you need to shutdown/stop the 10.3.2 instance and need to start the 12c instace...

Related

MQ Migration Process steps from lower version to Higher version[ MQ7 to MQ9]

Current version running is MQ7 in windows 2008 server. What to know about migration process steps from MQ7 to MQ8/MQ9?.New Version of MQ8/MQ9 Server to be installed and how existing Queue definition can be migrated?
Will Server Installation take care of QM definition also?
windows 2008 server will be good for mq9?
There is a MQ-Client7 contacting MQ-Server7, so if we upgrade MQ7 to MQ9 then MQ-Client also will be upgraded to MQ9?
There will be any issue in contacting MQ9-Client to MQ7 Server?
dspmqver will give MQ server details , how to verify MQ-Client version?
If you install the new version (V8 or V9) as an upgrade to the V7 installation on the same machine then then next time you start the queue manager it will be migrated to the new version.
If you install the new version alongside the V7 installation on the same machine, then you have to use the setmqm command to force the queue manager to move from V7 to the new version.
If you install the new version on a completely different machine, the no automatic migration can take place. You will have to create a brand new queue manager and then copy across the definitions from the old one.
The command to export all the object definitions is:
dmpmqcfg -m QM1 -x all > DEFS.mqs
The command to import all the object definitions is:
runmqsc QM1 < DEFS.mqs
The system requirements (e.g. minimum O/S levels) are documented by IBM here.
There is no requirement for the MQ Client to be the same version as the MQ Queue Manager. The MQ Client can be a higher version or a lower version than the MQ Queue Manager and still operate perfectly. The only thing to remember if the MQ Client is a higher version than the MQ Queue Manager is that new features cannot yet be used.
You can see the version of the MQ Client being used when it connects to the queue manager by looking in DISPLAY CHSTATUS for the field called RVERSION.

Can't install Apache web agent for OpenAM implementation

I have previously installed a J2EE policy agent and implemented SSO with it. Now I was trying to do the same with a web policy agent, but I am stuck. When I am trying to install the Apache22 web agent, I am being asked to provide some inputs. The second input is the URL of the OpenAM server. In my case, that is http://openam.example.com:9080/openIdp2 . But whenever I enter this value, the installation gets stuck. I have taken the following steps:
I have ensured that the openAM server is up and running.
I have created a centralized web agent in the openAM server.
I have installed OpenSSL and included the libeay32.dll, ssleay32.dll files in the agent/lib folder( I don’t have the ‘dll files missing’ error)
I have added the agent/lib folder in the environment variable path.
I have done all this and yet I am getting nowhere. I had used these same steps when I had configured the J2EE agent earlier. The OpenAM server is deployed in Tomcat on my local machine.
This is the configuration I am using:
Http server: Apache 2.2
Web Policy Agent:
i)Release: 4.0.0
ii)Platform: Apache 2.2
OS: Windows 10 64 bit
When I tried installing using the ‘silent’ option, I was asked to provide all the input. I did that and now the console is just stuck with the ‘Validating…’ message. It has been in that way for some time. The installation doesn’t stop, it just freezes.
Can you tell me what I might be doing wrong?
Can anyone help me out?
I had a similar issue a while back and was advised to step-back to the 3.3.4 Agent. Since there were no features I needed in 4.0 that were not in 3.3 I did and have not looked back. Also, consider that the latest agent available is 4.0.1. So either go back to 3.3.4 or consider trying 4.0.1.

How to migrate SonarQube to new host

Need to migrate my SonarQube to a new server (not the remote DB, just the application). Is there any special tool offered by Sonar to do so? is it just a matter of pointing this new installation (if possible) to the old DB?
Sonar v5.2
MySQL 5.x
Thanks!
I do this regularly as the servers I run on are only provisioned for 30 days. You don't specify the operating system, but for windows it's as simple as:
Stop "old" service
Copy folder from old machine to new machine
Install the windows service with the java wrapper
Start the service
In my case I change the DNS alias after the service is running

MQ 6.0 testing by UFT 12.02

I am trying to configure test automation project in UFT 12.02 for IBM Websphere MQ 6.0
I am facing the following error while connecting to MQ Queue Manager
(To run tests with IBM’s MQ client, make sure to install the MQ client on all machines running these tests.)
as per the above error description I need to install MQ client on my machine, but I cannot install it because IBM has been stopped supporting MQ 6.0 accordingly I didn't find it anywhere.
I have configured the same but in IBM RIT (Rational Integration Tester) and it was only required to configure the JAR files (com.ibm.mq.jar & connector.jar)
My question is; Is it applicable in UFT to configure only above two JAR files (just like IBM RIT) or it is necessary to install the MQ 6.0 Client?
And can I test the MQ 6.0 through UFT along with installing MQ 7.0 Client instead of 6.0, taking in consideration that the AUT is IBM Websphere MQ 6.0?
Also if applicable, can anyone provide the MQ Client download URL rather than IBM website?
Prior to V8.0 it was required to install the full client to receive support. Just grabbing the jar files worked but you risked IBM not supporting it if you wanted to open a PMR.
As of v8.0, IBM offers an all-Java client. I just provided the download instructions in another answer so instead of copying them, I'll link to that answer:
WMQ V8 Connection Factory setup on Tomcat using JNDI
One of the reasons this was not previously supported was that the old Java jars didn't have as much diagnostic function built in. IBM relied on the full client install for binary cient-side tracing, test programs, etc. The v8.0 stand-alone jars are really the way to go if you need an all-Java solution.
Note that support is based on the QMgr's license, not the client license (because that's free). If you are running a v6.0 QMgr other than the Linux Itanium version, then either you are paying a LOT of money for IBM Support or are running unsupported. If it is the latter, then you can't open a PMR anyway.
An unpatched v6.0 QMgr is effectively not secure. Even if you have applied the recommended security configurations, enough security-relevant APARS have now been discovered that you should consider an unpatched QMgr as being wide open.
As Tim notes in the comments, any version of MQ Client is supported with any version of MQ QMgr. Head over to the SupportPacs page and look for ones with names like MQC**. Pro tip - If you download a new client, it comes with XA transactionality enabled. No need to go grab the transactional client jar file (which put you out of license compliance anyway).

Can ehcache monitor be configured over https?

I have an application that is running on a secure site and I installed the ehcache probe jar. Everything seems to be running but I can't access it through the browser because by default the server is running on secure https.
Is there a way to view the monitor through https://myserver.com:9889/monitor?
I'm using the 30-day trial development version of ehcache monitor. Could this be the problem and perhaps the paid production version works?
Thanks.
You are using a free version and some resources maybe are not working or has a restriction , remember all that is free won't work perfect.

Resources