PartnerManager Tree View of the Partner Profile Elements
You can use PartnerManager to import, export, delete, and list the Odette FTP Partner elements.
- Import - Import a PartnerProfile.xml into the Sterling B2B Integrator database
- Export - Export elements of trees from an Odette FTP Partner Profile in the Sterling B2B Integrator database into a PartnerProfile.xml file
- Delete - Delete one or more trees of one or more element types from the Odette FTP Partner Profile in the Sterling B2B Integrator database
- List - List one or more element types in the Odette FTP Partner Profile
Elements are treated as nodes that are connected to trees. A Partner Profile can reside in the Sterling B2B Integrator database or in an XML file.
The notation of a tree t (one node with its direct children) can be written as follows:
t (node_1, .. , node_n) or t_name (node_1, .. , node_n)- t is one of {pp, ppc, lp, lpc}
- t_name is one t combined with a name (for example, pp_local or lpc_3)
- the nodes, node1, .. , node_n can be simple trees
The following are the four different kinds of trees that can be used in a Partner Profile:
- The simplest tree has only one root node and no children. The
following diagram illustrates Physical Partners (pp) or Logical Partners
(lp) in an isolated view.
- The following diagram illustrates PhysicalPartnerContract (ppc)
with its local (pp_local) and remote (pp_remote) Physical Partners:
pp_local and pp_remote:
- The following diagram illustrates Logical Partner Contract (lpc)
with the following:
- One Physical Partner Contract (ppc) as a sub tree (either inbound or outbound)
- Two Logical Partners (lp): one originator (lp_orig) and one destination (lp_dest)
- The following diagram illustrates Logical Partner Contract (lpc)
with the following:
- Two – inbound and outbound – Physical Partner Contracts: ppc_inb, ppc_outb where each of the ppcs has its own Physical Partners; pp_X_local, pp_X_remote (X = inbound or outbound)
- Two Logical Partners: one originator (lp_orig) and one destination (lp_dest)
The illustrations depicted here are complete trees because all references inside the trees are resolved. However, under certain conditions, it is possible to have incomplete trees. For example, a Physical Partner Contract with only one local Physical Partner but no remote Physical Partner is incomplete because of one unresolved reference. Trees where the root node is a Logical Partner Contract have maximal size because they cannot be extended any more. See illustrations labelled 3 and 4. The import and export operations in PartnerManager are executed on one or more trees as illustrated in this topic.