Logging In to a LiveCycle Server

After you start Workbench, you establish a connection with a server by logging in. Your administrator must configure your user account and the server so that you can use Workbench.

Logging in

To work on your processes or forms, you first must log in to a server. If a server has not already been configured for logging in, see Configuring server connections.

Hinweis: If you have configured LiveCycle to use the Documentum or FileNet repository provider, and you want to log in to a repository other than that configured as the default in Administration Console, you should provide the user name as [username]@[Repository].

After you log in, the server that you are logged into and the user name that you logged in with appear in the lower right-hand corner of Workbench. The following illustrations shows that the administrator user is logged into the localhost server.

To log in to a server:

  1. Start Workbench and select File > Login.

    You can also click the Login button  .
  2. In the login window, type your user name in the Username box and type your password in the Password box.

  3. In the Log On To list, select the required server and then click Login.

Hinweis: For security, the Reauthentication window may reappear at regular time intervals after you log in, at which time you need to provide your password again. Your administrator can determine the time interval. For more information, see “Configuring User Management > Configuring LiveCycle time-out setting” in User Management Help.

Increasing the memory allocation

If a low memory warning appears when you log in to Workbench, you can increase the amount of memory allocated to Workbench.

To configure the allocated memory, modify the workbench.ini file property that controls the amount of allocated memory. The property is in the format -Xmx[number]M, where [number] is the number of MB of memory that is allocated. The default amount of memory that is allocated is 512, which is set by using the property value of -Xmx512M. You increase the amount of memory in increments of 256. For example, if the warning appears when 512 MB of memory is allocated, increase the allocated memory to 768. If the warning occurs again, increase to 1024.

The workbench.ini file is located in the [install directory]/Adobe/Adobe LiveCycle Workbench 11/Workbench directory, where [install directory] is the location where you installed Workbench.

Increase the allocated memory:

  1. In a text editor, open the workbench.ini file.

  2. Locate the line that contains the property that sets the amount of allocated memory, and modify the values of the property as required. For example, -Xmx768M allocates 768 MB of memory.

  3. Save and close the workbench.ini file and restart Workbench.

If a low memory warning appears after extended use of Workbench, close and restart it.

Configuring server connections

You need to configure a connection to the LiveCycle Server that you want to log into and access the resources that it stores. If a server is not already configured or you want to change the server settings, you can configure the server from the login dialog box. Ask your administrator for the values you should use when configuring a server.

After you configure a server, you can select the configuration in the login window.

Hinweis: To use EJB connections, the LiveCycle Server and the computer that runs Workbench must reside on the same network subnet.

The following values are the default ports for the naming service of the supported application servers:

JBoss:
1099

WebLogic:
7001

WebSphere:
2809

Enabling EJB connections to WebSphere

If you are enabling EJB connections to WebSphere, you need to install a Java Runtime Environment that is provided by IBM, and configure Workbench to use it. For more information, see the Installing Workbenchguide.

To configure a server:

  1. In the Adobe LiveCycle ES4 login dialog box, click Configure. The Manage Configured Servers dialog box appears.

  2. To add a new server, click the Add New Server button  . To edit an existing server, select a server and click the Edit Selected Server button  .

  3. In the Server Title box, type a name to describe the server. This name is descriptive only. It is displayed in the selection menu of the login window.

  4. In the Hostname box, type the name or IP address of the LiveCycle Server.

  5. In the Protocol list, select Simple Object Access Protocol (SOAP/HTTP) or Simple Object Access Protocol (SOAP/HTTPS).

  6. In the Server Port Number box, type the port number provided by your administrator. This specifies the port number used to connect to the server.

  7. (Optional) To enable LiveCycle 7.x QPACs to communicate through an EJB connection, select Enable EJB Connections For LiveCycle 7.x QPACs, an then, in the EJB Port box, enter the port to use.

  8. Click OK, and then click OK again.

Logging out

If you are finished using Workbench or want to log in to a different server, you need to log out of the server you are connected to.

To log out of a server:

  1. Select File > Logout.

  2. In the logout window, click Logout.

    You can also click the Logout button  .

User permissions

To log into Workbench, your user account needs to be assigned the role of an Application Administrator. This role provides the following permissions that are relevant to Workbench users.

  • Use Administration Console (Applications and Services pages) to configure service run-time properties; add, remove, and configure endpoints, and configure security.

  • Install and uninstall components.

  • Create applications.

  • Delete applications

  • Create event types.

  • Delete event types.

  • Create processes.

  • Delete processes.

  • See a list of recorded process instances and play them.

  • Start and stop services, and activate and deactivate processes.

  • Open processes for reading and editing.

  • Invoke services.

  • Use Workbench features that enable you to create forms:

  • Set and delegate access permissions for applications.

For more information about assigning roles to users, see LiveCycle Administration Help or contact your LiveCycle administrator.