| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Configuring: Configuring the Distribution Model |
|
Configuring Java CAPS for SSL Support
Configuring Java CAPS Business Processes
Configuring Environment Components for the Sun Business Process Manager
Configuring Sun Master Indexes (Repository)
Configuring Java CAPS Project Components for Application Adapters
Configuring Java CAPS Project Components for Communication Adapters
Configuring Java CAPS Project Components for Database Adapters
Configuring Java CAPS Project Components for Web Server Adapters
Configuring Java CAPS Environment Components for Application Adapters
Configuring Java CAPS Environment Components for Communications Adapters
Configuring Java CAPS Environment Components for Database Adapters
Configuring Java CAPS Environment Components for Web Server Adapters
Configuring SAP R/3 for the SAP BAPI Adapter
Configuring SAP R/3 for the SAP BAPI Adapter
Creating the RFC Destination for the Adapter
Configuration Needed in SAP R/3 to Send and Receive IDocs
Configuring Secure Network Communications for SAP
Configuring Siebel EAI Workflows
Importing an SNA Custom Handshake Class
Configuring WebLogic for Asynchronous Communication
Configuring Master Index (Repository) Connectivity and Environments
Related Topics for Sun Adapter for Batch/FTP
You need to complete the following in SAP R/3 to run a RFC BAPI inbound.
Transaction: SALE



Caution - We recommend that you use the Z prefix when defining a name. This prefix is reserved for external use, and will not conflict with any SAP naming conventions. Using the Z prefix will also prevent any interference with standard SAP functionality or conflicts with standard SAP terminology.
Transaction: SALE





