Hello Experts,

we have installed the service pack (Latest)on source version wM8.2.1.

Service needs java1.7 we pointed the JAVA 1.7 package from webMethods installation package.(JVM)

Then successfully installed the service pack on webMethods 8.2.1.

source wM8.2.1 is in Java 1.6.

After installation of service pack IS and Update manager failed to start

server.bat failed with following error

"
the system cannot find the path specified

"
Then we have tried to start Update manager same issue with java version.

please suggest on this.

thanks in advance.

Thanks,
Ram.

Try to look at logs if you find more details.

@mahesh
Thanks for the reply…

Failed to start the integration server

error log:

Caused by: java.lang.NoClassDefFoundError: com/softwareag/platform/jaas/proxy/LoginModuleFactoryRegistry
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2413)
at java.lang.Class.getConstructor0(Class.java:2723)
at java.lang.Class.newInstance0(Class.java:345)
at java.lang.Class.newInstance(Class.java:327)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleAct
ivator(AbstractBundle.java:151)
… 26 more
Caused by: java.lang.ClassNotFoundException: com.softwareag.platform.jaas.proxy.
LoginModuleFactoryRegistry
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundl
eLoader.java:460)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
java:422)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.
java:410)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(De
faultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)… 32 more
Feb 26, 2018 6:42:58 AM com.webMethods.sc.config.ConfigurationLogger log
WARNING: Failed to process OOB file-change event on file 'E:\sagDIR82\profiles\IS\configuration\org.eclipse.equinox.app.manager.tmp5331994614044302403.instance.

Thanks,
Ram.

Hi,

please check for the Java 1.7 Update (as a Fix) for wM 8.2 to switch from Java 1.6 to Java 1.7.

Generally a Java 1.6 application should run in Java 1.7 but not vice versa.
But there might be a need to modify certain runtime settings to get IS 8.2 working with Java 1.7 which are applied with the Java Fix.

Regards,
Holger

Hi,

Thanks for the reply.

We will try applying fixes on IS to switch from Java 1.6 to Java 1.7

Can you be more specific on Runtime settings to get IS(wM8.2) work with Java1.7.

Also, can you suggest the usage of MWS DB tables…

Are that tables required while migration.

Thanks in advance.

Thanks,
Ram.

Hi Ram,

the settings will be applied automatically together with the new JVM/JDK being applied to your installation.
The settings should be documented in the Readme of the Fix.

Before creating the MWS instance the MWS DB tables should be created in the DB as during instance creation MWS initializes some data there.
It is highly recommended to use a real database instead of the embedded one especially if you are planning to use Optimize, TaskEngine or Central Users Management.

Regards,
Holger

Actually for MWS the embedded database is only for use when you are installing My webMethods Server for the sole purpose of running the Broker Messaging user interface. In all other cases an external RDBMS should be used. This is in the Installing SAG Products guide.

thanks

Marianne

Thanks to all,

we are using external Database.
Since we are not using any task engine and Optimize and using only Central user management.

Is it MWS tables need to migrate or not?

Because I don’t want to go through migration utility for MWS and IS.

Only we are using IS, TN, Broker in older wM8.2 and now planning to move UM.and MWS using for TN transactions.

Thanks,
Ram.

Hi,

thanks to Marianne for clarifying requirement for external database usage.

I would recommend using Database Configurator to migrate the database schemas to the latest version.
Otherwise it can happen that the servers do not start or will not behave as expected due to mismatches.

Regards,
Holger