Log in to the console. In the Domain Structure pane, shown in

2-4 Oracle Fusion Middleware Users Guide for Oracle B2B Figure 2–2 Domain Structure Nodes in Oracle WebLogic Server Administration Console The image shows the Summary of Servers configuration tab, which includes a table showing a summary of each server configured in the current WebLogic Server domain. In the table, each server occupies a single row with the following columns: Name, Cluster, Machine, State, Health, and Listen Port. To the left of each row is a check box. To the left, above and below the table, are the New, Clone, and Delete buttons. To the right, above and below the table, are links to Previous and Next pages of information.

3. Note the Listen Port column for your server.

■ Or from MW_HOME user_projectsdomainsyour_domain_nameconfigconfig. xml server namesoa_server1name ssl namesoa_server1name listen-port8002listen-port ssl machineLocalMachinemachine listen-port8001listen-port listen-address server

2.2.2 Accessing Oracle B2B Through Single Sign-On SSO

To log in, log out, and relog in to Oracle B2B using SSO in Oracle Identity Management, the b2bconsole location must be added to the mod_wl_ohs.conf file in Oracle HTTP Server as follows: Location b2bconsole SetHandler weblogic-handler PathTrim weblogic Getting Started with Oracle B2B 2-5 ErrorPage http:WEBLOGIC_HOME:WEBLOGIC_PORT Location This is in addition to the setting required for the b2b location: Location b2b SetHandler weblogic-handler PathTrim weblogic ErrorPage http:WEBLOGIC_HOME:WEBLOGIC_PORT Location

2.2.3 Enabling the weblogic User for Logging in to Oracle B2B

For the weblogic user in Oracle Internet Directory OID to log in to Oracle B2B as an administrator and search for users, the OID Authenticator must have an Administrators group, and the weblogic user must be a member of that group. To enable the weblogic user: 1. Create a weblogic user in OID using the LDAP browser. The users.ldif file is imported to OID as follows: dn: cn=weblogic,cn=Users,dc=us,dc=oracle,dc=com objectclass: inetorgperson objectclass: organizationalPerson objectclass: person objectclass: orcluser objectclass: orcluserV2 objectclass: top sn: weblogic userpassword: welcome1 uid: weblogic 2. Create an Administrators group in OID and assign the weblogic user to it. The groups.ldif file is imported to OID as follows: dn: cn=Administrators,cn=Groups,dc=us,dc=oracle,dc=com objectclass: groupOfUniqueNames objectclass: orclGroup objectclass: top owner: cn=orcladmin,cn=Users,dc=us,dc=oracle,dc=com uniquemember: cn=weblogic,cn=Users,dc=us,dc=oracle,dc=com

2.3 Using the Oracle B2B Interface

B2B activities are grouped as follows: ■ Administration ■ Partners ■ Reports ■ Metrics

2.3.1 Administration

Use the tabs of the Administration page, shown in Figure 2–3 , to manage importing and exporting, document protocols, deployments, types, batching, callouts, purging, listening channels, and B2B configuration.