Chapter 2   Configuring Access


This chapter provides instructions for setting up access to your iPlanet BuyerXpert system and configuring buyer for ECXpert.

---

Note	The information in this chapter is based on the assumption that you have already read the iPlanet BuyerXpert Concepts and Release Notes.

---

This chapter contains following sections:

• About Configuring Access

• Administrator's Access Tasks

• Configuring iPlanet BuyerXpert for Outbound Documents

• Configuring iPlanet BuyerXpert for Inbound Documents

• Configuring ECXpert

• Access Business Rules

• Requirements for Inbound EDI Documents

• Deployment Issues

About Configuring Access

---

iPlanet BuyerXpert has the flexibility to write out XML files in different formats. The XML file can be in OBI 3.0 (draft) standard format or non-OBI format depending on how your business rules are set up. ECXpert and iPlanet BuyerXpert communicate through the NFS file system.

The iPlanet BuyerXpert software is shipped with maps that convert between OBI 3.0 (draft) and EDI 3040 standards. This chapter discusses integration between iPlanet BuyerXpert and ECXpert for both outbound and inbound iPlanet BuyerXpert documents.

Three special characters are supported for XML files: < > &

For both inbound and outbound XML files:

< should be replaced by: &lt;

> should be replaced by: &gt;

& should replaced by: &amp;

It is the responsibility of the map or the supplier to do the replacement for inbound documents. For outbound documents, iPlanet BuyerXpert does the replacement.

The following types of EDI documents are supported by iPlanet BuyerXpert:

• 850—Purchase order (PO)

• 860—Change order (CO)

• 850—Order request (OR)

• 855—Acknowledgement of order receipt (Ack)

• 856—Advance shipment notice (ASN)

• 865—Acknowledgement of order change (Change Ack)

Figure 2-1 shows the process flow between BuyerXpert and ECXpert.

Figure 2-1    Process Flow between BuyerXpert and ECXpert

Administrator's Access Tasks

---

Some of the procedures for administering access are contained in this administrator's guide and some are contained in the Admin interface help. Figure 2-2 contains a list of common access tasks. The right-hand column provides information about where to find instructions, guidelines, or tools for performing that task.

Figure 2-2    Administrator's Access Tasks 

Task	Location of Instructions/Guidelines/Tools
Configure for outbound documents.	Configuring iPlanet BuyerXpert for Outbound Documents section ECXpert Administration Guide
Configure for inbound documents.	Configuring iPlanet BuyerXpert for Inbound Documents section
Configure ECXpert. Includes setting up members, training partnerships, maps, service lists, and custom services	Configuring ECXpert section
Configure associated business rules.	Chapter 5 "Setting Up Business Rules" iPlanet BuyerXpert Admin interface
Observe requirements for inbound EDI documents.	Requirements for Inbound EDI Documents section
Review issues to be aware of for deployment.	Deployment Issues section

Configuring iPlanet BuyerXpert for Outbound Documents

---

Figure 2-3 shows the process flow for outbound documents.

Figure 2-3    Outbound Documents Process Flow

The data submitted to ECXpert needs to have a header record (HREC) and a trailer record (TREC). The header record has twelve fields, some of which are optional. The key fields are:

• Sender Qualifier

• Sender ID

• Receiver Qualifier

• Receiver ID

• Document Type.

Example of a Header Record
HREC**|ZZ|buyer|ZZ|seller|iPlanet000000001155|X|003040|850|OEPO

Example of a Trailer Record
TREC**

For details on the header record format, see the ECXpert Site Administrator's Guide.

The submitToECX_850.sh script (and the submitToECX_860.sh script) first normalizes the XML file, then adds the header record and trailer record, depending on the partnership agreement. Then the ECXpert submit command is called.

All configuration, including email configuration, can be done using the config_xdoc.pl script, which is located in the iPlanet BuyerXpert NASROOT/buyer/sample_data/xdoc/scripts directory.

Configuring iPlanet BuyerXpert for Inbound Documents

---

Figure 2-4 shows the process flow for inbound documents.

Figure 2-4    Inbound Documents Process Flow

The xdocin.sh script and java class wakeBuyer.class/wakeSeller.class are located in this ECXpert directory: $ECXHOME/bin.

The xdocin.sh scripts calls the wakeBuyer.class/wakeSeller.class and passes three arguments to wakeBuyer:

• Buyer server name

• Buyer server port

• XDOC data file name

The wakeBuyer class wakes servlet ReadInTest in iPlanet BuyerXpert, at which point the xdocin.sh script is set up as a service in ECXpert.

The files can be copied to their respective directories using the config_xdoc_in.pl script, which is located in the following iPlanet BuyerXpert directory: iASROOT/buyer/sample_data/xdoc/scripts.

Configuring ECXpert

---

Before you run the script, there are a number of set up tasks required so that ECXpert can interface with iPlanet BuyerXpert to route documents between sellers and the iPlanet BuyerXpert system.

These tasks include:

• Defining ECXpert Members

• Defining Trading Partnerships

• Setting Up Maps

• Defining a Custom Service

• Defining Service Lists

Defining ECXpert Members

You must define the following members in ECXpert:

• A member representing each buyer organization

• A member representing each seller organization
  

  ---

  Note	Member names must match the names specified in the EDI SENDER and EDI RECEIVER rules.

  ---

  
  

For the sample data provided with iPlanet BuyerXpert to work, you must create the following member organizations:

• BuyerCompany

• tech

Defining Trading Partnerships

For members to exchange information using ECXpert, a trading partnership must be set up specifying the details of the exchange. A trading partnership specifies:

• Who is sending

• Who is receiving

• What type of information is involved

• How the information is to be sent and received at each end

