Design B2B Integrations in Projects or in Standalone Environments

You can design your B2B schemas, documents, trading partners, and integrations inside projects or in standalone environments (outside of projects).

Oracle recommends designing your integrations in projects. Projects provide a single workspace for designing, managing, and monitoring integrations. Use projects to perform release management, manage access to automation solutions, and keep everything organized. See Get Started with Projects and Tour of the Projects Workspace in Using Integrations in Oracle Integration 3.

Access B2B resources as follows:
  • In projects:
    1. In the navigation pane, click Projects.
    2. Click the project in which to design a B2B integration.
    3. Click B2B B2B icon.
    4. Depending on the design task to perform, go to the Documents, Schemas, or Trading partners section.
    5. Use the Deploy tab in the Integrations Integration icon section to create project deployments that use B2B.
    6. Use the Observe tab to monitor B2B wire messages and business messages at runtime.
  • In standalone environments (that is, outside of projects):
    1. In the navigation pane, click B2B.
    2. Depending on the design task to perform, select Documents, Schemas, Trading partners, or Host profile.
    3. Use the B2B Tracking tab to monitor B2B wire messages and business messages at runtime.

What's Supported in Projects for B2B

  • Documents, schemas (standard and custom), and trading partners
  • Sharing of schemas across projects to allow for reuse and consistency
    Schemas act as the structural base for B2B documents and are good candidates for reusability. Note the following details about sharing schemas:
    • When creating a schema, you can do either of the following:
      • Select to use a shared schema from another project.
      • Make the schema available for use in other projects.
    • You cannot edit a schema referenced by a schema that is part of an active agreement or integration.
    • You cannot delete a schema if it's referenced by any schema in another project.
    • You cannot delete a project if it contains a schema that is referenced in another project.
    • Schemas not marked as sharable are not eligible for access in other projects.
    • Schemas created in standalone environments are not sharable in projects.
    • Schema marked as sharable can only override another schema.
  • Trading partners and agreement deployments
  • Transport deployment
  • Export and import of individual documents and schemas
  • Export and import of individual trading partners
  • Export, import, and deletion of a project that includes documents, schemas, and trading partners
  • Activation and deactivation of a project deployment that includes documents, schemas, and trading partners
  • B2B action design in integrations in trading partner mode
  • Viewing and managing B2B design-time backend integrations, Send integrations, and Receive integrations under the Design tab in the Integrations Integrations icon section of a project
  • Viewing B2B runtime backend integrations, Send integrations, and Receive integrations under the Observe tab in the Integrations Integrations icon section of a project
  • Tracking runtime business messages and wire messages under the Observe tab
  • Design time and runtime support for the RosettaNet, AS2, AS4, FTP, and REST adapters
  • Viewing B2B integrations in the dependency diagram of a project
  • Resubmitting/reprocessing business messages or wire messages from the Observe tab in a project.
  • Role-based access control (RBAC) support to manage the users and groups that can edit, view, and monitor trading partners, schemas, and documents in a project. RBAC enables some users and groups to perform specific actions in a project while restricting others.
    Note the following details about B2B for Oracle Integration and RBAC:
    • B2B monitoring inside a project is only accessible to users with the proper access controls for that project.
    • B2B monitoring at the standalone (nonproject) level is restricted to users with access to view all standalone business and wire messages and specific project business and wire messages.
    • Existing, pre-RBAC B2B customers and existing development processes/flows performed at the standalone level remain unchanged.
    • RBAC applies only to design time and monitoring activities. RBAC does not impact runtime behavior.
    • The B2B Dashboard shows metrics for both project and standalone resources.

    For specific details about RBAC, see Control Who Can Edit, View, and Monitor in a Project in Using Integrations in Oracle Integration 3.

    For details about B2B for Oracle Integration tasks that users granted specific service roles can perform and Oracle Integration service roles, see What Users Can Do in B2B for Oracle Integration by Role and Oracle Integration Service Roles in Provisioning and Administering Oracle Integration 3.

What's Not Supported in Projects for B2B

  • You cannot define the host profile. The host profile is only available in standalone environments (outside of a project).
  • You cannot create a B2B schema by importing a Standard Exchange Format (SEF) file.
  • You cannot share some B2B artifacts (documents and trading partners) created in one project with another project.
  • The B2B dashboard page is only available in standalone environments by selecting Observability, then Dashboards, and then B2B from the drop-down list.
  • You cannot migrate B2B artifacts from Oracle SOA Suite to a project.