A Installing the Demo User Community in the Database

This appendix describes how to install and use the organizational hierarchy of users and groups known as the demo user community in the database. You can assign users and groups in this community to tasks that require approvals or other types of human interactions that advance the task workflow.

This appendix includes the following sections:

• Section A.1, "Installing the Demo User Community"

• Section A.2, "Demo Community Users"

• Section A.3, "Demo Community Groups"

• Section A.4, "soa-infra Application Roles"

• Section A.5, "SOATestDemoApp Application Roles"

• Section A.6, "Roles Granted to and Owned by Users"

• Section A.7, "WorkflowPermission Class"

A.1 Installing the Demo User Community

The demo user community is an organizational hierarchy of users and groups. After installing Oracle SOA Suite, you must install the demo user community in the database. The demo user community is part of the workflow-001-DemoCommunitySeedApp sample available under the HW link on the Oracle SOA Suite samples site. The README.txt file included with the sample describes both basic and advanced methods for installing the demo user community. The basic method for installing the demo user community is also described in this section.

Notes:

You must run the script for seeding the user demo community locally from within a domain, and not remotely.

To install the demo user community:

1. Ensure that you have a local installation of one of the following:

   • Oracle JDeveloper

   • Oracle BPM server

   • ant 1.7

2. Download the workflow-001-DemoCommunitySeedApp sample from the Oracle SOA Suite samples site.

3. Enter the following command to determine the version of Java on the host.

   java -version
   

   The host on which to install the demo user community into the database must include Java 1.6 update 17 or higher.

4. Ensure that your environment PATH contains the version of Java that is shipped with Oracle SOA Suite.

5. Select a method for installing the demo user community in the database.

   To Use the build.properties File...

   To Run the ant Script with Specified Parameters...

   Edit the build.properties file included in the downloaded sample to match your environment: # Set the admin server location admin.url=t3://localhost:7001 server.url=http://localhost:8001 # Set the Fusion Middleware home, also # called the bea home # Linux style /scratch/oracle/middleware # Windows style C:\\Oracle\\Middleware bea.home=/scratch/oracle/middleware/ home_betaupdate # Set the authentication admin.name=weblogic admin.pwd=password # Use the managed server for the target or # if single server configuration use the # admin server # e.g. target=soa_server1 or # target=AdminServer target=AdminServer Run the following ant command: $FMW_HOME\modules\org.apache.ant _1.7.0\bin\ant seedDemoUsers Where $FMW_HOME is the Oracle Fusion Middleware home directory for Oracle JDeveloper or SOA Server (or, specify the path to the ant 1.7 location).

   Run the ant script with specified parameters. Note that bea.home and FMW_HOME are the same ant seedDemoUsers -Dbea.home=FMW_HOME -Doracle.home=ORACLE_HOME -Ddomain.home=FMW_HOME/user_projects/ domains/Domain_Name -Dtarget=Managed_Server_Name -Dadmin.url=t3://HOST:Admin_Server_Port -Dserver.url=http://HOST:Managed_Server_Port -Dadmin.name=Admin_Name -Dadmin.pwd=Admin_Password Where FMW_HOME is the absolute path of the installation home directory and ORACLE_HOME is the absolute path of the Oracle home provided during installation. For example: ant seedDemoUsers -Dbea.home=/scratch/wls/as11wls/lt20 -Doracle.home=/scratch/wls/as11wls/lt20/ AS11gR1SOA -Ddomain.home=/scratch/wls/as11wls/lt20/ user_projects/domains/domain1 -Dtarget=soa_server1 -Dadmin.url=t3://wlserver.example.com:7001 -Dserver.url=http:///wlserver.example.com: 8001 -Dadmin.name=weblogic -Dadmin.pwd=password

   
   

This installs the demo user community and grants permissions to the demo appRoles.

If installation is successful, the following message is displayed:

Build Successful

Note:

You can receive a Build Successful message even though there were connection problems. Watch for those messages.

After the successful seeding of demo users, you can log in with jcooper, jstein, or other users with the password specified in the build.properties file.

If installation is unsuccessful, the following message is displayed:

Build Failed

Installation failure is caused by a configuration or server availability issue. Correct those problems and retry again.

A.2 Demo Community Users

Table A-1 lists the users in the demo community.

Table A-1 Users in the Demo Community

