Title:How to Resolve Fatal Error due to missing system mandatory properties for server startup   Fact: Interstage BPM (Business Process Manager) V11.4.1 Build IF1141013   Fact: Oracle 12c   Fact: JBoss EAP (Enterprise Application Platform) V6.4.9 GA   Fact: Windows Server 2012   Fact: JDK 1.8.0_192   Symptom:JBoss failed to start due to the following fatal errors found in server.log: 18:47:42,464 INFO (ServerService Thread Pool -- 77) JBAS018210: Register web context: /fujitsu-ibpm-startup-webapp18:47:43,964 INFO (ServerService Thread Pool -- 77) WARN : SYSTEM: TID=838425121: Some fatal error has occurred, server will be shutdown now. {Following system mandatory properties are missing for server startup ''ServerHost','ServerRoot','ServerSharedRoot','JMSNamingProviderURL''}18:47:43,964 INFO (ServerService Thread Pool -- 77) Some fatal error has occurred, server will be shutdown now. {Following system mandatory properties are missing for server startup ''ServerHost','ServerRoot','ServerSharedRoot','JMSNamingProviderURL''}18:47:43,965 INFO (ServerService Thread Pool -- 77) at com.fujitsu.iflow.commonee.SystemEnvironment.initialize(SystemEnvironment.java:144)18:47:43,965 INFO (ServerService Thread Pool -- 77) at com.fujitsu.iflow.serveree.impl.common.IflowStartup.startTimer(IflowStartup.java:107)18:47:43,966 INFO (ServerService Thread Pool -- 77) at com.fujitsu.iflow.startup.IflowStartupServlet.init(IflowStartupServlet.java:23)18:47:43,966 INFO (ServerService Thread Pool -- 77) at javax.servlet.GenericServlet.init(GenericServlet.java:242)18:47:43,966 INFO (ServerService Thread Pool -- 77) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1206)18:47:43,967 INFO (ServerService Thread Pool -- 77) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1112)18:47:43,967 INFO (ServerService Thread Pool -- 77) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3593)18:47:43,967 INFO (ServerService Thread Pool -- 77) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3802)18:47:43,968 INFO (ServerService Thread Pool -- 77) at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163)18:47:43,968 INFO (ServerService Thread Pool -- 77) at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61)18:47:43,968 INFO (ServerService Thread Pool -- 77) at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96)18:47:43,969 INFO (ServerService Thread Pool -- 77) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)18:47:43,969 INFO (ServerService Thread Pool -- 77) at java.util.concurrent.FutureTask.run(FutureTask.java:266)18:47:43,969 INFO (ServerService Thread Pool -- 77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)18:47:43,970 INFO (ServerService Thread Pool -- 77) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)18:47:43,970 INFO (ServerService Thread Pool -- 77) at java.lang.Thread.run(Thread.java:748)18:47:43,970 INFO (ServerService Thread Pool -- 77) at org.jboss.threads.JBossThread.run(JBossThread.java:122)18:47:43,971 INFO (ServerService Thread Pool -- 77) Caused by: Following system mandatory properties are missing for server startup ''ServerHost','ServerRoot','ServerSharedRoot','JMSNamingProviderURL''18:47:43,971 INFO (ServerService Thread Pool -- 77) at com.fujitsu.iflow.common.BaseSystemEnvironment.checkIfMandatoryPropertyPresent(BaseSystemEnvironment.java:2009)18:47:43,972 INFO (ServerService Thread Pool -- 77) at com.fujitsu.iflow.common.BaseSystemEnvironment.validateMandatoryProperties(BaseSystemEnvironment.java:1954)18:47:43,972 INFO (ServerService Thread Pool -- 77) at com.fujitsu.iflow.common.BaseSystemEnvironment.checkMandatoryProperties(BaseSystemEnvironment.java:1937)18:47:43,972 INFO (ServerService Thread Pool -- 77) at com.fujitsu.iflow.commonee.SystemEnvironment.initialize(SystemEnvironment.java:87)18:47:43,972 INFO (ServerService Thread Pool -- 77) ... 16 more18:47:43,973 INFO (ServerService Thread Pool -- 77) 18:47:44,033 ERROR (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."fujitsu-ibpm-engine.ear"."fujitsu-ibpm-engine-ejb.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."fujitsu-ibpm-engine.ear"."fujitsu-ibpm-engine-ejb.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "fujitsu-ibpm-engine-ejb.jar" of deployment "fujitsu-ibpm-engine.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011030: Could not configure component ProcessInstance at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:96) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) ... 5 moreCaused by: java.lang.IllegalStateException: Container is down at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:691) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:243) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2433) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:345) at org.jboss.as.ejb3.security.EJBSecurityViewConfigurator.configure(EJBSecurityViewConfigurator.java:160) at org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:68) at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:82) ... 6 more Fix: The issue occurred during reverse lookup of IP to hostname at BPM startup. Step 1:Check IBPMPROPERTIES for the four missing system properties by executing sql query: Execute sql query to see the key for the four system properties: select * from IBPMPROPERTIES WHERE tenantid=-1; 'ServerHost','ServerRoot','ServerSharedRoot','JMSNamingProviderURL'   Refer to BPM Administration Guide of the four System parameters.They must exist in IBPMPROPERTIES table in the PROPERTYKEY column in the following format for single server setup. Cluster will be different. Refer to admin guide for cluster format:ServerHost.{HOSTNAME}ServerRoot.{HOSTNAME}ServerSharedRoot.{HOSTNAME}JMSNamingProviderURL.{HOSTNAME}   Step 2: Check hosts file, typically found in C:\Windows\System32\drivers\etc\hosts for Windows or /etc/hosts Linux. Make sure there is only one valid entry of IP to mapping. This symptom can be reproduced if the following were found in hosts file:   192.168.217.132 interstagedemo2 #invalid alias which doesn't exist192.168.217.132 interstagedemo #intended valid entry   ping -a 192.168.217.132 should return the intended hostname found in step 1.   To fix the issue, simply remove the invalid entry or correct the mapping in hosts file. This post was edited by C.Y. Chen at December 13, 2018 5:41:04 PM PST

Title: Resetting Users List is Sufficient   Fact: Interstage BPM (Business Process Manager) V11.4.1   Fact: Microsoft Active Directory   Fact: BPM Local Store   Fact: Interstage BPM Console System Administration for User and Group Management   Fact: Interstage BPM Model API method com.fujitsu.iflow.model.workflow.WFAdminSession.resetLDAPGroupsList()   Fact: Interstage BPM Model API method com.fujitsu.iflow.model.workflow.WFAdminSession.resetLDAPUsersList()   Fix: Resetting both cached groups and users can be redundant and adding unnecessary operation to server caching of groups. BPM Model API allows refreshing groups and users kept in server cache. Specifically, to update caching of users in server memory is done via model API method com.fujitsu.iflow.model.workflow.WFAdminSession.resetLDAPUsersList(),while updating cache of groups in server memory is done via model API method com.fujitsu.iflow.model.workflow.WFAdminSession.resetLDAPGroupsList().   In BPM Console System Administration page, the context operation for users and groups is available to invoke the API method mentioned above.For details, refer to Console documentation https://interstagebpm.com/console/web/help/Console/t_UserOperations.html for refreshing users list from Directory;refer to https://interstagebpm.com/console/web/help/Console/t_GroupOperations.html for refreshing groups list either locally or remotely from LDAP. What needs to be kept in mind is that resetting the users list is actually resetting both caches for users and groups, while resetting the groups will only update the cache for the groups whether local or remote. Therefore, updating users list is sufficient and there is no need to explicitly update groups list in cache again.  

Title: How to Update Edgar Validator in XWand ToolKit   Fact: Interstage XWand ToolKit V13.4.0   Fact:  EFM (Edgar Filer Manual) Volume II Version 39   Fact:  EFM (Edgar Filer Manual) Volume II Version 41   Fact:  EFM (Edgar Filer Manual) Volume II Version 42   Fact:  EFM (Edgar Filer Manual) Volume II Version 43   Fix: Below is a typical download link for the updated Edgar Validator for XWand ToolKit.   Download Link: https://software.fsw.fujitsu.com/DownloadPlus/confirm.asp?productID=8&itemID=724&urlID=-1&OfferToSendPackage=0 Download Information: Interstage XWand EDGAR Filing Validator Item label: Interstage XWand EDGAR Filing Validator V41 for XWand ToolKit Item filename: efmv_41_java_20170602.zip Zip file is password protected.  Obtain password from Fujitsu support organization.   Note that EFM v41 validator is compatible with v42 and v43.  If you have applied the update correctly, you should expect to see v41 during edgar validation.   You need to apply the jar files to the two folders as shown below.  You will be prompted to overwrite and replace, please choose yes or OK. C:\Program Files (x86)\ISXWand\XWand-tk\tools\xbrl21\plugin C:\Program Files (x86)\ISXWand\XWand-tk\tools\xwviewer\plugin   This post was edited by C.Y. Chen at October 19, 2017 6:06:16 PM PDT

Title: How to Enable Telnet Client on InterstageDemo VM   Fact: CentOS 7   Fact: Interstage BPM V11.3.1    Fact: Interstage BPM V11.4.0   Fact:  Interstage BPM V11.4.1   Fact: InterstageDemo VM v60 onwards   Symptom: issue telnet command returns with the message: telnet: command not found   Fix: At the command-line prompt, issue the following command to download and install telnet client:   yum install telnet  

Title: XWand Tool Fails to Launch due to Missing Java Runtime Environment   Fact: XWand ToolKit Version 13.4.0   Fact: XWand ToolKit Version 13.3.0   Fact: XWand ToolKit Version 13.2.0   Fact: Java 1.7   Fact: Java 1.8   Fact:  Windows 7 Professional   Fact: Windows 10   Symptom: Launching XWand Viewer or some other tool fails with the following error:     Fix: The error indicates that XWand Tool launcher couldn't find the needed JRE whether Java 1.7 or 1.8 depending on the version of XWand ToolKit in use.  The Java version supported is mentioned in the software release guide.   To fix the error, confirm whether the required Java is installed in the machine. If not installed, then install the missing Java version 64 bits.  This should fix the problem.   Another possible scenario is that Java is available in the file system, but it is not set up in the environment variable.  To fix it, one suggestion is to add or edit the User environment variable called "PATH" and set the value by pointing to the bin directory of the Java runtime environment.   Below is a snapshot of how the user environment variable is set up: Open Windows Explorer > select My Computer icon > right click on properties > to bring up Control Panel\Ssytem > locate "Advanced system settings > System properties dialog will pop up as shown below:   Click on Environment Variables button.   If PATH doesn't exist, then add a new variable; otherwise, just edit the existing to append the required Java runtime environment by pointing to its bin directory.     Click on OK.  You may not need to restart your machine. You can now open a DOS console and issue the following command to see what returns: java -version   You should expect to see the version of Java runtime environment specifed in the new user environment variable called "PATH".     Now you have the JRE (Java Runtime Environment) set up in your environment, you can test to launch one of the XWand Tools.