Siebel Remote and Replication Manager Administration Guide > Troubleshooting Remote and Replication Manager >

Setting Up Remote Server and Remote Clients

This quick reference sequence provides an overview of the steps to set up Siebel Remote on both the server and the Mobile Web Client. The purpose is to provide a "quick look" so you can review or learn the material.

The following sequence of steps outlines the general flow to set up Siebel Remote Server and Remote Clients for an out-of-the-box installation of your Siebel application.

  1. Make sure employees are set up; navigate to Application Administration > Employees > Employees.

    The employee must have at least one position and responsibility. The fields cannot be blank.

  2. If your deployment includes regional nodes, define the appropriate employees as users on their corresponding regional nodes.

    For details on how to do this, see Registering a Regional Node.

  3. Set up users as Mobile Web Clients: navigate to Remote Administration > Mobile Clients.
    1. Add Mobile Web Clients here.
    2. At a minimum, fill in the fields Mobile Client, User Login Name and Routing Model.

      For example: HALACON, HALACON, MOBILE CLIENT - STANDARD

  4. Start a "Generate New Database" process. Wait for it to finish successfully.
  5. If the Siebel Server has not had Mobile users set up on it before, start a "Database Extract Process" for the Mobile Web Clients.
    1. Enter * in the Client Name field in the Parameter Overrides view.
    2. Wait for this task to finish successfully.
  6. If the transaction process is not currently running, start a transaction processor process.

    For details to start a transaction processor component, see Starting Siebel Remote Server Components.

  7. If the transaction router process is not currently running, start a transaction router process.

    For details to start a transaction router component, see Starting Siebel Remote Server Components.

  8. If the transaction merger process is not currently running, start a transaction merger process.

    For details to start a transaction merger component, see Starting Siebel Remote Server Components.

  9. Make sure that you set up the Mobile Web Client hardware and software.
  10. Make sure the appropriate CFG files for your Mobile Web Clients are correctly set up.

    Especially verify the contents of the section titled [Local]. Values of CHANGE_ME are indicators that these values probably require changing.

  11. Run a Mobile Web Client session on a mobile user's PC and attempt to connect to the local database.

    It will not exist yet and will require initialization of the local database.

    If this step is successful, it means the mobile user is set up and initialized correctly.


 Siebel Remote and Replication Manager Administration Guide 
 Published: 19 November 2003