User	User Name	First Name	Last Name	Title	Manager	Email
1	achrist	Agatha	Christie	Loan Consultant	wfaulk	[e-mail]
5	cdickens	Charles	Dickens	CEO	--	[e-mail]
6	cdoyle	Conan	Doyle	Loan Agent 2	rsteven	[e-mail]
3	EHEMING	Ernest	Hemingway	CFO	JVerne	[e-mail]
7	fkafka	Franz	Kafka	Manager 1	ltolstoy	[e-mail]
8	istone	Irving	Stone	Loan Agent 2	sfitzger	[e-mail]
9	jausten	Jane	Austen	Loan Consultant	fkafka	[e-mail]
10	jcooper	James	Cooper	Loan Agent 1	jstein	[e-mail]
11	jlondon	Jack	London	Loan Agent 1	sfitzger	[e-mail]
12	jstein	John	Steinbeck	Manager 2	wfaulk	[e-mail]
2	JVerne	Jules	Verne	CIO	cdickens	[e-mail]
13	ltolstoy	Leo	Tolstoy	Director	wfaulk	[e-mail]
14	mmitch	Margaret	Mitchell	Loan Analyst	fkafka	[e-mail]
15	mtwain	Mark	Twain	Loan Agent 2	jstein	[e-mail]
16	rsteven	Robert	Stevenson	Manager 3	jstein	[e-mail]
17	sfitzger	Scott	Fitzgerald	Manager 1	wfaulk	[e-mail]
18	szweig	Stefan	Zweig	Loan Analyst	fkafka	[e-mail]
4	VHUGO	Victor	Hugo	HR Manager	EHEMING	[e-mail]
19	wfaulk	William	Faulkner	Vice President	cdickens	[e-mail]
20	wshake	William	Shakespeare	Manager 3	rsteven	[e-mail]

Figure A-1 shows the organizational hierarchy of the demo community.

Figure A-1 Demo Community Organizational Hierarchy

Description of "Figure A-1 Demo Community Organizational Hierarchy"

A.3 Demo Community Groups

Table A-2 lists the following:

• Groups in the demo community

• Users and groups that are granted each group role (direct grantees and all grantees)

• Group roles and application roles granted to each group (direct-granted roles and all granted roles)

See Table A-6 for the roles granted to users sorted by user.

Table A-2 Groups in the Demo Community: Grant Relationships

Group	Direct Grantees	All Grantees	Direct-Granted Roles	All Granted Roles
RegionalOffices	CentralRegion, WesternRegion, EasternRegion	szweig, wshake, jcooper, WesternRegion, mmitch, EasternRegion, jlondon, CentralRegion, istone, cdoyle, mtwain, California, fkafka	-	-
EasternRegion	szweig, wshake, mmitch, fkafka	szweig, wshake, mmitch, fkafka	RegionalOffices	RegionalOffices
CentralRegion	jlondon, mtwain	jlondon, mtwain	RegionalOffices	RegionalOffices
WesternRegion	cdoyle, California	jcooper, istone, cdoyle, California	RegionalOffices	RegionalOffices
California	jcooper, istone	jcooper, istone	WesternRegion	RegionalOffices, WesternRegion
LoanAgentGroup	jlondon, wshake, LoanAnalyticGroup, jcooper, istone, cdoyle, mtwain	szweig, jlondon, wshake, LoanAnalyticGroup, jcooper, istone, cdoyle, mtwain, mmitch, fkafka	-	-
LoanAnalyticGroup	szweig, mmitch, fkafka	szweig, mmitch, fkafka	BPMWorkflowCustomize, LoanAgentGroup	BPMWorkflowCustomize, LoanAgentGroup
Supervisor	jcooper, mtwain, rsteven	jcooper, mtwain, rsteven	-	-
Executives	cdickens, JVerne, EHEMING, VHUGO	cdickens, JVerne, EHEMING, VHUGO	-	-

Table A-3 shows information for several groups listed in Table A-2. It lists the following:

• Users and groups (direct owners and all owners) that own each group

• Group roles (direct-owned roles and all owned roles) that each group owns

See Table A-6 for the roles owned by users sorted by user.

Table A-3 Groups in the Demo Community: Ownership Relationships

Group	Direct Owners	All Owners	Direct Owned Roles	All Owned Roles
EasternRegion	jstein	jstein	-	-
WesternRegion	jstein	jstein	-	-
California	fkafka	fkafka	-	-
LoanAgentGroup	jcooper, fkafka	jcooper, fkafka	-	-
LoanAnalyticGroup	jstein	jstein	-	-
Supervisor	jstein	jstein	-	-

A.4 soa-infra Application Roles

Table A-4 lists the following:

• soa-infra application roles

• Users, groups, and roles that are granted each application role (direct grantees and all grantees)

• Roles granted to each application role (direct-granted roles and all granted roles)

