Forum Stats

  • 3,816,042 Users
  • 2,259,133 Discussions
  • 7,893,368 Comments

Discussions

After ReDeploy/Deploy Auto Change URI of Task on Soa Server Issue

Jack Issac
Jack Issac Member Posts: 78 Blue Ribbon
edited Jan 18, 2017 3:05AM in SOA & Process Management

Hi,

I am using

JDeveloper 11.1.1.9

BPM Editor 11.1.1.9.0.1.7

Java 1.6.0_45

SOA Composite Editor 11.1.1.9.0.99.99

I have a bpm project. it has two different version on soa server.

For example:

first project version is 1.0

second project version is 2.0

I deployed first project to soa server and uri of this project version are like this : /workflow/v1.0/...................... on soa server

After I deploying second project (v2.0), this project tasks uri are /workflow/v2.0/......................  on soa server

After these deploys, I am checking first project (v1.0)  again and this project version uri of tasks changed like this /workflow/v2.0/.... 

I mean uri of tasks changing when what I deployed latest same project.

Why uri of tasks changing, when I deployed a new version of bpm project?

Thanks.

Jack.

Tagged:
DurgadasHaldar

Best Answer

Answers

  • DurgadasHaldar
    DurgadasHaldar Member Posts: 199
    edited Jan 16, 2017 6:44AM

    That's how it is .

    Every UI Project has a file called hwtaskflow.xml which has an attribute called "TaskDefinitionNamespace"

    so whenever a UI project is deployed, it goes to SOA-infra, finds out al the Human Tasks with same Name space and changes URI

    Its a good feature from my prespective as when you have many versions and a new UI, it reflects on all HTs.

    Jack Issac
  • Jack Issac
    Jack Issac Member Posts: 78 Blue Ribbon
    edited Jan 16, 2017 8:34AM

    Hi @DurgadasHaldar,

    Thanks for your answer.

    I understood what you mean. So is there a way keep same uri without changing for it version of project

    Because, I changed java class in adf project of bpm application. So new version workig different and if my users open old process instance with new uri, so they gets error.

    All after deploy, I am changing uri for old version from soa server. In this way, old instance working with old uri, new version instance working with new uri.

    I guess, I shouldn't change TaskDefinitionNamespace, or if I can change, how can do it?

    Jack.

  • DurgadasHaldar
    DurgadasHaldar Member Posts: 199
    edited Jan 17, 2017 7:15AM Answer ✓

    Pls dont change namespace.that ll meed lot of changes.

    I would suggest going to EM post new deployment and change URI back to older one.

    Sent from my iPhone

  • Jack Issac
    Jack Issac Member Posts: 78 Blue Ribbon
    edited Jan 18, 2017 3:05AM

    Hi,

    Yes, you right.

    I guess there isn't another way to solve this issue.

    Thanks for helping @DurgadasHaldar.

    Jack

    DurgadasHaldar
This discussion has been closed.