Petals ESB CLI

Add a command to BC JBI Gateway re-propagate endpoints

Details

  • Type: New Feature New Feature
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.2.0
  • Fix Version/s: 2.3.0
  • Component/s: Extension 'BC Gateway'
  • Security Level: Public
  • Description:
    Hide

    Create a command to BC JBI gateway to re-propagate endpoints:

    bc-gateway.repropagate [-n <component-id>] [-u <service-unit-id> [-c <consumer-domain-id>]]

    where:

    • component-id is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used),
    • service-unit-id is the JBI identifier of BC JBI Gateway Service Unit,
    • and consumer-domain-id is the identifier of a consumer domain declared in the previously specified service unit.

    This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway.

    Show
    Create a command to BC JBI gateway to re-propagate endpoints: 
    bc-gateway.repropagate [-n <component-id>] [-u <service-unit-id> [-c <consumer-domain-id>]]
    where:
    • component-id is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used),
    • service-unit-id is the JBI identifier of BC JBI Gateway Service Unit,
    • and consumer-domain-id is the identifier of a consumer domain declared in the previously specified service unit.
    This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway.
  • Environment:
    -

Issue Links

Depends
 

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Thu, 17 Mar 2016 - 10:55:54 +0100
Field Original Value New Value
Link This issue depends on PETALSBCJBI-2 [ PETALSBCJBI-2 ]
Christophe DENEUX made changes - Thu, 17 Mar 2016 - 10:56:12 +0100
Fix Version/s 2.3.0 [ 10605 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Thu, 17 Mar 2016 - 10:59:59 +0100
Description Create a command to BC JBI gateway: to re-propagate endpoints. This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway. Create a command to BC JBI gateway to re-propagate endpoints: {{bc-gateway.repropagate [-n <component-id>]}}, where {{component-id}} is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used).

This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway.
Christophe DENEUX made changes - Thu, 17 Mar 2016 - 11:00:20 +0100
Description Create a command to BC JBI gateway to re-propagate endpoints: {{bc-gateway.repropagate [-n <component-id>]}}, where {{component-id}} is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used).

This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway. 		Create a command to BC JBI gateway to re-propagate endpoints: {{bc-gateway.repropagate \[-n <component-id>\]}}, where {{component-id}} is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used).

This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway.
Christophe DENEUX made changes - Sat, 26 Mar 2016 - 13:56:59 +0100
Status New [ 10000 ] Open [ 10002 ]
Christophe DENEUX made changes - Sat, 26 Mar 2016 - 13:57:04 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Permalink
Christophe DENEUX added a comment - Sat, 26 Mar 2016 - 15:18:22 +0100

Added in trunk

Show
Christophe DENEUX added a comment - Sat, 26 Mar 2016 - 15:18:22 +0100 Added in trunk
Christophe DENEUX made changes - Sat, 26 Mar 2016 - 15:18:22 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Hide
Permalink
Christophe DENEUX added a comment - Sat, 26 Mar 2016 - 15:34:37 +0100

User doc added

Show
Christophe DENEUX added a comment - Sat, 26 Mar 2016 - 15:34:37 +0100 User doc added
Hide
Permalink
Victor NOËL added a comment - Tue, 17 May 2016 - 16:15:44 +0200

Reopen to add command parameter to only reload an SU or a consumer domain.

Show
Victor NOËL added a comment - Tue, 17 May 2016 - 16:15:44 +0200 Reopen to add command parameter to only reload an SU or a consumer domain.
Victor NOËL made changes - Tue, 17 May 2016 - 16:15:44 +0200
Status Resolved [ 10004 ] Open [ 10002 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Resolution Fixed [ 1 ]
Victor NOËL made changes - Tue, 17 May 2016 - 16:18:02 +0200
Description Create a command to BC JBI gateway to re-propagate endpoints: {{bc-gateway.repropagate \[-n <component-id>\]}}, where {{component-id}} is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used).