See Table A-6 for the application roles granted to users sorted by user.

Table A-4 Application Roles in soa-infra

Application Role	Direct Grantees	All Grantees	Direct-Granted Roles	All Granted Roles
SOAAdmin	Administrators	Administrators	BPMWorkflowAdmin	BPMWorkflowCustomize BPMWorkflowAdmin
BPMWorkflowAdmin	SOAAdmin, demoadmin	SOAAdmin, demoadmin, Administrators	BPMWorkflowCustomize	BPMWorkflowCustomize
BPMWorkflowCustomize	LoanAnalyticGroup, BPMWorkflowAdmin	szweig, LoanAnalyticGroup, SOAAdmin, BPMWorkflowAdmin, mmitch, fkafka, Administrators, demoadmin	-	-

For more information about application roles, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

A.5 SOATestDemoApp Application Roles

Table A-5 lists the roles in the SOATestDemoApp application.

Table A-5 SOATestDemoApp Roles

Application Role	Direct Grantees	All Grantees	Direct-Granted Roles	All Granted Roles
DevTeam	rsteven	rsteven, mmitch, fkafka, jcooper, istone
QATeam	jlondon, Supervisor	jlondon, jcooper, mtwain, rsteven, mmitch, fkafka, istone
ProductionTeam	mmitch, fkafka, California	mmitch, fkafka, jcooper, istone	DevTeam, QATeam	DevTeam, QATeam

A.6 Roles Granted to and Owned by Users

Table A-6 lists the following:

• Roles granted to each user (direct-granted roles and all granted roles)

• Roles owned by each user (direct-owned roles and all owned roles)

Table A-6 Roles for Each User

User Name	Direct-Granted Roles	All Granted Roles	Direct-Owned Roles	All Owned Roles
achrist	Executives	-	-	-
cdickens	-	-	Executives	-
cdoyle	WesternRegion, LoanAgentGroup	RegionalOffices, WesternRegion, LoanAgentGroup	-	-
EHEMING		Executives
fkafka	LoanAnalyticGroup, EasternRegion, ProductionTeam	BPMWorkflowCustomize, RegionalOffices, LoanAnalyticGroup, LoanAgentGroup, EasternRegion, ProductionTeam, DevTeam, QATeam	LoanAgentGroup, California	LoanAgentGroup, California
istone	LoanAgentGroup, California	RegionalOffices, WesternRegion, LoanAgentGroup, California, DevTeam, QATeam, ProductionTeam	-	-
jausten	-	-	-	-
jcooper	Supervisor, LoanAgentGroup, California	RegionalOffices, WesternRegion, Supervisor, LoanAgentGroup, California, DevTeam, QATeam, ProductionTeam	LoanAgentGroup	LoanAgentGroup
jlondon	CentralRegion, LoanAgentGroup, QATeam	CentralRegion, RegionalOffices, LoanAgentGroup, QATeam	-	-
jstein	-	-	LoanAnalyticGroup WesternRegion, Supervisor, EasternRegion	LoanAnalyticGroup WesternRegion, Supervisor, EasternRegion
JVerne		Executives
ltolstoy	-	-	-	-
mmitch	LoanAnalyticGroup, EasternRegion, ProductionTeam	BPMWorkflowCustomize RegionalOffices, LoanAnalyticGroup, LoanAgentGroup, EasternRegion, DevTeam, QATeam, ProductionTeam	-	-
mtwain	CentralRegion, Supervisor, LoanAgentGroup	CentralRegion, RegionalOffices, Supervisor, LoanAgentGroup, QATeam	-	-
rsteven	Supervisor, DevTeam	Supervisor, DevTeam	-	-
sfitzger	-	-	-	-
szweig	LoanAnalyticGroup, EasternRegion	BPMWorkflowCustomizeDemoApp/FlexFieldRole, RegionalOffices, LoanAnalyticGroup, LoanAgentGroup, EasternRegion
vhugo		Executives
wfaulk	-	-	-	-
wshake	LoanAgentGroup, EasternRegion	RegionalOffices, LoanAgentGroup, EasternRegion	-	-

A.7 WorkflowPermission Class

Table A-7 lists the permissions defined in the WorkflowPermission class and the application roles associated with each permission.

Table A-7 WorkflowPermission Class

Permission	Application Role with Permission
workflow.mapping.publicFlexField	BPMWorkflowAdmin, BPMWorkflowCustomize
workflow.mapping.protectedFlexField	BPMWorkflowAdmin
workflow.admin	BPMWorkflowAdmin
workflow.admin.evidenceStore	BPMWorkflowAdmin