All geek questions in one place

Studio wso2 carbon: loading a class pick in an ESB

What is the fastest way to deploy the Mediator class on an ESB?

I have my own custom intermediary in eclipse and every time I extract the project as a JAR file and put it in "ESB \ repository \ components \ lib", but it does not commit the changes every time ...

it looks like the ESB is still using the old version of my user intermediary.

Please suggest

EDIT : also for deploying the latest version. I need to delete all files in the dropins folder

+1
source share
3 answers

The fastest way I would suggest (with Developer Studio 2.0.1):

  • Create a reseller project
  • Create a carbon project and incorporate the pick project into the C-App project as a C-App artifact
  • Export the C-App project and get the CAR file
  • Expand the CAR file in the Deplopyment C-App folder (/ repository / deployment / server / carbonapps)

** No need to restart the Server or delete existing Jars in the location of the / lib components or components / folders

The fastest way I would suggest (with Carbon Studio 1.0.14):

  • Export "Carbon Application Project" as CAR
  • enter CAR in / repository / deployment / server / carbonapps

** No need to restart the Server or delete existing Jars in the location of the / lib components or components / folders

** When you upgrade an existing mediator, replace the existing CAR file at the location of the C-App D-application with a new CAR and restart the server

Harshana

+3
source

You can create your own mediator project using Developer Studio (formerly called carbon studio), and then include the mediator logic in the mediator project of this class [1]. Then create a C-App project in Developer Studio, which includes the Class pick as an artifact of the C-App [2].

After exporting this C-App project, you will receive a CAR file that contains your class proxy [3]. After you deploy this CAR file to the ESB, it automatically deploys the OSGi package of the class broker to the ESB, and you can immediately use the class broker.

When you update the class broker logic, you can re-export the C-App project and simply replace the existing CAR file in the ESB with a new CAR file. Then your previous OSGi class broker package will be removed from the ESB. But due to a limitation in the implementation of Equinox OSGi, you cannot use the new version of the class broker until the server restarts.

So all you have to do is replace the existing CAR file with the new version of the CAR file and restart the ESB server. The ESB server will take care of deploying the OSGi package on the system.

Since we have implemented support for deploying the C-App on Carbon Server through Eclipse [4], you can also use this approach. What you need to do is add the ESB server to the Eclipse instance and deploy the C application that contains the class proxy through Eclipse itself. When you follow this approach, you can update the logic in the class proxy and reinstall the new version of the CAR file on the server via Eclipse [5].

You can even debug your class proxy inside Developer Studio, following the guidance in [6].

[1]. http://wso2.org/project/developer-studio/2.0.1/docs/server_extensions_category.html#CustomMediator

[2]. http://wso2.org/project/developer-studio/2.0.1/docs/packaging.html#Distribution

[3]. http://wso2.org/project/developer-studio/2.0.1/docs/testing_deploying_category.html#CarGen

[4]. http://wso2.org/project/developer-studio/2.0.1/docs/testing_deploying_category.html#Deploy

[5]. http://wso2.org/project/developer-studio/2.0.1/docs/testing_deploying_category.html#Redeploy

[6]. http://wso2.org/project/developer-studio/2.0.1/docs/testing_deploying_category.html#debug

Hope this helps!

Harshana

+2
source

The fastest way I've found so far:

  • Export "Carbon Application Project" as JAR
  • put the jar in WSO2_ESB \ repository \ components \ lib
  • remove relative jar in WSO2_ESB \ repository \ components \ dropins
  • reboot ESB
+2
source

Source: https://habr.com/ru/post/1439756/

More articles:


All Articles