Error when opening new empty project in Tibco Designer: Tibco Designer issue

Hi all,

Unable able to open "RECENT LIST OF PROJECTS" in TIBCO Designer

When we open an empty project in TIBCO designer, you may get the below error:

In Error Stack you can see this:

java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at com.tibco.net.CGI.parseDataInto(CGI.java:330)
at com.tibco.ae.tools.designer.RecentProjectsRegistry.remove(RecentProjectsRegistr y.java:77)
at com.tibco.ae.tools.designer.RecentProjectsRegistry.documentOpened(RecentProject sRegistry.java:136)
at com.tibco.ae.tools.designer.AEApplication.fireDocumentOpened(AEApplication.java :3244)
at com.tibco.ae.tools.designer.AEApplication.newDocument(AEApplication.java:2670)
at com.tibco.ae.tools.designer.AEApplication.newDocument(AEApplication.java:2582)
at com.tibco.ae.tools.designer.AEApplication.newEmptyDocument(AEApplication.java:2 908)
at com.tibco.ae.tools.designer.actions.NewEmptyDocumentAction.performAction(NewEmp tyDocumentAction.java:38)
at com.tibco.ae.designerapi.actions.GenericDesignerAction.actionPerformed(GenericD esignerAction.java:300)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.ja va:236)
at java.awt.Component.processMouseEvent(Component.java:5517)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3135)
at java.awt.Component.processEvent(Component.java:5282)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3984)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3819)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1791)
at java.awt.Component.dispatchEvent(Component.java:3819)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java: 242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:16 3)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

 With this error you cannot create an empty project and also you can't browse the recently opened projects in TIBCO Designer startup window.

Solution: The solution for this type of error is to delete Designer preferences file and refresh. Now restart the tibco designer. The issue will be solved.

Designer preference file location: C:\Documents and Settings\<user>\.TIBCO\Designer5.prefs

Read More

Timeout waiting for correct number of process responses - issues related to TIBCO Iprocess

Timeout waiting for correct number of process responses Solution: 

When you handle this situation while starting tibco iprocess engine. check the status of ipengine by entering the command in command prompt

Go to start->Run->cmd
and enter
now type:
cd\
and go to this path
c:\swserver\staffw_nod1\util\swadm show_processes

If any of your process status is shutting down then type this below command and it will start the process which was been shutdowned
c:\swserver\staffw_nod1\util\swsvrmgr START MachineID SPO  

If still it hasn't started, Restart your system and start the command prompt 

c:\swserver\staffw_nod1\bin\swstart -p 
Now it will start all the processes, like this. 

Note: staffw_nod1 is the node cluster under which you have installed the iprocess engine. if this doesn't match your node cluster change the path to your node cluster. 

This could happen when the iprocess engine was terminated unexpectedly (power failure) or if you failed to stop the ipengine before shuting down your windows.

Read More

Soap Send Fault Activity

The SOAP Send Fault activity sends a SOAP fault to the client if an error occurs during processing of a SOAP request. This activity is used when the SOAP Event Source process starter handles incoming SOAP requests. The WSDL file for the request can have one or more fault messages defined for an operation. The SOAP Send Fault activity can use the fault schema to send application-specific data about the fault back to the client that made the SOAP request. This activity cannot be used if the SOAP request is one way. SOAP faults are required to send the fault code and the fault string. These values are required input items on the Input tab. For example, "Client" can be used for client faults and "Server" can be used for server faults. See the SOAP specification at www.w3.org/TR/SOAP for more information about the syntax of SOAP fault codes.

Read More

Soap Request Reply Activity

The SOAP Request Reply activity performs a request on the specified web service and optionally expects a reply from the web service. You can invoke both document and RPC web services with this activity.

Read More

Soap Event Source Activity

The SOAP Event Source process starter creates a process instance for incoming SOAP requests. SOAP is a standard protocol for invoking web services. This allows you to create a web service using process definitions. At runtime, a client can retrieve the WSDL file for a process containing this process starter using an HTTP request. Once the WSDL file is retrieved, the client can perform a SOAP request to invoke the web service.

Read More