Re: Webtop installation on JBOSS : Windows

While installing Webtop on JBOSS I am encountered with below error . Kindly suggest how to troubleshoot . Also attached complete log file.

18:53:22,798 INFO [FileSystemContext] VFS forced fallback to vfsjar is enabled.

18:53:23,188 INFO [AbstractVirtualFileHandler] VFS force copy (NestedJarHandler) is enabled.

18:53:25,294 INFO [ServerInfo] Java version: 1.6.0_30,Sun Microsystems Inc.

18:53:25,294 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_30-b12)

18:53:25,294 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 20.5-b03,Sun Microsystems Inc.

18:53:25,294 INFO [ServerInfo] OS-System: Windows 7 6.1,x86

18:53:25,294 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms512M -Xmx512M -XX:MaxPermSize=512M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Dsun.lang.ClassLoader.allowArraySyntax=true -Djboss.vfs.forceVfsJar=true -Djboss.vfs.forceCaseSensitive=true -Djava.endorsed.dirs=C:Installsjboss-5.1.0.GA-jdk6jboss-5.1.0.GAlibendorsed

18:53:25,356 INFO [JMXKernel] Legacy JMX core initialized

18:53:28,289 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@bd5df[domain=default, server=default, name=default]

18:53:31,659 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/

18:53:41,238 INFO [NativeServerConfig] JBoss Web Services – Stack Native Core

18:53:41,238 INFO [NativeServerConfig] 3.1.2.GA

18:53:41,800 INFO [AttributeCallbackItem] Owner callback not implemented.

18:53:42,892 INFO [LogNotificationListener] Adding notification listener for logging mbean “jboss.system:service=Logging,type=Log4jService” to server org.jboss.mx.server.MBeanServerImpl@41a12f[ defaultDomain=’jboss’ ]

18:55:05,467 INFO [CopyMechanism] VFS temp dir: C:Installsjboss-5.1.0.GA-jdk6jboss-5.1.0.GAserverdefaulttmp

18:55:41,161 ERROR [ProfileDeployAction] Failed to add deployment: krbutil.jar

org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=webtop/WEB-INF/lib/commons-codec-1.3.jar} from krbutil.jar

at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)

at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)

at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)

at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)

at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)

at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)

at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)

at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)

at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)

at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)

at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

at org.jboss.Main.boot(Main.java:221)

at org.jboss.Main$1.run(Main.java:556)

at java.lang.Thread.run(Thread.java:662)

Caused by: java.io.IOException: Child not found webtop/WEB-INF/lib/commons-codec-1.3.jar for JarHandler@26746731[path=webtop/WEB-INF/lib/krbutil.jar context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/krbutil.jar], available children: [JarEntryHandler@3583147[path=webtop/WEB-INF/lib/krbutil.jar/META-INF context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/krbutil.jar!/META-INF/], JarEntryHandler@25309840[path=webtop/WEB-INF/lib/krbutil.jar/com context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/krbutil.jar!/com/]]

at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)

at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)

… 23 more

18:55:46,138 ERROR [ProfileDeployAction] Failed to add deployment: bpm_infra.jar

org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=webtop/WEB-INF/lib/castor-1.1-xml.jar} from bpm_infra.jar

at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)

at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)

at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)

at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)

at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)

at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)

at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)

at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)

at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)

at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)

at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

at org.jboss.Main.boot(Main.java:221)

at org.jboss.Main$1.run(Main.java:556)

at java.lang.Thread.run(Thread.java:662)

Caused by: java.io.IOException: Child not found webtop/WEB-INF/lib/castor-1.1-xml.jar for JarHandler@12116679[path=webtop/WEB-INF/lib/bpm_infra.jar context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/bpm_infra.jar], available children: [JarEntryHandler@3185168[path=webtop/WEB-INF/lib/bpm_infra.jar/META-INF context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/bpm_infra.jar!/META-INF/], JarEntryHandler@13808752[path=webtop/WEB-INF/lib/bpm_infra.jar/com context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/bpm_infra.jar!/com/], JarEntryHandler@21247461[path=webtop/WEB-INF/lib/bpm_infra.jar/org context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/bpm_infra.jar!/org/]]

at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)

at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)

… 23 more

18:55:55,452 ERROR [ProfileDeployAction] Failed to add deployment: jaxb-impl.jar

Related:

  • No Related Posts

Webtop 6.8.2 – Remember my credentials not working.

Recently, our Webtop 6.8.2 ‘Remember my credentials’ stopped working. Documentum Administrator works but Webtop does not….

In the Webtop wdk/app.xml the following is configured…

<save_credential>

<!– saved credentials functionality is turned on by default –>

<enabled>true</enabled>

<!– Default encryption key –>

<encryption_key>please specify your encryption key here</encryption_key>

<!– Disable saved credentials functionality in the following doccbases –>

<disabled_docbases>

<docbase></docbase>

</disabled_docbases>

</save_credential>

Thank you.

Related:

Dynamic Watch list map: Clicking on a monitor box