Figure 2-5 lists the entries required for sample data to work.

Figure 2-5    Required Trading Partnership 

Sender	Receiver	Document	Direction	Map	doc_type
BuyerCompany	tech	PO	Outbound	B850ECX35V34O.sun	850
BuyerCompany	tech	Change	Outbound	B860ECX35V34O.sun	860
tech	BuyerCompany	Order Request	Inbound	B850ECX35V34I.sun	850
tech	BuyerCompany	Ack	Inbound	B855ECX35V34I.sun	855
tech	BuyerCompany	ASN	Inbound	B856ECX35V34I.sun	856
tech	BuyerCompany	Change Ack	Inbound	B865ECX35V34I.sun	865

Setting Up Maps

Run the config_xdoc_in.pl script to set up maps to the correct directory for ECXpert to pick up.

Defining a Custom Service

To perform a service that is not built into ECXpert, you can define a custom service. iPlanet BuyerXpert ships with scripts that perform services that iPlanet BuyerXpert requires but that ECXpert does not provide

Figure 2-6 lists the custom services needed to make sample data work.

Figure 2-6    Required Custom Services 

Script	Description	Service Name
xdocin_850.sh	inbound 850 tech->BuyerCompany	inbound850
xdocin_855.sh	inbound 855 tech->BuyerCompany	inbound855
xdocin_856.sh	inbound 856 tech->BuyerCompany	inbound856
xdocin_865.sh	inbound 865 tech->BuyerCompany	inbound865

Defining Service Lists

In ECXpert, a service is a particular type of processing to be performed. Service lists indicate what services ECXpert is to perform on the transactions.

Figure 2-7 lists the service lists required for the sample data to work.

Figure 2-7    Required Service List

Sender	Receiver	Document	doc_type	Service List
BuyerCompany	tech	PO	850	parse, translate, ..
BuyerCompany	tech	Change	860	parse, translate, ..
tech	BuyerCompany	Order request	850	parse, translate, inbound850
tech	BuyerCompany	Ack	855	parse, translate, inbound855
tech	BuyerCompany	ASN	856	parse, translate, inbound856
tech	BuyerCompany	Change Ack	865	parse, translate, inbound865

Access Business Rules

---

The following iPlanet BuyerXpert business rules are associated with access and transmission:

• EDI Sender Rule

• EDI Receiver

• EDI Document

• Pre 4.1SP1 850 Order Map

• Auto Submit

• XMIT Currency

These business rules must be set up for every buyer organization, and can be accessed in the Transmission Rules category of the Admin interface. For additional information on business rules, refer to Chapter 5 "Setting Up Business Rules."

EDI Sender Rule

The name of the sender should match the name of the member in ECXpert. Enter this name for both Purchase Order and Order Change documents.

EDI Receiver

The name of the receiver should match the name of the member in ECXpert. Enter this name for both Purchase Order and Order Change documents.

EDI Document

The name of the sender should match the doc_type in ECXpert. Enter 850 for Purchase Order and 860 for Order Change documents.

Pre 4.1SP1 850 Order Map

Set this rule to True if you want iPlanet BuyerXpert to write out non-OBI compliant XML files.

Auto Submit

Set this to True if you want iPlanet BuyerXpert to automatically submit an incoming Purchase Order (850) document to approval.

XMIT Currency

Set this rule if you want iPlanet BuyerXpert to transmit the Purchase Order document (outbound 850) in a currency different from common currency.

---

Note	Verify that the conversion between this currency and common currency already exists in the buyer organization conversion table.

---

Requirements for Inbound EDI Documents

---

The following guidelines should be followed by the seller when transmitting an inbound document:

• All inbound documents should include the buyer organization name and seller organization name. The names should already exist in the database of the buyer organization.

  For OBI2.1, it is N1*BY and N1*SE.

• All inbound documents should include the requisitioner's login name.

  For OBI2.1, it is N1*EY

  For OBI3.0, put it into the email field of BuyingParty Contact

• For an Order Request document, the seller organization address must be used as the send-to location if no send_to_location for this seller company is defined in the System.

• The buyer organization address is not processed. The buyer organization address should already exist in the buyer database.

• For the ASN document, the seller organization should provide a carrier reference number so the requisitioner can track the shipping process.

• In an Order Request document, Total Monetary Amount (AMT) is required, not optional.

Deployment Issues

---

• File system access between the iPlanet BuyerXpert machine and ECXpert system must be read/write enabled. Also, the directory structure should be the same.

• The default scripts shipped with iPlanet BuyerXpert do not authenticate ECXpert. Therefore, the members must be made trusted.

• For outbound documents, the mapping from XML to EDI works only if you set Pre 4.1SP1 850 Order Map to false.

• If you run the config_xdoc.pl script to configure iPlanet BuyerXpert for ECXpert, the same header record appears for all partnerships. You can however, customize the header records in the deployed directory.

• Java (JDK 1.2 or higher) and Perl (5.0 or higher) must be in the environment.

iPlanet ECXpert and HTTPS

When configuring XDOC using the config_xdoc_in.pl script, the user is asked what protocol is being used by iPlanet BuyerXpert (http or https). If the user chooses https, then he is prompted for two other pieces of information:

• Classpath of the SSL Provider

• Classpath of the SSL Protocol Handler

This information is required because SSL implementations can be provided by several vendors and the classpaths may vary depending on the vendor.

---

Note	It is important to verify that the jar file(s) corresponding to the SSL implementation is (are) present in the classpath. If not, a ClassNotFoundException error occurs.

---

If the user incorrectly indicates that iPlanet BuyerXpert is using an HTTPS connection when it is actually using an HTTP connection, an Unrecognized SSL handshake SSLException occurs.