This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway. 		Create a command to BC JBI gateway to re-propagate endpoints: {{bc-gateway.repropagate \[-n <component-id>\] \[-u <service-unit-id> \[-c <consumer-domain-id>\]\]}}, where {{component-id}} is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used), {{service-unit-id}} is the JBI identifier of BC JBI Gateway Service Unit and {{consumer-domain-id}} is the identifier of a consumer domain declared in the previously specified service unit.

This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway.
Victor NOËL made changes - Tue, 17 May 2016 - 16:18:13 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Tue, 17 May 2016 - 17:03:59 +0200
Description Create a command to BC JBI gateway to re-propagate endpoints: {{bc-gateway.repropagate \[-n <component-id>\] \[-u <service-unit-id> \[-c <consumer-domain-id>\]\]}}, where {{component-id}} is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used), {{service-unit-id}} is the JBI identifier of BC JBI Gateway Service Unit and {{consumer-domain-id}} is the identifier of a consumer domain declared in the previously specified service unit.

This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway. 		Create a command to BC JBI gateway to re-propagate endpoints:
{code}
bc-gateway.repropagate [-n <component-id>] [-u <service-unit-id> [-c <consumer-domain-id>]]
{code}
where:
* {{component-id}} is the JBI identifier of a BC JBI Gateway (if not set, the default identifier 'petals-bc-jbi-gateway' is used),
* {{service-unit-id}} is the JBI identifier of BC JBI Gateway Service Unit,
* and {{consumer-domain-id}} is the identifier of a consumer domain declared in the previously specified service unit.

This command could be used to propagate endpoint of service providers deployed after the consume part of the JBI gateway.
Hide
Permalink
Christophe DENEUX added a comment - Tue, 17 May 2016 - 17:05:44 +0200

Can you confirm that:

  • if no SU is set, all endpoints of all SUs are refreshed ?
  • if no consumer domain is set, all endpoints of all consumer domains of the SU are refresh ?
Show
Christophe DENEUX added a comment - Tue, 17 May 2016 - 17:05:44 +0200 Can you confirm that:
  • if no SU is set, all endpoints of all SUs are refreshed ?
  • if no consumer domain is set, all endpoints of all consumer domains of the SU are refresh ?
Hide
Permalink
Victor NOËL added a comment - Tue, 17 May 2016 - 17:07:48 +0200

Yes it works like that.

Show
Victor NOËL added a comment - Tue, 17 May 2016 - 17:07:48 +0200 Yes it works like that.
Hide
Permalink
Victor NOËL added a comment - Tue, 17 May 2016 - 17:12:55 +0200

done and documentation updated

Show
Victor NOËL added a comment - Tue, 17 May 2016 - 17:12:55 +0200 done and documentation updated
Victor NOËL made changes - Tue, 17 May 2016 - 17:12:55 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
9d 3h 2m
1
Christophe DENEUX
Sat, 26 Mar 2016 - 13:56:59 +0100
Open Open In Progress In Progress
5s
1
Christophe DENEUX
Sat, 26 Mar 2016 - 13:57:04 +0100
In Progress In Progress Resolved Resolved
1h 21m
1
Christophe DENEUX
Sat, 26 Mar 2016 - 15:18:22 +0100
Resolved Resolved Open Open
51d 23h 57m
1
Victor NOËL
Tue, 17 May 2016 - 16:15:44 +0200
Open Open In Progress In Progress
2m 29s
1
Victor NOËL
Tue, 17 May 2016 - 16:18:13 +0200
In Progress In Progress Resolved Resolved
54m 42s
1
Victor NOËL
Tue, 17 May 2016 - 17:12:55 +0200

People

Dates

  • Created:
    Thu, 17 Mar 2016 - 10:54:52 +0100
    Updated:
    Tue, 17 May 2016 - 17:12:55 +0200
    Resolved:
    Tue, 17 May 2016 - 17:12:55 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.