It depends on the things you do with your process. E.g if you dont have any swimlanes in your process the database table isnt affected by this.
And you have to add users to your database manually. Thats how i did it or you can use the identity.xml. As a result u have one user you could assign a swimlane to this user and than deploy it. Afterwards there should be at least one row at the swimlane table.
Thanks for your reply.
As you said we added users manually to the Jbpm_users table, then we assigned swimlanes to the user and deployed.Now the swimlane table has some records.
But JBPM_ID_group and JBPm_ID_Membership tables are not getting populated.What is the objective of the above two tables.
thats the thing i didnt know,too. But i could imagine that u can add users to different groups and memberships, so they have special rights for the process execution like administrator etc. But i didnt work it out yet. I have several other problems ;-).
JBPM_ID_GROUP and JBPM_ID_MEMBERSHIP are part of the optional identity component that comes with jBPM. It is used to model your organisation. This info can then be used to assign task and swimlanes.