Preparing your system environment and the prerequisites

To prepare your WebSphere® Portal and the prerequisites for installing Integrator for SAP, make sure that you have all the required files and configure your Ajax proxy.

1. Configure your Ajax proxy:
   1. Copy the following sample code and save it in a file named proxy-config.xml in a temporary directory on your WebSphere Portal server:

      <?xml version="1.0" encoding="UTF-8"?>
      <proxy:proxy-rules xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
          xmlns:proxy="http://www.ibm.com/xmlns/prod/sw/ajax/proxy-config/1.2">
          <proxy:mapping contextpath="/proxy" url="*"/>
          <proxy:mapping contextpath="/myproxy" url="*"/>
          <proxy:mapping contextpath="/common_proxy" url="*"/>
      <!-- You can have more than one policy section here. -->   
          <proxy:policy url="http://example_sap_portal.company.com:50000/*" 
                        acf="none" basic-auth-support="true">
             <proxy:actions>
                <proxy:method>GET</proxy:method>
                <proxy:method>HEAD</proxy:method>
             </proxy:actions>
             <proxy:cookies>
                <proxy:cookie>MYSAPSSO2</proxy:cookie> 
             </proxy:cookies>
             <proxy:headers>
                <proxy:header>User-Agent</proxy:header>
                <proxy:header>Accept*</proxy:header>
                <proxy:header>Content*</proxy:header>
                <proxy:header>Authorization*</proxy:header>
                <proxy:header>set-cookie</proxy:header>
             </proxy:headers>
          </proxy:policy>
      <!-- End of policy section -->   
          <proxy:meta-data>
             <proxy:name>socket-timeout</proxy:name>
             <proxy:value>10000</proxy:value>
          </proxy:meta-data>
          <proxy:meta-data>
             <proxy:name>retries</proxy:name>
             <proxy:value>2</proxy:value>
          </proxy:meta-data>
          <proxy:meta-data>
             <proxy:name>max-connections-per-host</proxy:name>
             <proxy:value>5</proxy:value>
          </proxy:meta-data>
          <proxy:meta-data>
             <proxy:name>max-total-connections</proxy:name>
             <proxy:value>100</proxy:value>
          </proxy:meta-data>
          <proxy:meta-data>
             <proxy:name>forward-credentials-from-vault</proxy:name>
             <proxy:value>true</proxy:value>
          </proxy:meta-data>
      </proxy:proxy-rules>

      For more information about configuring your Ajax Proxy, see the topic about Ajax Proxy configuration.
   2. If you do not use Basic Authentication for single sign-on, remove the references to Basic Authentication from the file proxy-config.xml .
   3. In the file proxy-config.xml, set the values for the parameters socket-timeout and retries according to your environment. If your SAP NetWeaver Portal is not available for some reason, these parameters determine the amount of time that the task spends on the inaccessible connection. WebSphere Portal tries a connection once for each user who logs in to the WebSphere Portal and who has access rights to the SAP navigation.
      Note: If the connection fails for many users, the failures can affect the performance of WebSphere Portal.
   4. In the file proxy-config.xml, replace the proxy URL with your SAP NetWeaver Portal host and port. Example: http://example_sap_portal.company.com:50000 .
   5. In the file proxy-config.xml, make sure to add your SSO token name to the cookie section of the SAP NetWeaver Portal host. For example, the token name can be MYSAPSSO2 .
   6. If you want to run the configuration task in the following step without specifying passwords, add the user IDs and passwords for WebSphere Application Server and WebSphere Portal to the file wp_profile/ConfigEngine/properties/wkplc.properties .
   7. Run the WebSphere Portal configuration task checkin-wp-proxy-config as follows:
      • If you added user IDs and passwords to the file wp_profile/ConfigEngine/properties/wkplc.properties , enter the task as follows:

        ConfigEngine.bat|sh checkin-wp-proxy-config 
                            -DProxyConfigFileName=/proxy-config.xml

      • If you want to specify the user IDs and passwords when running the configuration task, enter the task as follows:

        ConfigEngine.bat|sh checkin-wp-proxy-config 
                            -DProxyConfigFileName=/proxy-config.xml  
                            -DWasPassword=password 
                            -DPortalAdminPwd=password

      For more details, see the topic about Global proxy configuration.
2. Optional: If you do not have a page with the unique name ibm.portal.page.Applications in your WebSphere Portal, create it before installing Integrator for SAP. The installation process expects to find a page with the unique name ibm.portal.page.Applications in WebSphere Portal. It adds integration artifacts to this page as child pages. If you do not have this page in your WebSphere Portal and run the Solution Installer install task, an XMLAccess exception occurs.