About AReNA B2B Connect

[Alejis]

Can anyone give me details on how this work?
which is the basic hardware that I must have?
If someone has some document about this subject, please, send me it to alejandra@netline.cl

Thank you very much. Alejandra.

 

[dpes1]

Alejandra: From Doco:


The PAC SERVER:
Partner Agreement Connect consists of
 Alliance Channel. This provides a direct connection to a PAM system (such as ArenaNet)
 Process Server. This is the engine that manages all public and private processes.
 Adapter Server. This is the engine that managers Adapters.
 PAC Proxy. Provided for extra security. This usually resides inside the DMZ
 Adapters – Generic (File, FTP, Zip, Email) and Application Specific (ie. MIMS/Ellipse)
 PAC Client – IDE for reviewing public processes, creating and managing private processes. Reviewing the exceptions within the system

Hardware and Software Requirements V1.1 of IBM Partner Agreement Connect

V1.1 of PAM/PAC supports both Windows NT (Intel) and Unix (Solaris and AIX) processors.
Server Hardware

 Intel
 Pentium III 600 MHz processor (or better)
 512 MB RAM (or more)
 A hard drive with 2 GB of free space (or larger)
 TCP/IP network adapter
 Sun and AIX (RS/6000)
 Single Processor
 256Mb of Memory
 2Gb of free disk

Server software requirements

 A standard version of Windows NT Server 4.0 operating system with Service Pack (SP) 6a
 Network access to an SMTP server (for email notifications), plus an email account that Partner Agreement Connect can use for sending email for notifications
 A certificate for the Web server (available from any certificate authority, such as

http://www.verisign.com,

depending on the local security policy). For notification and approval actions of public processes.
 DB2 V7.1 with Fix Pack 3 or DB2 V7.2 is required or Oracle 8.1.5
 IBM HTTP Web server and JVM 1.2.2

Application client hardware requirements (Optional)

The client can run on the same PC as the Process Server
 Pentium 166 MHz processor (or better) Recommended 64 MB RAM (or more)
 30 MB free hard disk space (or more)

Application client software requirements (Optional)

 A standard version of Windows NT Workstation 4.0 operating system with Service Pack (SP) 6a (not a Microsoft Developer Network release)
 Sun JRE (Java Runtime Environment) 1.2.1

Hardware and Software Requirements of IBM Partner Agreement Connect V2.1
Server Hardware

 Pentium III 600 MHz processor (or better)
 512 MB RAM (or more)
 A hard drive with 2 GB of free space (or larger)
 TCP/IP network adapter

IBM has committed to support Solaris and AIX but not firm timetable has been announced.
Server software requirements

 A standard version of Windows NT Server 4.0 operating system with Service Pack (SP) 6a
 Network access to an SMTP server (for email notifications), plus an email account that Partner Agreement Manager can use for sending email for notifications
 A certificate for the Web server (available from any certificate authority, such as

http://www.verisign.com,

depending on the local security policy). For notification and approval actions of public processes.
 DB2 V7.1 with Fix Pack 3 or DB2 V7.2 is required
 IBM HTTP Web server and JVM 1.2.2

Application client hardware requirements (Optional)

The client can run on the same PC as the Process Server
 Pentium 166 MHz processor (or better) - Recommended 64 MB RAM (or more)
 30 MB free hard disk space (or more)

Application client software requirements (Optional)

 A standard version of Windows NT Workstation 4.0 operating system with Service Pack (SP) 6a (not a Microsoft Developer Network release)
 Sun JRE (Java Runtime Environment) 1.2.1
Performance

For a Pentium III 700 with 512Mb of Memory, current estimates have the processor supporting 2000 – 2500 transactions per hour or approximately 60000


The software provided by Mincom as part of the Mincom Axis Connect
Installation:

IBM Partner Agreement Connect
IBM DB2 7.1 with Fix Pack 3
IBM HTTP Server
Arena B2B Connect
IBM JRE 1.2.2
Windows Scripting
MDAC 2.5
Mincom Axis Digital Certificate (this is not required for the intial
testing)
IBM PAC Proxy
JDBC Driver (This is the Thin Driver and not the OCI Driver)

Provided by the Customer

Windows NT 4, SP6a including Licence
Microsoft Internet Explorer 5.5
Solaris (if required for the Proxy
All Hardware

For the JDBC Driver, a TCP/IP Listener is required - Oracle's JDBC
Thin driver is a Type 4 driver that uses Java sockets to connect
directly to Oracle. It provides its own implementation of a TCP/IP
version of Oracle's Net8. Because it is written entirely in Java, this
driver is platform-independent. The Thin driver does not require
Oracle software on the client side. It connects to any Oracle database
of version 8.0.4 and higher. The driver requires a TCP/IP listener on
the server side.

Also a note on Digital Certificates.

Mincom will supply a digital certificate that will be used by
Customer to Digitally Sign and Encrypt data that flows between
Customer and Mincom Axis.
Customer may also use what is known as 'Approval Processes'. These
Processes are 'private' to Customer and run on the HTTP Server
Supplied as part of Mincom Axis Connect. Approval Processes are a
web form that allows the organization to set approval steps
Depending on certain criteria. Approval steps are Web pages that
can be protected by SSL. As such if required an organization would
require a digital certificate to provide the SSL Support. Customer
may wish to use the Mincom Axis supplied certificate, not use SSL
or use a third party certificate. If Customer does not require
approval steps than no certificates are required for this purpose.


Donna

 

[Alejis]

Hi Donna,

Thanks for your answer.
I know that Mincom has two B2B Integration options:
Arena B2B Connect (point-to-point strategy) and Mincom Axis (e-hub strategy).
Mincom Axis also uses Arena B2B Connect (I understand that they are the adapters).

In the point-to-point strategy Mincom provides these adapters and the plug-ins for a B2B server.
This B2B Server is used to transmit and receive the business documents directly with the Trading Partners and the supported B2B server are WebMethods B2B Server or IBM Websphere B2B Integrator.

Well, I need to know if anybody has implemented the point-to-point strategy.

Sorry I was not specific in my previous question.

Thank you very much.

Regards, Alejandra
alejandra@netline.cl

 

[dpes1]

Alejandra:

All of our traffic is going to Quadrem marketplace. No direct connects yet.

: )