WebSphere 8.5: Importing 6.1 Profile ends with "fail to deploy application isclite" - websphere

On the 6.1 server I run...
$AdminTask exportWasprofile {-archive c:/tmp/my.car}
On the 8.5 server I see...
$AdminTask importWasprofile {-archive c:/tmp/my.car}
WASX7015E: Exception running command: "$AdminTask importWasprofile {-archive c:/
tmp/my.car}"; exception information:
com.ibm.wsspi.configarchive.ConfigArchiveException
com.ibm.wsspi.configarchive.ConfigArchiveException: fail to deploy application isclite
Is there something special I have to do to properly migrate profiles? Is there a place I can look to get more info as to what is going wrong?

From IBM WebSphere Application Server Migration Toolkit's website:
The IBM® WebSphere® Application Server Migration Toolkit is a suite of
tools and knowledge collections that enables your organization to
quickly and cost-effectively migrate to WebSphere Application Server
V7, V8, or V8.5, whether from a previous version of WebSphere
Application Server or competitive application servers including Apache
Tomcat Server, JBoss Application Server, Oracle Application Server,
and Oracle® WebLogic Server.
You should use it as it's bundled in WebSphere Application Server 6.1 (and higher) and offers two scripts that help you in the migration: WASPreUpgrade and WASPostUpgrade.
WASPreUpgrade "saves the configuration of a previously installed version of WebSphere Application Server into a migration-specific backup directory." while WASPostUpgrade "retrieves the saved configuration that was created by the WASPreUpgrade command from the backupDirectory that you specified." (quoting their pages).
Although they might be using wsadmin/Jython, I think you may have more success with these two command-line utilities.

Related

Rational application developer(RAD) 9.6 cannot use Websphere Application Server 8.5?

I installed the Rational application developer(RAD) 9.6, and find that there is no WebSphere Application Server 8.5 in the option list when config the new server.
Define new server options
WebSphere 8.5 traditional is available with RAD 9.6. I have it here. You do have to select it during the installation process. Or you can use Installation Manager to Modify and add it:

weblogic 10.3.6 application all time availability

I am using weblogic 10.3.6. I have a cluster configured and there are two managed servers MS-1 and MS-2. Now I have deployed my EAR into MS-1 and it is working fine. Now my requirement is while the application is running if somehow the MS-1 breaks down,all i want is that my application runs by switching to MS-2 ,that is I want my application to available all time, I am new to weblogic ,please help me .Detailed steps are needed
Weblogic Server 10.3.6 documentation : https://docs.oracle.com/cd/E23943_01/nav/wls.htm
WebLogic Server & Apache http server : https://docs.oracle.com/cd/E23943_01/web.1111/e16435/apache.htm#PLGWL395

IBM Worklight - Can't run an app on WebSphere Application Server

My app runs well on Worklight Development Server, but not on WebSphere Application Server V8.5 Liberty Profile.
I tried both Oracle JDK and IBM JDK, there was no difference.
There was no problem connecting to the server with jconsole, although I had to connect without ssl.
On Eclipse Console,
[2014-07-11 17:18:10] Starting build process: application 'U1', all environments
[2014-07-11 17:18:12] Application 'U1' with all environments build finished.
[2014-07-11 17:18:12] Deploying application 'U1' with all environments to Worklight Server...
[2014-07-11 17:19:02] Failed to deploy the application to Worklight server: : JMX configuration error. Unable to obtain MBeans. Reason: "FWLSE3012E: JMX configuration
error. Unable to obtain MBeans. Reason: "Connection refused".".
Thank you.
I do not know how the Studio deploys to an external Liberty server.
You could also:
Install Worklight Server and deploy using
- the Server Configuration Tool
- or the ant tasks (provided by the Worklight Server installer)
- or manual procedure documented at https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_wlconsole_install.html
The manual procedure may give you hints about what is missing in your External Liberty Server.
It could be:
- rest connector and it's configuration https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/install_config/t_optional_config_app_server_liberty.html
- JNDI properties so that Liberty can use the REST connector (step 3 at https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_configuring_liberty_profile_for_wladmin_manually.html )

Publishing to WebSphere Application Server v7.0

I am using WebSphere Application Server v7.0 with Eclipse helious 3.6.2, it was working smooth previously with my java web projects, but I have just changed the properties of my project using runtime jre6, which was previoursly using jre6 comming with WebSphere as alternate runtime.
Then without testing I again reset my runtime back to runtime in WS. But now server is started quite well, but when I try to publish my project, it throws error and I can't publish it successfully and I am unable to run my project. I am using JMS in my project.
here is the msg:
Problem Occured: 'Publishing to WebSphere Application Server v7.0 at
localhost...' has encountered a problem An internal error occured
during: 'Publishing to WebSphere Application Server v7.0 at
localhost...'
Details: An internal error occurred during: "Publishing to WebSphere
Application Server v7.0 at localhost...".
com/ibm/CORBA/iiop/ORB
i forget to edit the eclipse.ini file in eclipse home folder, and changed the vm parameter value back to the
C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin\javaw.exe

Pmi Client is not created while using with sun java instead of IBM java

My task to monitor the IBM Websphere through pmi client.Pmi client is an agent provided by the IBM to get MBeans and is running under IBM Java. I tried it to run under Sun java. But, it fails to create the Pmiclient. Did Anyone come across this issue?
The IBM JRE has slightly customized classes. This is unfortunately not uncommon with PMI (and also JMX by the way) when working with different WebSphere Application Server versions.
There are hacks around involving copying the relevant IBM implementations and running them with the Sun/Oracle JRE but I don't think that is valid according to the licensing terms. What you really should do is to use the IBM provided JRE.
If you want a riskless shortcut you will build an applicaton (perhaps EJB or servlets) that runs on the WebSphere Application Server and exposes the results from PMI via custom interface. For instance web service.

Resources