I have created a dynamic watch list map (https://www.ibm.com/support/knowledgecenter/en/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/webtop/wip/task/web_cust_map_settingportletprefs.html) but when I click on a monitor box, nothing happens. What’s going on?

Related:

Re: XCP 2.3 and DM_SYSOBJECT_E_INVALID_ACL_DOMAIN issue

XCP2 has a security feature that I can not understand the point, which creates many problems in production system, which contains webtop and XCP app, with complex processes and many users collaborating in case management.

XCP simply does not allow user to add document to case, even he is allowed to do that by ACL entries, if at least one of the conditions is met:

– user must be owner of ACL of the case

– ACL of the case is public (either owner is docbaseowner, ot ACL class is set to public)

This is problem in multi application and multi user environment, since at some point, ACL of the case may easily become regular, owned by some regular user, so that finally no other user may add document to case.

Completely ridiculous feature! Why this additional limit, if ACL entries define permissions on object?

Since everything works fine with DA or WebTop, it is clear that constraint is not implemented on Content Server or docbase level, but only on XCP app level. Which makes it more nonsense and ridiculous!

I have every day, in production, at least one issue of this kind. It happens that case, created within XCP app, is edited by WDK user. ACL class is changed to regular and case becomes “corrupted” for other users. In XCP processes I take care of setting ACL class to public or owner to docbaseowner whenever ACL is created, permission edited, but it happens that somehow ACL class is changed during the work.

Is there any way to solve this issue, to workaround somehow (but not to create scheduled job which runs often, query regular ACLs and makes it public)?

Thanks in advance,

Cane

Related:

Re: Re: XCP 2.3 and DM_SYSOBJECT_E_INVALID_ACL_DOMAIN issue

XCP2 has a security feature that I can not understand the point, which creates many problems in production system, which contains webtop and XCP app, with complex processes and many users collaborating in case management.

XCP simply does not allow user to add document to case, even he is allowed to do that by ACL entries, if at least one of the conditions is met:

– user must be owner of ACL of the case

– ACL of the case is public (either owner is docbaseowner, ot ACL class is set to public)

This is problem in multi application and multi user environment, since at some point, ACL of the case may easily become regular, owned by some regular user, so that finally no other user may add document to case.

Completely ridiculous feature! Why this additional limit, if ACL entries define permissions on object?

Since everything works fine with DA or WebTop, it is clear that constraint is not implemented on Content Server or docbase level, but only on XCP app level. Which makes it more nonsense and ridiculous!

I have every day, in production, at least one issue of this kind. It happens that case, created within XCP app, is edited by WDK user. ACL class is changed to regular and case becomes “corrupted” for other users. In XCP processes I take care of setting ACL class to public or owner to docbaseowner whenever ACL is created, permission edited, but it happens that somehow ACL class is changed during the work.

Is there any way to solve this issue, to workaround somehow (but not to create scheduled job which runs often, query regular ACLs and makes it public)?

Thanks in advance,

Cane

Related:

XCP 2.3 and DM_SYSOBJECT_E_INVALID_ACL_DOMAIN issue

XCP2 has a security feature that I can not understand the point, which creates many problems in production system, which contains webtop and XCP app, with complex processes and many users collaborating in case management.

XCP simply does not allow user to add document to case, even he is allowed to do that by ACL entries, if at least one of the conditions is met:

– user must be owner of ACL of the case

– ACL of the case is public (either owner is docbaseowner, ot ACL class is set to public)

This is problem in multi application and multi user environment, since at some point, ACL of the case may easily become regular, owned by some regular user, so that finally no other user may add document to case.

Completely ridiculous feature! Why this additional limit, if ACL entries define permissions on object?

Since everything works fine with DA or WebTop, it is clear that constraint is not implemented on Content Server or docbase level, but only on XCP app level. Which makes it more nonsense and ridiculous!

I have every day, in production, at least one issue of this kind. It happens that case, created within XCP app, is edited by WDK user. ACL class is changed to regular and case becomes “corrupted” for other users. In XCP processes I take care of setting ACL class to public or owner to docbaseowner whenever ACL is created, permission edited, but it happens that somehow ACL class is changed during the work.

Is there any way to solve this issue, to workaround somehow (but not to create scheduled job which runs often, query regular ACLs and makes it public)?

Thanks in advance,

Cane

Related:

Re: Viewing content through mobile native browser.

Dear all,

We currently has a request to view the content on the user mobile devices. However, we have try to use the mobile device to view the content on webtop or RM. It can only browse the folder structure. If we click on the file, it will loop and prompt error because of time out.

We know the reason is caused by the mobile device cannot run java and applet. We are thinking is it possible to build custom code to allow to view content on the mobile devices. Please share your experience to us, thank you.

Best Regards,

Chuck

Related:

Viewing content through mobile native browser.

Dear all,

We currently has a request to view the content on the user mobile devices. However, we have try to use the mobile device to view the content on webtop or RM. It can only browse the folder structure. If we click on the file, it will loop and prompt error because of time out.

We know the reason is caused by the mobile device cannot run java and applet. We are thinking is it possible to build custom code to allow to view content on the mobile devices. Please share your experience to us, thank you.

Best Regards,

Chuck

Related:

Re: 1-time-use Password confusing Webtop

We have Webtop cfg’d to authenticate via LDAP (which accepts a 1-time-use CryptoCard generated paswword).

8 minutes after Webtop login, regardless of what you have used Webtop for (even completely idle), the AUTH log shows that upon your next Webtop request, that Webtop is trying to re-authenticate. This always FAILS because the 1-time-use (now stale) pwd is supplied.

All session timeouts have been increased to 60 minutes, but the above still occurs.

My guess is that whatever logic is used when RSA authentication w/ 1-time pwds is cfg’d for Webtop (not exactly my case) needs to be engaged here (hopefully via some cfg param).

Related:

Re: webtop 6.8.2 import and export issue

Hello,

Preparing Tomcat:

You must disable tag reuse in /conf/web.xml. Find the JSP servlet entry and set the

enablePooling initialization parameter to false.

For the HttpOnly cookies support, perform the following:

• Add the following in server.xml within the <Engine> and <Host> tags:

<Context path=“/webtop” useHttpOnly=”true”/>

If there are multiple applications deployed, then the HttpOnly property can be set for each

application in Tomcat’s server.xml. For example:

<Context path=”/da” useHttpOnly=”false”/>

<Context path=”/webtop” useHttpOnly=”true”/>

<Context path=”/dam” useHttpOnly=”false”/>

Related: