The managePolicyStore operation was added in Weblogic Plugin version 4.0.3.30. It creates Application Roles and adds members to them based on one or more properties files. Each file describes the application roles and members of one application stripe. No roles or members will be deleted by the operation. Missing roles and members will be created.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
| Oracle Weblogic Home (WL_HOME) |
| Yes | WebLogic Home Directory. (e.g. /u01/oracle/products/fmw/wlserver) |
| Weblogic Admin Listen Address |
| Yes | The listener address of the WLS admin server. (e.g. localhost) |
| Weblogic Admin Listen Port |
| Yes | The port of the WLS admin server. (e.g. 7001) |
| Weblogic Admin SSL Connection |
| No | Indicates whether the admin server is using SSL. |
| Weblogic Admin User |
| Yes | The user name for the WLS admin server. |
| Weblogic Admin Password |
| Yes | The password for |
| Oracle Middleware Home (MW_HOME) |
| Yes | The oracle middleware home (which has subfolders such as oracle_common, wlsserver_10.3, coherence*, etc.). |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| Properties File Path | FILE_PATH_TO_PROPERTIES | No | Path to the OPSS properties file or folders. If relative paths are given, paths inside of the |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation consumes artifacts from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the environment instance which have resource type of WLS Admin Server.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one. It is expected that there be only one WLS Admin Server for the domain.
Property File Explanation
The properties file has specific formatting requirements so that the tool can read it. Please follow these standards:
1 - Include a line like ApplicationRoleListlike ApplicationRoleList=roleToCreate,roleToCreate2,roleToCreate3...
2 - Include a line for each of the roles that you are creating:
roleToCreate1.members=membertype1:member1,memberType2:member2,memberType3:member3...
Valid values for memberType are: APP_ROLE, ENT_ROLE, CUSTOM.
| Code Block | ||
|---|---|---|
| ||
#The next line is required. It lists the application roles to create. Each one must have a matching role.members line in the file as well. ApplicationRoleList=BI_Finance_Managers, BI_Finance_Users, BI_HumanResources, BI_Intranet_Users # Roles will be managed for the indicated application # One file for each application stripe is needed appStripe=obi #Roles are designated with their type and the role name. #Valid role types are CUSTOM, APP_ROLE, and ENT_ROLE. BI_Finance_Managers.members=CUSTOM:authenticated-role,ENT_ROLE:BIConsumers,ENT_ROLE:BIConsumers,ENT_ROLE:BIConsumers,ENT_ROLE:BIConsumers,ENT_ROLE:BIConsumers BI_Finance_Users.members=APP_ROLE:BI_Finance_Managers, APP_ROLE:BI_HumanResources,ENT_ROLE:BIConsumers # Application Role mapped to Enterprise Role as well as Application Roles BI_HumanResources.members=ENT_ROLE:BIConsumers,APP_ROLE:BI_Finance_Managers,APP_ROLE:BI_Finance_Users # Application Role mapped to Authenticated Role and Enterprise Role BI_Intranet_Users.members=APP_ROLE:BI_Finance_Managers,APP_ROLE:BI_Finance_Users, APP_ROLE:BI_Finance_Managers,ENT_ROLE:BIConsumers |
...