Seeburger Overview

Seeburger is the Partner Connectivity Gateway for Ingram Micro. It handles inbound and outbound
transactions with our vendors and partners. The Seeburger gateway is used by the Ingram Micro
Distribution (IMD) business and the Ingram Micro Logistics (IML) business. The system provides an entry
point into Ingram Micro and has several internal connectivity points within Ingram Micro. Some are
main ones are listed below.

- Impulse – Mainframe ERP. Inbound Orders, Order Responses, Ship Notices, Invoices, etc.
Countries: Most of Europe, United States, Canada
- SAP – Inbound Orders, Order Responses, Ship Notices, Invoices, etc. Countries: BE, NL, AU, SG,
US and Canada IML business
- IPC and RPE – Seeburger receives price files from these systems. SAP countrys.

Other PCG gateways at Ingram Micro, for reference purposes:

- Legacy PCG Tibco Gateway. (HTTP) Handles XML messages going to Impulse. Has some
connectivity with Seeburger for SOAP v3 and RNet transactions.
- Cyclone. AS2. Being replaced by Seeburger
- CE:Unix . FTP. Being replaced by Seeburger.

Seeburger Protocols:

- HTTP/HTTPS
- FTP/SFTP
- AS2
- RNIF
- Email

Seeburger Message Formats:

- EDI x12
- EDI Tradicom
- Proprietary XML (Ingram Micro formats and partner format)
- RosettaNet XML
- Flat files/Delimited
- PDF files
Seeburger Support

Setup needed for support. The following should be setup to support the Seeburger application.

- Mapping Designer. Seeburger install.

- Process Designer. Seeburger install.
- Database access for map testing/report generation. Database setup on machine.
- Telnet access to Seeburger servers to check connectivity to partners and reprocessing of files.
- Remedy Access
- Seeburger Front End Access
- SAP Access. ECC prod and TE1, TE2, QA1, QA2

Seeburger URLs

Message Tracker. Used to search for messages. Central database that stores data for a Seeburger
Instances. (XML, EDI and Reporting)

https://mars.ingrammicro.com

Can also be accessed via: (This can be faster while on the ingram micro network)
https://uschlpcg1101:30000/

Seeburger Front End URLs

The Seeburger Front End program is used to monitor the system, resent files and view messages. There
are several Seeburger instances.

XML Instances:

http://USCHLPCG1003:20000/security/login
http://USCHLPCG1004:20000/security/login
http://USCHLPCG1005:20000/security/login

EDI and Reporting Instances:

http://sbprodcentral:20000/security/login

On 8/10 Addition Seeburger Servers will be added to Support EDI.

http://uschlpcg1007:20000/security/login
http://uschlpcg1008:20000/security/login
http://uschlpcg1009:20000/security/login
Monitoring Seeburger Alert Email

Monitoring Hourly Report (See Appendix A) for an example.

Look for any area that has a high number failures. It depends on the process but 40 is probably high. If
you see thousands than there is a more serious issue or one large partner server is down.

Monitor Seeburger Transactions with Filters

Create Filter for today’s processes, yesterdays processes and all process.. This will help with monitoring
failures in Seeburger and will help with resending failures.

APPLE_FAILURES Filter

State: Failed (7)

Info3: *APPLE*

This filter should be checked first thing every morning and several times throughout the day. These
failures should be addressed before other partner failures.

OUTBOUND_FTP_SERVERFAILURES Filter

State: Failed (7)

