In this section, the environment settings for the X-UP server and X-UP Builder that are necessary for users during development are explained.

X-UP Server Settings

To configure the X-UP server, several environment configuration files are provided. This explanation assumes that the X-UP server has been installed.

By navigating to the [webapps > xup > WEB-INF > xup > conf] path in the WAS installation directory, you will find various configuration files as shown in the image below.

xup_config.xml

The xup_config.xml file contains the following configuration information for the X-UP Server.

The exception log levels used by X-UP Server are as follows:

auth_info.xml

The auth_info file contains account information for X-UP.

By default, no accounts are provided in the distribution, and accounts need to be configured using the bin/encrypt.bat file. Below are the steps for configuring an account.

To set up the account, navigate to the bin folder.

Set the name and password values.

Here is the content of the authInfo.xml file after adding the account.

<?xml version="1.0" encoding="utf-8"?>
<authInfo>
  <userList>
    <user>
      <name>xup</name>
      <password>n1M4xHQzLqhyIJjrzPIsFg==</password>
    </user>
  </userList>
</authInfo>

To add a new account, run encrypt.bat with the command: encrypt.bat newName newPassword.

web.xml

The web.xml file, located under the xup/WEB-INF folder in the X-UP server's web application root directory, handles servlet configurations, servlet mappings, filters, and encoding settings.

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>

	<!-- xupservice, webservice, ui5 -->
	<servlet>
		<servlet-name>FrontControllerServlet</servlet-name>
		<servlet-class>com.nexacro.xup.service.FrontControllerServlet</servlet-class>
		<load-on-startup>1</load-on-startup>
	</servlet>
	
	<!-- serviceInfo, webServiceWSDL -->
	<servlet>
		<servlet-name>ServiceInfoServiceServlet</servlet-name>
		<servlet-class>com.nexacro.xup.service.ServiceInfoServiceServlet</servlet-class>
	</servlet>
	

	<!-- Servlet Mapping -->
	<servlet-mapping>
		<servlet-name>FrontControllerServlet</servlet-name>
		<url-pattern>/FrontControllerServlet.do</url-pattern>
	</servlet-mapping>
	
	<servlet-mapping>
		<servlet-name>ServiceInfoServiceServlet</servlet-name>
		<url-pattern>/ServiceInfoServiceServlet.do</url-pattern>
	</servlet-mapping>

</web-app>

JCO Library

The following libraries are recommended by the SAP guide to be placed in the system's specified path for use.

In X-UP, these libraries are distributed for easier use during development through X-UP Builder. In X-UP, when using JCO 2.0, it loads librfc32 and internally loads sapjcorfc.dll. For JCO 3.0, it internally loads sapjco3.dll, so X-UP does not need to load it separately.

For JCO 3.0, the installation method when applying sapjco3.dll is as follows:

• Using NetWeaver

  • X-UP does not load JCO-related libraries

    • Use 'xup_env.property com.tobesoft.useJcoStandalone= false'

    • Delete sapjco3.jar and sapjco3.dll for SAP RFC DataSource

• During Development and Operation

  • X-UP loads the sapjco3.jar library

    • Load the library located in the SAP RFC DataSource

  • If sapjco3.jar library is located in the System Path

    • Use 'xup_env.property com.tobesoft.useStandAlone = false'

    • Delete sapjco3.jar and sapjco3.dll in the SAP RFC DataSource

  • When using the Java ext folder

    • Use 'xup_env.property com.tobesoft.useStandAlone = false'

    • Move sapjco3.jar from SAP RFC DataSource to the Java ext folder

    • Move sapjco3.dll from SAP RFC DataSource to the Java bin folder

X-UP Builder Preference Settings

X-UP Preference allows configuration of the overall environment settings for X-UP Builder. Access X-UP Preference by navigating to [Window > Preferences.. > X-UP].

Currently, X-UP Preference is organized into the following sections

• X-UP: General X-UP Builder Settings

  • DataSource: Manage frequently used data sources

  • "Export Generated Files" PATH: The location where resources will be copied when "Export Generated Files" is executed.

X-UP

Common environment settings can be defined.

The "Is show X-UP Builder log message to console" option allows setting whether to output logs to the console. Additionally, the "include package and class debug line message" option defines whether to include the "package" and "class line message" in the logs when the output is directed to the console.

The "SAP RFC GROUP Search limit count" option limits the number of records displayed during group searches, preventing excessive data from being shown. Only the defined number of records will be displayed. More environment setting options will be added in the future.

DataSource

X-UP Builder allows saving frequently used data sources in advance for easy reference or reuse when creating X-UP models.

Registered data sources can be referenced from anywhere, regardless of the project or model.

In X-UP Builder's Preference, you can define and use data sources using the following method.

1. Click the [Window > Preferences..] menu to open the Preferences wizard.

2. Select the X-UP DataSource menu to display the data source settings screen.

3. Click the New button to define a new data source.

4. The defined data sources can be copied and used in X-UP projects. In the X-UP model creation wizard, click the 'Define DataSource' window and select the Copy From… button to copy the data source defined in Preferences.

Compile Version Change

The JRE version used by X-UP Builder is 1.6. Therefore, users can change the compile version in X-UP Builder as follows.

The compile version can be changed to 1.5 in the X-UP Builder's Preference settings as described below.

1. Click on the [Window > Preferences] menu to open the Preferences wizard.

2. Click on the Java Compiler menu.

3. Select the Compiler compliance level as 1.5 under JDK Compliance and click the Apply button.