Dependent Application 'isv' does not exist : Resolution

Normally we encounter a error which says "Dependent Application 'isv' does not exist" while installing the isvp. A screenshot is shown below

Reason : As far as I have understood whenever your project has any UDDI services this dependency will be added by default (may be a product bug) but this can be solved by following below steps

Resolution :

Step 1 : Locate the isvp which will be in "isvcontent" folder of <<InstanceOfCordys>>

Step 2 : Right click and open the archive (I am using 7z you can also use winrar to follow this step)

Step 3 : Once you open the archive, you would be seeing isv.xml file (this is where your concentration should be) drag and drop somewhere in your hard drive (I have copied the isv.xml file in the same location where isvps are present. This is shown below)

Step 4 : Open the isv.xml file using some textpad or notepad++ (I am fortunate that its only 1MB, You have to struggle if your application is huge editing this isv.xml would be a challenge)
A view to show the text which causes this problem is shown below

You could see the highlighted portion which must be removed in order to overcome this error.
Once you remove you have to replace this isv.xml file to the same archive.

Step 5 : Over write the isv.xml into archive content (isv)

Step 6 : You can go ahead and install the isvp (You might have to close and open the Application registry not to run into problem while installing again)

Note : Write to me if anything to be added here.

One Problem of having CWS and ISVP in a single Environment

Scenario:

 This post is about the problem I have faced by having the CWS content and ISVP content only in one single environment. I have one project's CWS content and ISVP content in my local environment. Now what I did was, I have uninstalled the isvp from my local machine. The UnInstallation was successful but however both the CWS content and ISVP content in the same environment will be sharing common cordys database, while uninstalling the ISVP it removed certain content from the cordys database (Assumable its xsd related content). The process of uninstallation was successful. But now I am facing a problem from my development content. When i publish any of the newly created web service it doesn't succeed throwing the exception which is shown below,

<![CDATA[ApplicationTransaction 'com.cordys.cap.applicationconnector.Transaction' threw an exception during abort.]]></log4j:message>
<log4j:NDC><![CDATA[Running Publishing document(s)
 Publishing HealthMonitoringTool/Web Services/HealthMonitor/ESB-App/Composite/HealthMonitor.ESBApp.Composite.ESBAppCompositeWS
 Publishing HealthMonitoringTool/Web Services/HealthMonitor/ESB-App/Composite/HealthMonitor.ESBApp.Composite.ESBAppCompositeWS/ESBAppCompositeWSI
 Publishing HealthMonitoringTool/Web Services/HealthMonitor/ESB-App/Composite/HealthMonitor.ESBApp.Composite.ESBAppCompositeWS/ESBAppCompositeWSI/GetDistintOrgsFromConfiguration
 Publishing HealthMonitoringTool/Web Services/HealthMonitor/ESB-App/Composite/HealthMonitor.ESBApp.Composite.ESBAppCompositeWS/ESBAppCompositeWSI/GetDistintOrgsFromConfiguration/GetDistintOrgsFromConfigurationRealization
 Publishing HealthMonitoringTool/Ws-App Packages/HealthMonitor/HealthMonitorAppR1
 Publishing HealthMonitoringTool/Ws-App Packages/HealthMonitor/HealthMonitorAppR1/COMM_JOBRUN_WORKITEM_DETAILS.xsd
 Publishing HealthMonitoringTool/Ws-App Packages/HealthMonitor/HealthMonitorAppR1/COMM_JOBRUN_WORKITEM_DETAILS.xsd/Reference_to_00505687-00BD-11E3-E8EE-2679912CB788
 Publishing HealthMonitoringTool/Ws-App Packages/HealthMonitor/HealthMonitorAppR1/XMLSchema_Binary_Reference_WSAppServerSchema.xsd
]]

I have understood that I created a mess first by having both cws and ISVP content in one single environment and second by unInstalling isvp. I have installed the isvp again in the environment and tried publishing the newly created web service. But NO LUCK :( still I have the same issue. This issue got resolved when I restarted the cordys monitor and then tried publishing the service. 

The situation is same for any newly created web service in this scenario. Whenever I create a new web service in my local development server, in order to publish it successfully I have to restart cordys monitor and then try publishing.

Note : I could able to find the resolution, but I wasn't able to understand what exactly went wrong. People can put their thoughts on this and let me know if they have found the reason behind this by giving a clear explanation.

Rollback an Application in Cordys

Hi,

Today, we tried to RollBack an application in Cordys using "Application Registry".

Everything went fine, but when we triggered one of the BPM instances, the instance was executing using the last installed path, and not the path it was suppose to. (i.e. it was taking the version 22 path and not the version 21 path).

Anyone faced the same issue??

I am using BOP4.1CU6.

Conclusion :

It has been identified as a "Product Defect (or rather say Effect :-) )"

Cordys product team will provide a patch for the same.

--

Courtesy :

Amit Kumar DH

Transaction Object is null : Coboc Browser : Problem installing isvps which has DTs

Issues related to this:

·         Isvps related to CoBOC Content will not be installed as CoBOC browser will not be functioning properly.

·         When opening CoBOC Browser we get an error “TransactionObject is null” and in the log it will be “invalidTransactionObject”.

Possible reason:

The port number of CoBOC container is not in sync with Monitor container hence even after restart we could not solve this issue. So as a resolution we have created a clone of CoBOC container (port number will be changed automatically and it will create proper connection with Monitor service container) and stopped the main container and let the copy of coboc container in started state (assuming the algorithm the CoBOC service group is in failover mode). Then the issue has gone.