ProcessName: {http://www.seeburger.com/}OutboundFTPServer

(Set up under the Failed Processes Section)

This will give you all the outbound processing failure. LOOK OUT for any failure with Info 8 and blank
and Info 5: UNKNOWN. This indicates corrupt data from the main frame.

UNKNOWN ** Requires immediate attention **

This indicates corrupt data from the main frame. Basically someone has added a new partner(s)
improperly in Impulse. Work with the impulse team to correct the setup, also the input file will need to
manually be altered and reprocessed.

- Download file and look for bad Records. (EDI messages that look empty)
- Ask the Impulse team if there has been new setups
- If the issue cannot be found with a visual inspection we need to run the file through the map

TPLOOKUP

These failure should be handle by the TP Enablement team. This is when a transaction is in the
mainframe EDI batch and we don’t have a setup in Seeburger.
FORWARDING_AS2

These failure should be resent if the failure has something to do with connectivity. Connect Timeout
etc. Right click and restart these processes.

EMPTY FILE

These failures can simply be a Acknowledged. They are empty files from the mainframe.

FORWARDING_HTTP
These failure should be resent if the failure has something to do with connectivity. Connect Timeout
etc. Right click and restart these processes. If a certificate has expired then it needs to be uploaded
before a resend.
Seeburger Tickets

Incidents are handled using the following application.

Remedy: https://im-remedy.com/arsys/shared/login.jsp?/arsys/home

- Review incidents under queue B2b Seeburger AMS

- A Bridge call should be opened for High and Critical Issues
o Open by Email csd@ingrammicro.com) or
o Phone : 1(877) 848-7609 or 22800 while at Office

Query to review open incidents:

'Assigned Group*+' = "Global IS – B2B AMS PC Seeburger" AND ( 'Status*' != "Resolved" AND
'Status*' != "Closed" AND 'Status*' != "Cancelled" )

Query To review resolved tickets:

'Assigned Group*+' = "Global IS – B2B AMS PC Seeburger" AND ( 'Status*' = "Resolved")

Contacts

Below is a list of groups that we deal on a day to day basis.

Impulse Team: IM_Impulse_Mumbai_Support <IM_Impulse_Mumbai_Support@ingrammicro.com>

PCG XML Impulse Team: (IT - XML Support (itxmls@IngramMicro.com)
Seeburger Platform Team: Jha, Ashwinikumar <Ashwinikumar.Jha@ingrammicro.com>; Chamala,
Nishanth <Nishanth.Chamala@ingrammicro.com>; Kim, Hunsu <hunsu.kim@IngramMicro.com>
IM Mid Operations (for deploys and production access): IMMidOps IMMidOps@ingrammicro.com
BI Team (Reports generation): IMGlobalL&TAMSSupportBI@ingrammicro.com
North America Help desk: ECS - Buffalo <Electronic.Services@IngramMicro.com>

Reports and Price Files

- IML
- Price Files

Apple Close Loop Report

Sample close loop report shown below.

 FW URGENT --
FW US_APPLE Transactions Close Loop Report for SLA Date 20130804 IS_STATUS-RED(SB_STATUS-GREEN) OPR_STATUS-RED.msg
Appendix A – Sample Email Alert

SEEBURGER LIVE
DASHBOARD for 2013-08-05 07 02 58.msg
Appendix B – Glossary

CRQ – The name for a change request at Ingram Micro.

DDC- Seeburger production which acts as a file system for Partners to send and retrieve data.

EAI – Enterprise Application Integration. Internal system which Seeburger interacts with to process data
for SAP and Impulse.

IMD – Ingram Micro Distribution business.

IML – Ingram Micro Logistics business

Impulse – Mainframe ERP application

RMA - Return Material Authorization

SAP – ERP system used for several countries and IML business

Seeburger Front End Custom Columns:

Info1: Seeburger Track ID

Info2: Connectivity source. Example: AS2, FTP, JMS, RNIF, SAP.
Info3: Trading Partner Name
Info4: Agreement Name
Info5: Message Type: ANSIX12, iDOC, XML, XML_RNIF
Info6: In case the message is from SAP this will be the idoc number. Example:
0000000219774268.
Info7: Filename when the input is a file from the mainframe or report sytem.
Info8: In case of failure this will be the failure type. Example: CONVERSION.

Tibco – Software company that makes middleware products. We used several of their products for the
EAI applications and Legacy PCG xml applications. Generally when you hear Tibco we are talking about
EAI and PCG XML systems.

JMS – Java Messaging System

Appendix C - Connectivity to EFS report server.

Be careful with this.

Ipaddress: 10.22.96.110
Port: 22
User: sbbisprd
Password: seeburger
Folder: /pcg