Friday, January 7, 2011

ABPP 0022 Deployment

1. Select "Prepare For Deplyment"


2. Enter locations

3. Making deployment file



4. You can distribute "deploy.jar" to customer

ABPP 0017 User Authorization

1. Creaate new user activity file


2. Create new user activity, ex) seller_activity


3. Post "updateActivityInDB" method.


4. Map "role" and "activity" using "ROLE_TEMPLATE" table.


5. You can control authority for each workflow.


6. You can control authority for each screen component.

ABPP 0016 User Authentication

1. Import archived service "USER_SECURITY"


2. Select "Archived Service"

3. Select "USER_SECURITY"


4. Generate incremental schema by solution setup.



5. Create user profile data in ../data/user_data.xml

<REQUESTS ServiceName="USER_SECURITY">
 <REQUEST Name="addRole">
  <ID Value="BUYER"/>
  <NAME Value="BUYER"/>
 </REQUEST>
 <REQUEST Name="addRole">
  <ID Value="SELLER"/>
  <NAME Value="SELLER"/>
 </REQUEST>

 <REQUEST Name="addUserGroup">
  <ID Value="BOOKSTORE_BUYER_UGP"/>
  <GRP_NAME Value="BOOKSTORE_BUYER"/>
  <ORG_ID Value="ORG_1"/>
  <GRP_TYPE Value="ENTERPRISE"/>
  <DESC Value="Bookstore Buyer User Group"/>
  <AUTO_ACTIVATE Value="true"/>
  <ASSIGN_ROLE_TEMPLATES>
   <ROLE_TEMPLATE Value="BUYER"/>
  </ASSIGN_ROLE_TEMPLATES>
 </REQUEST>  

  <REQUEST Name="addUserGroup">
  <ID Value="BOOKSTORE_SELLER_UGP"/>
  <GRP_NAME Value="BOOKSTORE_SELLER"/>
  <ORG_ID Value="ORG_1"/>
  <GRP_TYPE Value="ENTERPRISE"/>
  <DESC Value="Bookstore Seller User Group"/>
  <AUTO_ACTIVATE Value="true"/>
  <ASSIGN_ROLE_TEMPLATES>
   <ROLE_TEMPLATE Value="SELLER"/>
  </ASSIGN_ROLE_TEMPLATES>
 </REQUEST>

<ADD_DOCUMENT Name="USER_PROFILE">
  <ID Value="buyer1"/>
  <LOGIN_NAME Value="buyer1"/>
  <PASSWORD Value="pw"/>
  <ORG_ID Value="ORG_1"/>
  <CONTACT_ID Value="ct-1"/>
  <LOCALE Value="en_US"/>
  <USER_GRP_ID Value="BOOKSTORE_BUYER_UGP"/>          
 </ADD_DOCUMENT> 

<ADD_DOCUMENT Name="USER_PROFILE">
  <ID Value="seller1"/>
  <LOGIN_NAME Value="seller1"/>
  <PASSWORD Value="pw"/>
  <ORG_ID Value="ORG_1"/>
  <CONTACT_ID Value="ct-1"/>
  <LOCALE Value="en_US"/>
  <USER_GRP_ID Value="BOOKSTORE_SELLER_UGP"/>          
 </ADD_DOCUMENT>

</REQUESTS>


6. Load user profile data


7. edit xserver.xml


8. "User Authentication" is on.

Wednesday, January 5, 2011

ABPP 0014 creating simple UI node for "creating new order"

1.

2.

3.

4.

view.x2ps vs start.x2ps

There are two reserved actions with respect to workflow interaction.
- view.x2ps: This is for invoking a continue workflow action wherein the
control goes to the post processing section of the current UI node. In our case
we are specifying view.x2ps so that our workflow would continue from this
UI node to go to the' add book from catalog' screen; control will then return to
this UI node for further actions.
- start.x2ps: This is for starting a new workflow. This needs two extra
parameters, workflow name and the service name which holds that workflow

Tuesday, January 4, 2011

ABPP 0013 executing debugging

1. Click set debugger.

2. Set debug breaking point.

3.When you meet breaking point in your browser, debuggin window will pop up authmatically.

4. You cau see variable's value.

ABPP 0012 making simple UI with table editor

1. add a new workflow "wf_select_book.xml"

2. Edti new table editor's properties
name : te_1
description : te_1
service : SVC_STORE
table name : BOOK_MASTER
Model : SELECT
select property : BOOK_ID
is multi selected : Yes
assign selecttion : xml_book_selected

[Edit Next Nodes Tab]
output var : xml_output
output type : xml

3. Edit done properties.
name : dn_1
node input : xml_book_selected
type : xml
action : ...

4. Right-click in white background, and "click add to navigation"

5. You can see new workflow in menu.