WSO2 API Manager Overview

WSO2 API Manager 

As its name suggests, API Manager helps to manage exiting APIs for any service provider. It provides a common platform to search APIs with there details, It also provides mechanism to provide restricted and monitored accessibility for APIs to prospective and existing clients for any service provider.

Please find more details from my another blog from the below given link:

https://bhajanmehtablog.wordpress.com/2016/10/01/WSO2-API-Manager/

WSO2 API Manager Overview

WSO2 API Manager 

As its name suggests, API Manager helps to manage exiting APIs for any service provider. It provides a common platform to search APIs with there details, It also provides mechanism to provide restricted and monitored accessibility for APIs to prospective and existing clients for any service provider.

Please find more details from my another blog from the below given link:

https://bhajanmehtablog.wordpress.com/2016/10/01/WSO2-API-Manager/

WSO2 ESB Start-up Issue : Failed to retrieving resource from /. Table "REG_PATH" not found; SQL statement: SELECT REG_PATH_ID FROM REG_PATH WHERE REG_PATH_VALUE=? AND REG_TENANT_ID=?

TID: [-1234] [] [2016-02-02 13:10:15,774] ERROR {org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache} - Failed to retrieving resource from /. Table "REG_PATH" not found; SQL statement: SELECT REG_PATH_ID FROM REG_PATH WHERE REG_PATH_VALUE=? AND REG_TENANT_ID=? [42102-140] {org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache} org.h2.jdbc.JdbcSQLException: Table "REG_PATH" not found; SQL statement: SELECT REG_PATH_ID FROM REG_PATH WHERE REG_PATH_VALUE=? AND REG_TENANT_ID=? [42102-140] at org.h2.message.DbException.getJdbcSQLException(DbException.java:327) at org.h2.message.DbException.get(DbException.java:167) at org.h2.message.DbException.get(DbException.java:144) at org.h2.command.Parser.readTableOrView(Parser.java:4498) at org.h2.command.Parser.readTableFilter(Parser.java:1011) at org.h2.command.Parser.parseSelectSimpleFromPart(Parser.java:1577) at org.h2.command.Parser.parseSelectSimple(Parser.java:1682) at org.h2.command.Parser.parseSelectSub(Parser.java:1571) at org.h2.command.Parser.parseSelectUnion(Parser.java:1416) at org.h2.command.Parser.parseSelect(Parser.java:1404) at org.h2.command.Parser.parsePrepared(Parser.java:392) at org.h2.command.Parser.parse(Parser.java:275) at org.h2.command.Parser.parse(Parser.java:247) at org.h2.command.Parser.prepare(Parser.java:201) at org.h2.command.Parser.prepareCommand(Parser.java:214) at org.h2.engine.Session.prepareLocal(Session.java:434) :::: :::: ::: :::

Solution: Re-Start ESB with Dsetup options:

1. Stop ESB :  /bin/wso2server.sh stop
2. Start ESB with -Dsetup option: /bin/wso2server.sh start -Dsetup

Not able to import WSDL file in WSO2 Governance Registry Project

When you are trying to add/import WSDL into WSO2 Registry Project and you are facing issue then there could be many reasons, but one trick worked for me.

Issue: Not able to import WSDL in WSO2 Registry Project

Solution: Open the WSDL file and check for the encoding statement (first line). If that exists then remove that statement (and also if there is any empty line). Make sure that definitions element is the first line in the WSDL you want to import.

Issue Found with IDE: WSO2 Developer Studio (Version 3.8.0)

ActiveVOS BPEL Simulation

ActiveVOS Designer also provides simulation facility. This is very useful feature of this IDE. Simulation helps us for unit testing of single BPEL process without invoking other partner services (Those services that are invoked by BPEL).

How can we simulate?

1. Create BPEL process.
2. Create Sample files for the request or response for the activities wherever we are expecting input from the out-side of BPEL process. Mostly we needs sample files at the receive activity or for the response of any invoke activity.
   
3. Go to Run menu and choose Simulate Process. Press F5 to move step by step or F8 to complete simulation in one shot.

Can we check intermediate data during simulation?

Yes, we can. When we simulate the BPEL process then we can also check current value of any variable at any time. Some times, You may see "value not initialized" as value of any variable. It means simulation is not reached to the point where this particular value supposed to be updated (at first time).

How?

1. Make sure that you project doesn't have any error (compile time error).
   
2. Make sure that Process Variables window is open. If it is not visible then please click on the Windows Menu and then choose show views-> Process Variables.
3. Start simulation.
4. Double click on any variable (whose value you want to see).
5. A new window will open for that particular element in the same window, if it is already not opened.
   
6. If it is complex type element expand that variable otherwise you should be able to see its value there only.
7. If you are not able to see its value in last step, then right click on the variable and choose view data rather then view definition.
8. If you want to change value of any particular value during simulation then you can double click on that variable or at any particular element, in case of if it is complex. One pop-up box will come out with its current value then you can change its value. It is very useful during unit testing.
   

PS: Once you complete simulation, then (best practice says) you should click on the Clear Execution State in Run Menu, before starting simulation again.

Bypass wait/any activity at run time - ActiveVOS BPEL

Some time we may need to use wait activity (to wait BPEL process for some specific time) as per business requirement. This waiting time can be in mins, hours, days or even in years. But during testing it is not feasible that you wait for hours, days or months. ActiveVOS BPM allows you to bypass this particular activity.

How?

1. Login into the activeVOS BPEL Console.
2. Click on Monitor and then on the Active Processes links. These link will be visible on the left side of the screen.
3. Select process instance
4. Go to wait activity (it will be visible as clock). Select this activity.
   
5. You can see suspend button on the left of the screen. (Two bold parallel lines in Green-Yellow colour, tool tip message will be Suspend). Click on that. Now suspend button should be disabled and resume button should be enabled (Just in right of suspend button).
   
6. Now you should be able to see action list in the upper-right side of lower window. (Now if you still stick to you decision of by passing this activity go to next step otherwise go to 8th point. ... :) )
   
7. There should be 3 buttons, first two should be disabled and 3rd one (complete button) should be enabled. Click on this.
8. Click on the resume button.

Now you can see that process has been by passed that wait activity.

Note:

• Similarly, you can by pass ANY OTHER activity also.
• This is working fine for activeVOS BPM 6.2, hope it will also work for other versions.
  

ActiveVOS Assignment

If your BPEL process is giving some problem in the assignment. Then you need to check that all the assignments are in the proper sequence.
Suppose there is one request (say employeeDetails) expecting employee information in the following sequence (suppose this sequence is defined in the xsd):

• name
• age
• salary
• company
• DOB

Suppose you are doing assignment operation in assign activity like this:

• name
• salary (age is expected here)
  
• age
  
• company
• DOB

PS: this problem will come only if all the above listed elements are defined in the sequence.

Now in assign activity, if you are not following sequence, then you will get run time fault at that assignment.

Solution:
You can select any assignment the click on the up/down button to make proper assignment.