Payload Obfuscation Security Features of Oracle B2B
1.4.2 Restricting Access to Document Types
Oracle B2B supports payload security by restricting access based on document type. The following user permissions for document-type access are available: ■ Admin permission for all document types With this permission, the user can add, access, edit, and delete all document types. This user also has access to administrative functions such as import, export, and purge. ■ Admin permission for specified document types With this permission, the user can access, edit, and delete the specified document types for which he has permission. The user is not allowed to access, edit, or delete the restricted document types. The user cannot add new document types or have access to any administrative functions such as import, export, and purge. ■ Monitor permission for all document types With this permission, the user can access and view but not edit or delete all document types. ■ Monitor permission for specified document types With this permission, the user can access and view but not edit or delete the specified document types. The user cannot access and view the restricted document types. The default administrator user can restrict document-type access to other roles as follows: ■ The host administrator can be granted access to all document types, in which case this user can restrict document-type access to other host or remote administrators. ■ The host administrator can be granted access only to specified document types, in which case this user cannot restrict document-type access to other host or remote administrators. ■ The remote administrator can be granted access to specified document types only, or all document types pertaining to the remote trading partner. In either case, the remote trading partner administrator cannot create document types in the system, or provision users for that particular remote trading partner. Users can only be provisioned by a host trading partner administrator user. ■ The host monitor can be granted view-only access to all document types or to specified document types, but cannot restrict document-type access to other users. ■ The remote monitor can be granted view-only access to all document types pertaining to the remote trading partner or to specified document types pertaining Introduction to Oracle B2B 1-7 to the remote trading partner, but cannot restrict document-type access to other users. See Task 3, Add Document Types That the User Has Permission to Access in Section 5.3, Adding Trading Partner Users, for how to specify document-type access in the Oracle B2B interface. When access to specific document types is restricted, consider the following: ■ New document definitions for a restricted document type cannot be added. ■ No document types can be imported, exported, or purged. ■ No document types can be modified on the Partners Documents tab, as shown in Figure 1–1 . Figure 1–1 Accessing a Restricted Document Type from the Documents Tab The image shows that the selected document type is restricted for the logged-in user. The error message User does not have access to the document type. Selected definition cannot be accessed appears. ■ The restricted document types are listed, but details cannot be viewed or accessed, on the following tabs: – Administration Document tab – Reports tabs – Metrics tabs Note: Admin users with access to all Administration tab functions lose admin privileges when permission for any or all document types is assigned, and the Administration tab is no longer available.Parts
» Oracle Fusion Middleware Online Documentation Library
» Oracle B2B and Business-to-Business E-Commerce Protocols Supported in Oracle B2B
» Payload Obfuscation Security Features of Oracle B2B
» Restricting Access to Document Types
» What You Need to Get Started with Oracle B2B
» Log in to the console. In the Domain Structure pane, shown in
» Accessing Oracle B2B Through Single Sign-On SSO
» Administration Partners Reports Using the Oracle B2B Interface
» Creating a B2B Transaction: An Overview of the Process Flow
» If Oracle JDeveloper is running for the first time, specify the location for the Java
» Create a new SOA composite application, as described in
» On the Name your application page, you can optionally change the name and
» From the Component Palette, select SOA.
» From the Service Components list, drag a component into the designer.
» Click OK. How To Use B2B Binding Components in a SOA Composite Application
» Select Save All from the File main menu.
» Drag B2B to the Exposed Services or the External References swim lane.
» On the Operation page, select Send or Receive, as described in
» On the Document Definition Handling page, select the option on the Basic tab or
» On the Finish page, click Finish.
» Click Finish. How To Use B2B Binding Components in a SOA Composite Application
» If you selected Oracle WebLogic JMS or Oracle Advanced Queuing, then the
» If you selected Send in Step 7, then the Produce Operation Parameters page
» About Using the JMS Integration Type in the B2B Configuration Wizard
» Enabling Debug Mode at Run Time Logging Out: SSO Logout Configuration for Oracle Access Manager
» Introduction to Oracle B2B Document Editor
» Installing Oracle B2B Document Editor Creating Guideline Files: EDIFACT D98 Example
» The Document Hierarchy Introduction to Document Protocols
» Creating Document Definitions Oracle Fusion Middleware Online Documentation Library
» Deleting a Document Definition
» Introduction to Trading Partners Creating Trading Partner Profiles
» Adding Trading Partner Users
» Adding Document Definitions Oracle Fusion Middleware Online Documentation Library
» About MLLP Configuring Channels
» Message Sequencing Configuring Channels
» Using Transport Sync Callback
» Correlating Messages Using JMS Queues
» Configuring Delivery Retry Options
» Using the Auto Create Agreement Feature
» Using Identifiers for Trading Partner Lookup Scheduling Trading Partner Downtime
» Broadcasting Messages to Multiple Trading Partners
» Introduction to Agreements Oracle Fusion Middleware Online Documentation Library
» Creating an Agreement Oracle Fusion Middleware Online Documentation Library
» Deleting and Exporting Agreements
» Importing and Exporting the Design-Time Repository
» Exported ZIP Files Containing Agreement Names in Multibyte Character Languages
» How to Configure the XPath Expression for a Custom XML Document
» Using the EDI EDIFACT Document Protocol
» Using the EDI X12 Document Protocol
» Using the HL7 Document Protocol
» Using the OAG Document Protocol
» Using the Positional Flat File Document Protocol
» PIPs Using the RosettaNet Document Protocol
» Changing Document Definitions After Deploying an Agreement
» Changing Document Definitions After Importing Metadata
» Introduction to Agreement Deployment States
» Click Export. Exporting an Active Agreement
» Creating Custom Identifier Types
» Creating Custom Contact Information Types
» Creating Custom Trading Partner Parameter Types
» Managing Batched Messages Oracle Fusion Middleware Online Documentation Library
» Introduction to Scheduling Trading Partner Downtime Scheduling Trading Partner Downtime
» Deleting Scheduled Downtime Oracle Fusion Middleware Online Documentation Library
» Overlapping Schedules Extending Trading Partner Downtime
» Transport Callouts Introduction to Callouts
» Creating a Callout Oracle Fusion Middleware Online Documentation Library
» Including a Callout in an Agreement
» Implementing a Callout Oracle Fusion Middleware Online Documentation Library
» Purging Design Metadata and Instance Data
» Adding a Listening Channel and Protocol
» Using Transport Protocols Oracle Fusion Middleware Online Documentation Library
» Transport Protocol Parameters Adding Listening Channel Details
» Channel Attributes Exchange Protocol Parameters Security Parameters
» Configuring a Listening Channel Configuring Document Sequencing
» Setting Configuration Parameters Oracle Fusion Middleware Online Documentation Library
» Creating Business Message Reports
» Creating Wire Message Reports
» Creating Application Message Reports
» Creating Error Reports Oracle Fusion Middleware Online Documentation Library
» Creating Conversation Reports Oracle Fusion Middleware Online Documentation Library
» Prerequisites for Running the Command-line Tools
» Archiving Data Oracle Fusion Middleware Online Documentation Library
» Purging Data Oracle Fusion Middleware Online Documentation Library
» Importing Data Oracle Fusion Middleware Online Documentation Library
» Exporting Data Oracle Fusion Middleware Online Documentation Library
» Batching Operations Oracle Fusion Middleware Online Documentation Library
» Deploying Agreements Oracle Fusion Middleware Online Documentation Library
» Creating CPPCPA Properties Templates
» Validating B2B Metadata Verifying Agreement Availability
» Document Protocols selfservice XML files.
» Resubmitting a Message Oracle Fusion Middleware Online Documentation Library
» Scheduling Trading Partner Downtime
» Managing the Keystore Oracle Fusion Middleware Online Documentation Library
» Errors During Import Oracle Fusion Middleware Online Documentation Library
» Introduction to Oracle B2B Web Services
» Using the Outbound Web Service Using the Translation Web Service
» Is Trading Partner Agreement Setup Parameters
» Get Trading Partner Agreement Information Parameters
» Securing Oracle B2B Web Services
» Introduction to Archiving and Restoring B2B Business Messages Archiving B2B Business Messages
» Restoring B2B Business Messages
» AQ Enqueue AQ Enqueue and Dequeue Utilities
» AQ Dequeue AQ Enqueue and Dequeue Utilities
» JMS Enqueue JMS Enqueue and Dequeue Utilities
» Enqueue—Using a JMS JCA Adapter or Custom Utilities JMS Dequeue
» Using the attachmentsDescriptor.xsd
» Click New, and go to the list of JMS resources.
» Select the Foreign Server option, and click Next.
» Enter a Name for the Foreign Server for example, BAMAQForeignServer,
» Enter oracle.jms.AQjmsInitialContextFactory in the JNDI Initial
» Enter datasource=data_source_jndi_location In the JNDI Properties
» Check the Default Targeting Enabled checkbox.
» Select the Connection Factories ta
» Enter QueueConnectionFactory in the Remote JNDI Name field. Click OK.
» Mapping Oracle B2B Instance Messages to Oracle BAM Data Objects
» Creating a Dashboard to Monitor Oracle B2B
» Enabling the Oracle BAM Integration in Oracle B2B
» Programmatically Accessing Instance Message Data
» Declare the Variable_largePayload variable in an outbound BPEL process in the
» In the Assign activity, copy true into the variable.
» Assign the variable to b2b.largePayload in the Invoke activity.
» If you are doing large payload testing, set Show Payload on the Administration
» For an outbound SOA composite, always select the Use file streaming option for
» Create a test JMS module as shown in
» Install Weblogic server and SOA server.
» Navigate to Foreign JNDI Providers under Services on the left-hand navigation
Show more