Maintaining WebAS Settings from Java side

Question

Hi there
Where are the WebAS ABAP settings maintained from a JAVA point of view?
I know an RFC destination is configured in SM59 which allows ABAP to communicate with JAVA, but where / how on the J2EE Engine (Visual Administrator ??) are the WebAS ABAP settings maintained.
I get an error when opening the support desk tool, which says the WebAS Settings could not be retrieved. In addition, when clicking on the WebAS ABAP Settings tab, nothing is returned, which makes me think that there is some setting in Visual Administrator missing.
Cheers,
Andrew

Answer 1

Hi Andrew,
You can configure that through Visual Administrator. I am not sure which particular setting are you referring to but here's a list of frequently done activities. Do let us know what exactly are you trying to achieve, so that we can have a clear idea.
<i><b>Create and Maintain RFC destination on J2EE</b></i>
<b>Step 1</b>
1) Start SAP J2EE Engine Administrator with %INSTALLATION_ROOT%\admin\go.bat
2. Connect to the Enterprise Portal server (usually default)
3. Choose <SID>/Server<…>/Services/JCo RFC Provider in tree
4. Maintain RFC Destination
- Program ID: <PORTAL_HOSTNAME>_PORTAL
- Gateway host: <GATEWAY_HOST>
- Gateway service: sapgw<SYSTEM_NUMBER>
- Number of processes (1..20): 20
- Application server host: see Gateway host
- System number: <SYSTEM_NUMBER>
- Client: <System_CLIENT>
- Language: EN
- User: <User> (User in Backend SAP System)
- Password: <PASSWORD>
5. Copy the RFC destination to the available RFC destinations with the button Set
6. If not already running, start the RFC server with the button Start. To validate J2EE configuration you must first complete step 2
<b>Step 2</b>
1. The maintenance of an RFC destination with the transaction Display and maintain RFC destination (transaction code SM59) is required.
2. Before you create a RFC destination in the SAP Backend system, you have to create the RFC destination in the J2EE engine (see step 1)
3. Alternatively, this RFC destination can be defined with the customizing activity Maintain Portal server settings for EP 6.0 in table RSPOR_T_PORTAL. This RFC destination will be classified as a connected Portal
4. The RFC destination is used for the communication from the SAP Backend System to the SAP Enterprise Portal
<b>(A) Name of RFC destination</b>
- Choose the name of the RFC destination for an SAP Enterprise Portal
- SAP recommends SAP_EP as a name for the RFC destination to the connected Portal
<b>(B) Connection Type</b>
- Choose T for TCP/IP connection as the connection type
<b>(C) Description of RFC destination</b>
The Description of the RFC destination can be maintained language-dependent
(D) Activation Type
- Choose Registered Server Program as activation type Registered Server Program
- The server program is set up under Program ID on the J2EE engine (see step 1)
- The recommended naming convention is <PORTAL_HOSTNAME>_PORTAL
<i>Gateway Options</i>
- Enter the Gateway Host and Gateway Service under Gateway Options that are used by the J2EE engine to communicate with the SAP system
- The Gateway Host is an application server of the SAP system
- The Gateway Service can be set generically as sapgw<SYSTEM_NUMBER>
- The gateway parameters can be retrieved via the Gateway Monitor transaction (transaction code SMGW) with Jump Parameter Display.
Check: If the RFC destination is maintained on both sides (J2EE engine and SAP system), the connection can be checked with the button Test connection in
transaction SM59
<i><b>Import Certificate from SAP Backend System to Portal</b></i>
Let me know if you need any clarification on this.
Hope this helps.
Regards,
Sunil