Sybase.com

DocID: DC10036-01-0500-01

Topic	Page
1. Accessing current release bulletin information
2. Product summary
3. Special installation instructions
4. Special configuration instructions
5. Special license upgrade instructions
6. Port conflicts
7. Sybase WorkSpace Development Issues
8. Sybase Unwired Orchestrator Server Issues
9. Internationalization Issues
10. Documentation updates and clarifications
11. Technical support
12. Other sources of information
13. Accessibility features

1. Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the release of the product CD, use the Sybase Technical Library Product Manuals Web site.

Accessing release bulletins at the Technical Library Product Manuals Web site

Go to Product Manuals.

Follow the links to the appropriate Sybase product.

Select the Release Bulletins link.

Select the Sybase product version from the Release Bulletins list.

From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.

2. Product summary

See the Sybase WorkSpace online help for product summary information.

3. Special installation instructions

3.1 Installation updates

Review the following instructions and updates before installation.

3.1.1 Warning message after CD2 installs

CR # 403689

Description: During the CD installation (this does not apply to DVD installations), you may receive the following warning after the installation of CD2 is complete:

The wrong volume is in the drive. Please insert volume WS 1.0 WIN CD1 into drive <n>.

Workaround: If you receive the warning, leave the warning open and do the following:

To complete Sybase WorkSpace installation:

Eject CD2 and re-insert CD1.

If the CD drive is configured to Autorun, you may receive the following error message:

The Vital Product Data registry is in use by another installer. Please start this installer after the other installation has finished.

Click OK.

In the warning, click Try Again to complete the install.

Do not click Cancel or Continue. Clicking Continue or Cancel causes the installer either to hang or to appear to complete successfully, even though the installation is not complete

Complete the installation as prompted.

In the rare situation that the above workaround does not work, use the following alternate procedure.

To complete the Sybase WorkSpace installation:

Ensure you have 1.5G available on your local drive.

Create a temporary directory on your local drive.

Copy CD1 into the temporary directory.

Copy CD2 into the same directory.

If you are prompted to overwrite some files and directories, select Yes.

Locate the WorkSpaceContents.ini file in the temporary directory.

Using Notepad, make the following change to the second line in the section [Image]:

CDVersion=0

Double-click setup.exe in the temporary directory to start the installation.

3.1.2 Installing Unwired Orchestrator 5.0 on Windows XP Professional Edition

CR # 394111

Problem: When VPN is running and you install the Unwired Orchestrator 5.0 Production Edition with Database Event Management on Windows XP Professional with service package 2, you cannot start the Unwired Orchestrator server.

When VPN is active, the installer picks up vpnlinux as the machine name instead of the actual machine name.

Workaround: Do the following procedure.

To start up Unwired Orchestrator 5.0 Production Edition:

Open the <installation directory>\Orch-5_0\EAServer\bin\setenv.bat file.

Replace vpnlinux with <your machine name>.

Open the following file:

<installation directory>\Orch-5_0\EAServer\bin\UO50ASACache.props

Replace vpnlinux with <your machine name> in the following properties:

com.sybase.jaguar.conncache.remotesvrname=jdbc:sybase:Tds:vpnlinux:8202/UO50Runtime

com.sybase.jaguar.conncache.xa.remotesvrname=jdbc:sybase:Tds:vpnlinux:8202/UO50Runtime

Start Unwired Orchestrator. Select Start | Programs | Sybase | Unwired Orchestrator 5.0 | Start UO5.0 Runtime.

3.1.3 Installing Adaptive Server Enterprise 15.0

CR # 400975

Description: If you plan to use Adaptive Server Enterprise (ASE) 15.0 with the Sybase WorkSpace and already have ASE 12.5.3 installed, deployment problems arise when both versions of ASE are installed in the Sybase WorkSpace directory.

Workaround: Install ASE 15.0 in a Sybase WorkSpace directory that is different than ASE 12.5.3.

3.1.4 Installing the Enterprise Modeling Tutorial

To use the Enterprise Modeling tutorials, you must install Sybase WorkSpace TX, TX Enterprise, or Evaluation edition.

3.1.5 Standalone EAServer Patch Installation

Description: A new patch exists for EAServer 5.2.

Resolution: In Chapter 2: Installation Planning, in the section Installing Unwired Orchestrator with a Standalone EAServer Installation, after you complete the step to install the EAServer EBF#1, do the following procedure to download the latest EAServer patch.

Note:

This procedure applies only to a standalone implementation of EAServer with Sybase WorkSpace.

To download the EAServer patch and continue with the installation:

Go to the EBFs/Maintenance section of the Sybase Support Page.

Download EBF 12976 (for Windows) or EBF 12977 (for Solaris).

Install the patch, following the instructions in the downloaded readme.

Continue with the rest of the steps as directed in the Unwired Orchestrator Installation Guide.

3.1.6 Sybase WorkSpace EAServer Patch Installation

Description: Sybase WorkSpace includes EAServer 5.2, Unwired Orchestrator 5.0, and Unwired Accelerator (EAServer) 7.0. These development edition servers all include EAServer. A new patch exists for EAServer as its used within these products.

Resolution: After you install Sybase WorkSpace, download and install the most recent EAServer patch.

To download the patch and continue with the installation:

Go to the EBFs/Maintenance section of the Sybase Support Page.

Download EBF 12976 (for Windows) or EBF 12977 (for Solaris).

Install the patch, following the instructions in the downloaded readme.

Continue with the rest of the steps as directed in the Unwired Orchestrator Installation Guide.

3.2 Installation Guide documentation updates and clarifications

3.2.1 Sybase WorkSpace

CR # 403827

Description: In the section Installing SybaseWorkSpace, step 9 incorrectly instructs you to insert CD2.

Workaround: When you click Install on the Installation Summary Information page, the installer starts displaying the progress of the installation, which is documented in step 11 of the section Installing SybaseWorkSpace. As the install progresses, you are asked to insert CD2.

3.2.2 Upgrading to Adaptive Server Enterprise 12.5.3

Description: In Upgrading to Adaptive Server Enterprise 12.5.3, the text currently reads:

Download and launch EBF 12461.

Resolution: Alternately, you can find the EBF 12461 file in one of the following locations, depending on whether you are installing from CD or DVD:

- On CD #3: <installation media>\EBF12461.zip.

- On the DVD: <installation media>\ASE 12.5.3\EBF12461.zip.

4. Special configuration instructions

4.1 Setting up the Oracle JDBC driver

To use the Oracle JDBC Driver for Database services, you must set up the Oracle JDBC driver.

To set up the Oracle JDBC driver:

Add the Oracle JDBC driver jar file to the following directory:

<installation directory>\EAServer\java\lib<filename>

Unzip and extract the files to:

<installation directory>\EAServer\java\classes

5. Special license upgrade instructions

5.1 Upgrading from WorkSpace MX or MX Enterprise to WorkSpace TX or TX Enterprise

CR # 401325

Description: When upgrading from a WorkSpace MX or MX Enterprise license to a WorkSpace TX or TX Enterprise license, the installer does not clearly indicate how to install the Conceptual Data Modeling component.

Workaround: A WorkSpace MX or MX Enterprise license enables the installation of Physical Data Modeling, a Data Modeling component. However, when you upgrade to a TX or TX Enterprise license, you must select to reinstall Data Modeling to enable the installation of the Conceptual Data Modeling component provided by a TX or TX Enterprise license.

6. Port conflicts

After installing Sybase WorkSpace, use the following workarounds to resolve potential port conflicts.

6.1 Resolving port conflicts with the EAServer and Tomcat versions of Unwired Accelerator

CR # 401510

Description: A full installation of Sybase WorkSpace includes both Unwired Accelerator (Tomcat) and Unwired Accelerator (EAServer) and both servers use port #4040.

For example, because Unwired Accelerator (EAServer) deploys to EAServer, when you start EAServer, Unwired Orchestrator, or Unwired Accelerator (EAServer), port 4040 is taken and you cannot start Unwired Accelerator (Tomcat).

Workaround: To use both Unwired Accelerator servers, modify the HTTP port number for EAServer.

To change the HTTP port number for EAServer:

Start EAServer, EAServer Manager, and connect to EAServer.

Right-click the httpUA listener and select Properties. Change the port number to the port for EAServer.

Do the same for the httplocal listener. Change the port number to the same number as defined for the httpUA listener.

Shutdown EAServer, Unwired Orchestrator, and Unwired Accelerator (EAServer).

Restart EAServer, Unwired Orchestrator, Unwired Accelerator (EAServer), and start Unwired Accelerator (Tomcat).

You should have all the servers that use EAServer running on the port you changed to, and Unwired Accelerator (Tomcat) running on port 4040.

See the EAServer System Administration Guide on the Sybase WorkSpace online bookshelf for more information.

6.2 Resolving a Sybase WorkSpace help port conflict

Description: A port conflict may occur with a Sybase application or independent software vendor (ISV) application when launching the Sybase WorkSpace Help. The following error appears:

Embedded server could not be started.

Workaround: If you experience a port conflict when launching Help, close and restart Sybase WorkSpace.

6.3 Resolving a UDDI Registry database port conflict

CR # 400892

Description: The JUDDIServerCache connection cache in EAServer is configured to use port 4545.

This port number does not match the port used in the Start script for the database server that hosts the UDDI registry database. Because the Start script leaves the port unspecified, the result is the default ASA port (2638) is used.

Workaround: Edit the Start script to specify that the database use port 4545.

To change the Start script:

Open the following file:

<installation directory>\DevRuntimes\UO\bin\ startUO50uddidb_asa.cmd

Edit the following line:

START "Start UDDI db" "%ASA_HOME%\dbsrv9.exe -n %DB_NAME% "%DB_LOC%\%DB_DATA%"

Specify the correct port:

START "Start UDDI db" "%ASA_HOME%\dbsrv9.exe" -n %DB_NAME% "%DB_LOC%\%DB_DATA%" -x tcpip(ServerPort=4545;doBroadcast=no)

See Changing the Sybase WorkSpace UDDI Server Port on the Sybase WorkSpace online bookshelf for more information.

6.4 Resolving an EAServer port conflict

CR # 389777

Description: Before deploying services to EAServer, verify that port number 1099 is not used by another application.

Workaround: If port number 1099 is being used by another application, change the SYBAGENT configuration.

To change the SYBAGENT configuration:

Open the boot.xml file. Choose from the following:

Table 1: boot.xml file

Server edition

File location

Production

<installation directory>\Orch-5_0\EAServer\ SysMgmt\boot.xml

Edit the boot.xml file.
[Unmapped FQGI: TECHDOC RBULLETIN SECTION SECTION PROCEDURE STEPS STEP SUBPROCEDURE DESCRIPTION ]
Do the following:
1. Insert the following attribute on line 55:
  
  <attribute name="Port">1399</attribute>
  
  Port value 1399 replaces the default port value of 1099.
2. Replace the port number in line 78 to the same port you used in line 55. For example:
  
  <param type="java.lang.Object">rmi://banglor:1399</param>

Open the StopSybAgent.bat file. Choose from the following:

Table 2: StopSybAgent.bat file

Server edition

File location

Production

<installation directory>\Orch-5_0\EAServer\ SysMgmt\bin\StopSybAgent.bat

Edit the StopSyb Agent.bat file. Replace the port number on line 24 with the port number you used in the boot.xml file.

Table 1: boot.xml file
Server edition	File location
Production	<installation directory>\Orch-5_0\EAServer\ SysMgmt\boot.xml

Table 2: StopSybAgent.bat file
Server edition	File location
Production	<installation directory>\Orch-5_0\EAServer\ SysMgmt\bin\StopSybAgent.bat

7. Sybase WorkSpace Development Issues

7.1 General WorkSpace issues

7.1.1 Using the Revert File option in the XML Editor

CR # 402257

Description: When you want to revert pending changes to a document you are editing using the XML Editor, the Revert File context menu option does not work.

Workaround: Either use Edit/Undo from the context menu or close the document without saving.

7.1.2 Minimizing a welcome page

CR # 391835

Description: When you minimize a welcome page, it appears as a blank window.

Workaround: Click the Restore icon to make the welcome page visible in minimized view.

7.1.3 VNC Viewer causes WorkSpace UI sizing problems

CR # 396716

Description: If your machine is connected through VNC Viewer, the WorkSpace UI has component sizing problems.

Workaround: Do not run the Sybase WorkSpace UI through the VNC Viewer.

7.1.4 Errors exporting a project template

CR # 401341

Description: If you did not refresh your project before attempting to create a template from a project, the template may not be created. When you select Finish in the New Project from Template wizard, nothing happens. Errors will appear in the log file.

Workaround: Do the following:

To export a project as a project template:

Highlight the project in the WorkSpace Navigator and then select File| Refresh from the main menu bar.

This ensures the project in the workspace is in sync with the file system.

Export the project as a template.

7.1.5 Accessing the online help while using a wizard

CR # 400966

Description: If you are using a wizard and you want to refer to the online help at the same time, you must exit the wizard to open the Sybase WorkSpace bookshelf.

Workaround: Open the online help in an external browser.

To access online help while using a wizard:

Select Window|Preferences from the menu bar to display the Preferences dialog box.

Select Help in the left pane.

Select Always use external browsers.

Note:
If the selected browser is not fully compatible with Internet Explorer or Mozilla, or if JavaScript is disabled, the help topic shown in the browser may not appear as intended.

(Optional) Choose one of the following:
- In the Current external browser adapter list box, select the browser.
- If your system does not have any supported browser adapters installed, only the Custom Browser (user-defined program) in the list box appears. To specify a path to the browser program that launches your browser:
  - Select Custom Browser.
  - Enter or browse for the path in the Custom Browser command field.
    
    If the program is available on your system path, you can specify only the program name. If the program does not accept URL as its last parameter, use %1 strong to denote the position of the URL parameter in the command.

Click OK.

Open a wizard and toggle to the help when needed.

7.2 Samples and Tutorials

7.2.1 Problems creating the MySybStore project

CR # 401378

Description: When the MySybStore_Tutorial or MySybStore_Sample projects are created, the Problems view displays an error and two warnings. The description for the primary warning is:

Class “com.sybase.workspace.tutorials.sybstore.schemas.SalesDetail” in service “SalesProcessingValidateService” will not work in UO servers. The reason is: java.lang.ClassNotFoundException: com.sybase.workspace.tutorials.sybstore.schemas.SalesDetail.

Because the project is built from the template, the Java builder for the project occurs after the Java Service builder. As part of the project build, a clean and rebuild is performed, however during this process the clean occurs, which deletes all the .class files, then the Java Service builder runs, which reports it cannot find the .class file, then the other builders are run, and finally the Java builder is run, which creates the .class file.

Workaround: Move the Java builder to the top of the build list. First, create the project as described in the Tutorial or Sample procedure, then use the following procedure to reorder the project builders.

To reorder the project builders:

From the WorkSpace Navigator, right-click on the project and select Properties.

In the Properties dialog, do the following:
1. Select Builders on the left-hand side; select Java Builder on the right-hand side
2. Click the Up button until the Java Builder entry is at the top of the list.
3. Click OK. The Properties dialog closes.

From the WorkSpace main menu bar, select Project | Clean to clean and rebuild the project.

The errors do not appear in the Problems view.

7.2.2 Sample services fail to test due to invalid SOAP addresses in WSDL

CR # 403186

Description: In the SybStore_Sample resources, there are services with WSDL documents that are invalid because they contain a SOAP address with a hardcoded value inappropriate for your environment.

For example:

<soap:address location="http://CBLATHER-XP.sybase.com:8180/SalesBPService/services/SOAPHandler/HTTPTransport/urn~3Amycompany~3A/SybStore_Sample/Services/BP/SalesBPService/SalesBPService"/>

If you right-click any of the invalid WSDL files and select Test Service, the test fails.

Workaround: Do one of the following:

Edit the WSDL file and change the location, for example, location="http://CBLATHER-XP.sybase.com:8180/" to the correct Unwired Orchestrator hostname and http listener port for your environment.

Deploy the service package to your Unwired Orchestrator server, then test the resulting WSDL.

7.2.3 Location of mobile application on UA server

CR # 403196

Description: In Tutorials, Chapter 5: Mobile Development Tutorials, Deploying a Mobile Application, Lesson 1: Deploying to a Blackberry Device, step 6, the text currently reads:

In the WorkSpace Navigator, right-click on the ListAllItems_usingSelect mobile application.

Resolution: The text should read:

In the WorkSpace Navigator, select MyMobileServer|MobileApplications|Approved, then right-click on the ListAllItems_usingSelect mobile application.

7.2.4 Starting the MySybStore Database

CRs # 403194, 403201

Description: In Tutorials, Chapter 1: Introduction and Setup, Tutorial Setup, Sybase WorkSpace Tutorial Setup, Starting the MySybStore Database, step 6, the text currently reads:

The Adaptive Server Anywhere, Enterprise Version pop-up appears.

Resolution: The text should read:

The Adaptive Server Anywhere, Developer Edition pop-up appears.

A similar misprint occurs in Samples, Chapter 2: Installing the Sample Application, Start the Sample Database, step 6, Introduction and Setup, Tutorial Setup, Sybase WorkSpace Tutorial Setup, Starting the MySybStore Database, step 6. The resolution is identical.

7.2.5 Starting the Unwired Accelerator Server

CRs # 403195, 403203

Description: In Tutorials, Chapter 1: Introduction and Setup, Tutorial Setup, Mobile Development Tutorial Setup, Starting the Unwired Accelerator Server, step 2, the text currently reads:

Select Programs|Sybase|Sybase WorkSpace|UA 7.0|Start UA.

Resolution: The text should read:

Select Programs|Sybase|Sybase WorkSpace|UA 7.0 and select Start UA (EAServer) or Start UA (Tomcat), depending on which Mobile Development options you chose at installation.

A similar misprint occurs in Samples, Chapter 2: Installing the Sample Application, Start the Unwired Accelerator Server, step 2. The resolution is identical.

7.2.6 Deploying to a Blackberry Device

CR # 403197

Description: In Chapter 5: Mobile Development Tutorials, Deploying a Mobile Application, Lesson 1: Deploying to a Blackberry Device, in the Conclusion section, the text currently reads:

You have finished deploying a mobile application and making it available for offline BlackBerry access.

Resolution: The text should read:

You have finished making a mobile application available for offline Blackberry access.

7.2.7 Start the sample database

CR # 403200

Description: In Chapter 2: Installing the Sample Application, Start the Sample Database, in step 3, the following note is missing:

If you selected a location for your workspace folder other than the default (<installation directory>\Eclipse\workspace), edit the path to the MySybStore.db file to reflect that change.

7.2.8 Setting up Mobile applications

CR # 403204

Description: In Chapter 3: Running the Sample Application, Setting Up Mobile Applications, step 5, the text currently reads:

Normally it is the MobileApplications\ExportedMobileApps.ua file.

Resolution: The text should read:

Normally it is the MobileApplications\ExportedMobileAppls.ua file.

7.2.9 Editing an endpoint for a message service

CR # 403220

Description: In Tutorials, Chapter 4: Service Development and Business Process Orchestration Tutorials, Service Development Tutorials, Creating a Message Service, Lesson 2: Verify Service Parameters, Prerequisites section, the text currently reads:

You must edit the endpoint of the pre-built service for the service to work correctly.

Resolution: The text should read:

You must edit the endpoint of the pre-built service for the service to work correctly, using the instructions found in the online help topic Editing an Endpoint for a Message Service.

7.2.10 Testing a service

CR # 403221

Description: In Tutorials, Chapter 4: Service Development and Business Process Orchestration Tutorials, Service Development Tutorials, Packaging, Deploying, and Testing a Service, Lesson 3: Test a Service, step 1, the text currently reads:

In the Enterprise Explorer, right-click MySalesEmailSend and select Test Service from the context menu.

Resolution: The text should read:

In the Enterprise Explorer, right-click Services/MySalesEmailSend and select Test Service from the context menu.

7.2.11 Creating a Simple Business Process tutorial

Description: In the Lesson 4: Defining Error Handling for a Business Process Service, all the elements you must select in step 14 are not documented.

Resolution: Step 14 should read:

Set the properties of the renamed setErrorInfo Assign activity as follows:

For the first Assign, set the Source to a literal, FAILURE. Set the Target to:

Interface:MySalesBPService:MySalesBPService/ManageInventory/Response/ outputResponse /SalesDetailResponse/ProcessingResult.

For the second Assign, set the Source to a literal, invalid sales item. Set the Target to: Interface:MySalesBPService:MySalesBPService/ManageInventory/Response/outputResponse /SalesDetailResponse/FailureReason.

7.2.12 Miscellaneous corrections in Samples

CR # 403234

Description: In Samples, Chapter 2: Installing the Sample Application, Create the Sample Project, step 8, the text currently reads:

From the WorkSpace main menu bar, select Project|Clean to clean and rebuild the project.

Resolution: The text should read:

From the WorkSpace main menu bar, select Project|Clean to clean and rebuild the project, then respond Clean Selected Project at the prompt.

Description: In Samples, Chapter 2: Installing the Sample Application, Create a Connection Profile for the Sample Database, step 6, the ASA password *** is not given:

Resolution: The text should read:

The default Password is sql, which appears as *** in the dialog box. You do not need to change the password.

Description: In Samples, Chapter 2: Installing the Sample Application, Start the Unwired Accelerator Server, step 2, the text currently reads:

Select Programs|Sybase|Sybase WorkSpace|UA 7.0|Start UA

Resolution: The text should read:

Select Programs|Sybase|Sybase WorkSpace|UA 7.0, then select Start UA (EAServer) or Start UA (Tomcat), depending on the Mobile Development options you selected during installation.

Description: In Samples, Chapter 3: Running the Sample Application, Deploying and Testing Services, SalesDBService, step 4, the text currently reads:

Select the test method called SOAP Dialog Service Test Wizard.

Resolution: The text should read:

Select the test method Dialog Service Test Wizard.

Description: In Samples, Chapter 3: Running the Sample Application, Deploying and Testing Services, SalesEmailSend, step 5, the text currently reads:

5. Click Edit and then Edit again on the Complex Type dialog.

Resolution: The text should read:

5. Click Edit on the Complex Type dialog and provide the following values:

ItemNum: A6459
RestockQty: 2

6. Click Edit again on the Complex Type dialog to enter other optional values.

Description: In Samples, Chapter 3: Running the Sample Application, Deploying and Testing Services, SalesEmailSend, To deploy and test SalesEmail Send, step 1, the text currently reads:

In the Message Service editor, Service Interface panel, right-click the endpoint icon and select Edit Endpoint from the context menu.

Resolution: The text should read:

With the SalesEmailSend service open in the Message Service Editor, select the Service Interface panel, right-click the endpoint icon, and select Edit Endpoint from the context menu.

Description: In Samples, Chapter 3: Running the Sample Application, Deploying and Testing Services, SalesEmailSend, To deploy and test SalesEmail Send, step 2, the text currently reads:

Select the send operation, and open the Properties view.

Resolution: The text should read:

Select the send operation, open the Properties view, and select the Operation context tab.

Description: In Samples, Chapter 3: Running the Sample Application, Deploying and Testing Services, SalesEmailSend, To deploy and test SalesEmail Send, step 8, the text currently reads:

Click Edit and then Edit again on the Complex Type dialog.

Resolution: The text should read:

Click Edit on the Complex Type dialog.

7.2.13 Miscellaneous corrections in the Tutorial

CR # 403236

Description: In Tutorials, Chapter 1: Introduction and Setup, Tutorial Setup, Sybase WorkSpace Tutorial Setup, Creating the MySybStore_Tutorials Project, step 5, the note currently reads:

When the MySybStore_Tutorial or MySybStore_Sample project are created, the Problems view may display an error and two warnings.

Resolution: The text should read:

When either the MySybStore_Tutorial or _Sample project is created, the Problems view may display an error and two warnings.

Description: In Tutorials, Chapter 1: Introduction and Setup, Tutorial Setup, Sybase WorkSpace Tutorial Setup, Creating the MySybStore_Tutorials Project, after the note, in step 3, the text currently reads:

From the WorkSpace main menu bar, select Project|Clean to clean and rebuild the project.

Resolution: The text should read:

From the WorkSpace main menu bar, select Project|Clean to clean and rebuild the project, responding Clean Selected Projects when prompted.

Description: In Tutorials, Chapter 3: Database Development Tutorials, Running a SQL Script, Lesson 1: Open and Run a SQL Script, step 2, in the screen capture, the Select Profile for the Editor dialog box currently displays the database connection profile name as:

SybStore

Resolution: The database connection profile name is:

MySybStore

Description: In Tutorials, Chapter 4: Service Development and Business Process Orchestration Tutorials, Service Development Tutorials, Creating a Database Service, Lesson 1: Create a Database Service, step 7, the text currently reads:

The Database Service Introduction page appears.

Resolution:

Click Finish in the Create a Service wizard. The Database Service Introduction page appears.

Description: In Tutorials, Chapter 4: Service Development and Business Process Orchestration Tutorials, Service Development Tutorials, Creating a Transformation Service, Lesson 2: Define Mapping for a Transformation Service, step 25c, the text currently reads:

Select literal_1 and, in the Properties Panel, change its name to Float Value.

Resolution: The text should read:

Select literal_1 and, in the Properties Panel, change its name to Float Value and change its Literal Value to 0.0.

Select literal_2 and, in the Properties Panel, change its Literal Value to 0.

7.2.14 Incorrect tool palette specified

CR # 403397

Description: In Chapter 4: Service Development and Business Process Orchestration Tutorials, Service Development Tutorials, Creating a Transformation Service, Lesson 2: Define Mapping for a Transformation Service, step 12, the text currently refers to an incorrect tool palette:

Generic Variables and Constants tool palette

Resolution: The correct tool palette is:

Constants tool palette

7.2.15 Using SalesDBService

CR # 403551

Description: The MySybStore_Tutorials project provides a pre-built proxy file that is based on the pre-built SalesDBService. If this proxy file, SalesProcessingDBServiceProxy.java located in the mycompany folder, exists when the sybstore_validate_salesdata operation is dragged onto the SalesValidate Java service, the proxy is not re-generated with correct references to the interface name. When the Java service is deployed, the service fails due to this issue.

Workaround: Add the following Prerequisite to Lesson 2: Invoke a Database Service from Java Service Operation.

If you use the pre-built database service, SalesDBService.svc_db, complete the following before starting this lesson:

I n the WorkSpace Navigator, locate MySybStore_Tutorials | mycompany | SalesProcessingDBServiceProxy.java.

Right-click SalesProcessingDBServiceProxy.java and select Delete.

As you complete Lesson 2, you will see the proxy generate as described in the Tutorials documentation.

7.3 Cheat Sheets

Cheat Sheets are a feature of the Eclipse platform implemented with Sybase WorkSpace 1.0. A cheat sheet is a view that opens in a perspective to guide you through complex tasks, such as Developing a Message Service, Developing a Java Service, Developing an ASA Trigger, and Developing a Web Services Mobile Application.

After launching a cheat sheet, you use the cheat sheet steps to perform work or to guide you through work in the tooling.

To use cheat sheets effectively, it is important that you:

Click the Begin icon in the cheat sheet Introduction to start working through the steps in the cheat sheet.
Complete each step in the cheat sheet in the order presented.
For each step, click the Perform icon or follow the instructions to complete the work yourself.
As you complete a step, click the Complete icon to continue to the next step.
Click the? icon if you want more information about a step.

To launch a cheat sheet, select Help | Cheat Sheets from the main menu bar. The cheat sheet selection dialog appears where the cheat sheets are categorized according to development component.

Within any category, you can select Using Cheat Sheets in Sybase WorkSpace to open a cheat sheet that will walk you through how to use cheat sheets effectively.

7.4 General Service Issues

7.4.1 Character limitations on the length of package names

CR # 400927

Description: If you install Sybase WorkSpace using the default directory (C:\Sybase\WorkSpace) and subsequently name service packages that exceed 31 characters in length, you will receive errors and warnings in EAServer Manager and log files.

Workaround: Use under 31 characters to name all service packages.

7.4.2 Inadequate error message when service not available

Description: When a service is unavailable, non-descriptive error messages are logged in the server runtime log.

Example messages are:

Failed to get MessageHandler for Action urn:mycompany:/<PROJECT NAME>/<PACKAGE NAME>/<SERVICE NAME>/<REQUEST MESSAGE NAME>
org.apache.wsif.WSIFException: No method named '<OPERATION NAME>'

found that match the parts specified...followed by a SOAP envelope, the body of which contains the request message with the default namespacexmlns="urn:mycompany:/<PROJECT NAME>/<SERVICE NAME>”

Workaround: The service may not be available. Confirm the availability of the service and ensure that the following attributes of the service that is being invoked match with the deployed service: Package name, Service name, and target namespace.

Note:

A service with the correct name but different values for the package name or target namespace is recognized, but generates an error message when the service is invoked.

7.4.3 Renaming a resource file while the associated editor is open

CR # 399298

Description: Renaming a service file when the associated service editor is open results in all associated resources, dependencies, and references not reflecting the change.

Workaround: Do not rename a service file when its associated editor is open.

7.4.4 XML positiveInteger values are serialized incorrectly

CR # 398151

Description: If you have fields that use the XML positiveInteger type in outbound XML formatted messages from a service, the field serializes incorrectly with an additional lowestSetBit attribute in the XML, and the XML fails validation if consumed by a validating parser.

The issue does not arise during standard service development, but may cause problems if you send messages to an external process or server that runs a validating parser.

Workaround: Do one of the following:

Change the XSD allowed for validation to allow the lowestSetBit attribute in the XML.
Change the data to use the integer type instead of positiveInteger.
Reconfigure the consuming process to run without validation.

7.4.5 Only single thread access is supported for inbound file transports

CR # 400433

Description: When a package containing two or more services that are configured to use an inbound File transport is deployed, Sybase WorkSpace locks and the CPU usage of the system increases to 100% and remains there.

Workaround: Verify that the inbound file transport defined for each service is a different file transport. Only single thread access is supported for inbound file transports. Therefore, if two or more services are publicly accessible using a file transports, each must be defined to use a separate file.

7.5 Business Process service

7.5.1 DateTime Comparisons

CR # 401270

Description: When comparing the value of a dateTime field to the dateTime constant or a variable, Sybase WorkSpace does not always return True even when the condition is True. For example:

getVariableData('BP11243231409382', 'newParameter1', '/ns0:CT/ns0:dateTime') < '2005-08-17T18:00:00'

Workaround: Convert the dateTime field values to ISO dates or times. The ISO format puts the number in a sequence, such as YYYYMMDDHHMMSS, without any of the annotations that are present in the format used by XSD Schema types. When dates and times are in this format, you can compare the two integers to identify which dates are newer or older.

For example, if you have a dateTime format, such as 2005-08-17T18:00:00, you can perform the following operations on that string to convert it to an ISO dateTime:

where dateTime = 2005-08-17T18:00:00

result =

concat(

concat

(

concat

(

substring(dateTime, 1, 4),

substring(dateTime, 6, 2)

concat

(

substring(dateTime, 9, 2),

substring(dateTime, 12, 2)

)

concat

(

substring(dateTime, 15, 2),

substring(dateTime, 18, 2)

)

This operation would yield result = 20050817180000. Convert this string to an integer using number ( ) and round ( ) functions, round(number(result)), which could then be used as an integer in a comparison.

7.5.2 Correct values are not returned if the ceiling function is less than zero

CR # 397654

Description: This problem occurs in Jaxen versions 1.0, 1.1, and the Beta 6 version.

If the argument of the ceiling function is less than zero, but greater than negative one, the correct value is not returned. For example, the ceiling value of -0.5 converts to -0.0 stored in a java.lang.Double object. The zero value is also converted to a java.lang.Double object with the value 0.0. When the two are compared using the equals operator on the java.lang.Double object, the result is incorrectly reported as False.

Workaround: Use the following procedure.

To correct the problem:

Assign the ceiling of the value to a local variable.

Run the comparison to that variable.

7.5.3 Substring-after and substring-before function arguments with leading zeros

CR # 399122

Description: Substring-after and substring-before functions do not always give the correct output if the argument strings have leading zeroes. The leading zeroes are deleted.

Workaround: Perform the operations using a map.

7.5.4 Exception Handler does not fire if an exception is thrown from Fault Handler

CR # 401773

Description: If a fault or exception is thrown from within a Fault Handler or an Exception Handler activity, other Fault Handlers and Exception Handlers located within the same scope do not fire.

Workaround: If the Fault Handler or Exception Handler throwing the fault or exception is placed inside a Complex activity, the Fault Handler or Exception Handler catches the fault or exception.

Do one of the following:

Move the Exception Handler that is catching the exception thrown from the Fault Handler out of the Complex activity into the next higher scope.

If the handler is in the root scope, add a Complex activity and move all the associated activities, excluding the Exception Handler, into the Complex activity.

7.5.5 Undoing an activity deletion

CR # 399341

Description: If you delete an activity from the business process editor and then use the Undo command, all objects associated with the activity are not restored, causing the business process to fail at runtime.

Workaround: After you perform an undo of a delete, disconnect and then reconnect the activity’s associated inputs and outputs.

7.5.6 XPath number function

CR # 390946

Description: The XPath number function does not return the numeric value of the given argument if it is of a Boolean type. For example, if you create an input parameter, connect it to number function, and connect this to an output parameter in an Assign, you would not see the expected results.

Workaround: Use the following method to produce the correct results for the above example.

To convert a Boolean argument to a number in an Assign:

Create an input Boolean parameter.

Create an output Float parameter.

Activate the Tool Palette.
- Click inside the editor.
- Click the Tool Palette icon on the Fast View shortcut bar and select the Activities tool palette.

Drag and drop an Assign activity onto the canvas.

From the Business Process Variables section, drag the parameter you want to use as the source and drop it into the Source cell of the Assign properties.

From the Business Process Variables section, drag the parameter you want to use as the target and drop it into the Target cell of the Assign properties.

Click the Assign tab in the Properties Panel for the Assign.

Click in the Expression editor to activate the Tool Palette.

Select the Boolean Functions tool palette, drag IsEqualTo, and drop it onto the Expression editor.

From the Generic Variable and Constants tool palette, drag String Constant, and drop it onto the Expression editor.

Highlight String Constant in the editor, and change the Logical name property to True. Select the check box next to Source text to keep the Logical name and Source name the same.

Change the data type to Boolean.

From the Number Functions tool palette, drag number and drop it onto the Expression editor.

Connect the following to create the flow:
1. Connect the input variable to IsEqualTo.
2. Connect True to IsEqualTo.
3. Connect IsEqualTo to the number.
4. Connect the number to the output variable.

7.5.7 Assign tab displays blank with certain conditions

CR # 401032

Description: Using the Variable Reference Dialog to select parameters of an invoked service operation after it is dropped into a complex activity causes the Assign tab to become blank. The Variable Reference Dialog displays when you click the ellipse ... in the Source or Target cell of an Assign.

Workaround: Drag parameters from the Business Process Variables section of the Business Process editor and drop them into Assign table cells. Do not use the Variable Reference Dialog to select parameters. This restriction is necessary only the first time parameters of a newly dropped operation are to be used in the Assign tab.

7.5.8 Mapping an indexed repeating source to an indexed target in a business process

CR # 401250

Description: The Business Process Service editor does not have a built-in facility for mapping a repeating element and assigning different values to target elements depending on values in the source data.

Workaround: If you need to map an indexed repeating source, you must do this in the Transformation Service editor by mapping the repeating elements, then using the If and Then conditional logic functions in the Expression editor (located in the Map tab, in the Transformation Rule section) to control the repeating elements. For example, using the If and Then functions, you can express logic such as the following:

If weight > 1000 Then set status to overweight else set status to OK.

If the element on which you want to define the conditional transformation is not itself repeating, but its parent is repeating, then you should first connect the parent elements, then connect the child elements and define the conditional transformation on the link to the element using the Expression editor.

7.5.9 Loop termination condition is misleading

CR # 397858

Description: Loop Termination Condition is mislabeled. When you select Loop Termination Condition, when the condition is False, the loop terminates, so it is actually not a termination condition, but a loop-run or continuation condition.

Workaround: Use Loop Termination Condition to continue iterating in a Complex activity.

7.5.10 Extremely large message definitions may not generate successfully

CR # 401726

Description: Extremely large message definitions that contain several hundred nodes may not successfully generate the necessary classes for custom wire format message processing, resulting in the following error:

Message.wfim (Error: Compile Failed)

Compile Failed

com.sybase.jtf.jso.JSOException: Compile Failed

com.sybase.jtf.jso.xsd.CodeGenerator$JavaImp.compile(CodeGenerator.java:130)

com.sybase.jtf.jso.xsd.CodeGenerator.compile(CodeGenerator.java:429)

com.sybase.jtf.jso.xsd.Generator.compile(Generator.java:424)

com.sybase.jtf.fedit.core.builders.MDArtifactWrangler.generateJSO(MDArtifactWrangler.java:751)

com.sybase.jtf.fedit.core.builders.MDArtifactWrangler.generateAll(MDArtifactWrangler.java:1026)

com.sybase.jtf.fedit.core.actions.GenerateMsgDefinitionsAction.generateMessage(GenerateMsgDefinitionsAction.java:119)

com.sybase.jtf.fedit.core.actions.GenerateMsgDefinitionsAction$InstallJob.run(GenerateMsgDefinitionsAction.java:176)

org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

Workaround:

Do the following:

Remove unused nodes from the message definition.

Regenerate the definition.

Note:
If no nodes can be removed or if message generation fails, consolidate groups of fields into single fields and split the field values in a transformation service.

7.5.11 Using local variables

CR # 402376

Description: To transform or manipulate a local variable defined in a Business Process service in an Assign activity using the Expression editor, use the following guidelines:

Use globally defined variables as the source of the Assign. Even within a Complex activity, use variables defined globally to the business process, and not variables scoped to the Complex activity.
Always drag-and-drop local variables from either the Business Process Variables section of the editor or the Variables Panel view into the Source cell of the Assign activity. Do not use the Variable Reference Dialog that appears when you click the ellipsis in the Source cell of the Assign.

7.5.12 Apostrophes are not escaped in assignments

CR # 403328

Description: When apostrophes are used as part of a literal in an Assign, the apostrophes are not escaped correctly in the translator.

Workaround: Create a transformation service to replace an Assign that requires an apostrophe in a literal. Map a String Constant as the source of the transformation to the String target.

7.5.13 Correlation set error

CR # 403794

Description: If business process correlation keys match, but correlation does not occur, check the Jaguar log for the following error:

No StaticRegistration found for key value

In this case, the error indicates that the staticKeyValue exceeded 100 characters in the business process. The staticKeyValue is created by combining <Target name space>+<Service name>+<operation name>. If the staticKeyValue exceeds 100 characters, it is truncated to 100 characters.

Workaround: Use Target name space, service, and operation names that, when combined, do not exceed 100 characters.

7.5.14 Problem with two stateful business processes in the same package

CR # 403833

Description: Deadlocks can occur when stateful business process #1 invokes stateful business process #2. This occurs when the invokes are in the same package (the same transaction) and multiple threads invoke the services.

Workaround: Break the transaction between business process #1 and business process #2 by wrapping business process #2 with a SOAP service.

7.6 Database service

7.6.1 Problems using JDBC and DB2 version 7

CR # 389255

Description: You may experience problems using JDBC and DB2 version 7.

Workaround: Check the DB2 product documentation for more information.

7.6.2 Using an Oracle database

CR # 401643

Description: When using Oracle, the database provides time zone information in their TIMESTAMP data type; however, JDBC does not provide for time zone information, so a class cast exception results.

Workaround: You may want to use a third party driver, such as the DataDirectJDBC driver for Oracle, if database operations have result sets with a TIMESTAMP column.

7.6.3 Creating an ODBC data source for an ASA connection profile

CR # 383224

Description: You need an ODBC data source for use with any ASA connection profile you create.

Resolution: Use the following steps to create the appropriate ODBC data source.

To create an ODBC data source:

Select Start | Control Panel | Performance and Maintenance (Windows XP only) | Administrative Tools | Data Sources (ODBC).

In the File DSN tab, click Add.

In the Create New Data Source dialog, select ASA 9.0, which is the driver for the database to be used in Modeling, then click Next.

For the file data source name, enter asaDemo and click Next, then click Finish.

In the Logon to Sybase dialog, specify the database details. In the ODBC Data Source Administrator dialog asaDemo is now displayed in the menu.

Launch Sybase WorkSpace and open the Enterprise Modeling perspective.

Select Repository | Connect from the main menu bar.

Click Setup.

Enter a new repository name.

Click DataSource Name and specify the File DSN you just created. You can now connect to ASA.

To use the ODBC data source for a physical model:

Select Database | Connect from the main menu bar.

Click Add.

Click DataSource Name and specify the File DSN you just created. You can now connect to ASA.

7.6.4 Using a storedProcedure that returns an update count from an Oracle database

CR # 389565

Description: An issue exists when using a StoredProcedure that returns an update count from an Oracle database. When the database service runs, it returns an update count for any operation; combined with the known Oracle issue related to how Oracle handles update counts, this results in the procedure running in an infinite loop.

Workaround: Use a SQL statement instead of a stored procedure to perform work in the database service.

See the Oracle product documentation for additional information regarding this issue.

7.6.5 A select statement sometimes returns an update count for each row

CR # 380113

Description: When a stored procedure or SQL statement executes a select * statement, an update count is sometimes returned for each row.

Workaround: Ignore the update counts if they are not necessary for your result.

7.6.6 Result sets contain date and time columns set to timestamp

CR # 392641, 392846

Description: If a select statement is used to generate a database service and the result set contains columns with date or time datatypes, the date and time columns are returned with their type incorrectly set to timestamp.

Workaround: Manually correct the type values for any rows of the result set in the Edit Result Set dialog box. After making this edit, if you then edit the SQL statement, the result set may be regenerated, resetting the type to the incorrect value.

7.6.7 Editing endpoint of database service removes operations currently there

CR # 398998

Description: Changing the endpoint of a database service using the Database Service editor removes all service operations. For example, switching from a development database to a deployment database.

Resolution: To change the endpoint of a database service and ensure retention of the existing service operations, edit the endpoint at the package level rather than using the service editor.

If you change the endpoint in the Database Service editor and then restore the removed service operations using Undo, you may experience runtime errors resulting from a mismatch between the endpoint and the service operations.

7.6.8 Result sets display some blank data types

CR # 401527

Description: In the Type column of the Edit Result Set dialog box, some data types appear blank, but the result set actually contains the correct information.

Workaround: In the Edit Result Set dialog, edit a row that has a blank datatype. The data type displays correctly in the Edit Column dialog box. The result set returns properly at runtime.

7.7 Java service

7.7.1 Using classes starting with ArrayOf

CR # 401122

Description: When you create a Java service using classes that begin with ArrayOf, an error message appears in the Problems view.

Workaround: Do not create a Java service using classes that begin with ArrayOf.

7.7.2 Service invocations, direct or via SOAP wrapper, are exclusive

CR # 398601

Description: The service editor does not issue a warning that service invocations of a service and a SOAP wrapper to that service are exclusive.

Workaround: A Java service cannot simultaneously include invocations of a service and a SOAP wrapper to that service. This is due to the fact that the generated proxy classes will have identical names, but different interfaces for the two invocations. The proxy that is generated last overwrites the former if they are contained in the same project. If the proxies are generated in different projects, then the import statements are in conflict.

7.7.3 Browse dialog crops buttons if parameter package name is long

CR # 389875

Description: The Browse dialog crops the OK and Enter buttons when the package name of a parameter is long.

Workaround: To continue after a class is selected, either resize the Browse dialog to access the OK and Enter buttons, or press Enter on the keyboard.

To clear the selection, delete the displayed characters in the text window.

7.8 SOAP service

7.8.1 Enabling service access to the WSDL

CR # 395443

Description: In the SOAP Service wizard, when a secured WSDL is being accessed, the wizard is unable to access the WSDL if the URL address of the WSDL is specified before the security credentials are entered.

Workaround: When defining a SOAP Service, do the following in the Connection Properties page of the wizard:

To enable access to the WSDL:

Enter the User name and Password in the Security Credentials frame before selecting the From URL option.

Select From URL to enable access to the WSDL by the SOAP service.

The available service displays in the text field.

7.9 Transformation service

7.9.1 Receiving XML messages that contain a Date/Time format with a “Z” property

CR # 396301

Description: When Unwired Orchestrator passes an XML message to a Java Transformation Service that contains a Date/Time format with Z property, an exception is thrown.

Workaround: Use one of the following supported Date/Time formats.

2002-05-30T09:30:10
2002-05-30T09:30:10-06:00

7.9.2 Testing a Transformation Service using the Dialog Service Test wizard

CR # 402232

Description: If you create test conditions for an optional target field in a transformation service, then test the service using use the Dialog Service Test Wizard, an optional field appears.

Workaround: Use the SOAP Request/Response Service Test Wizard to test the transformation service.

7.9.3 Editing the properties of a Test Condition in the Transformation Service Editor

CR # 397586

Description: When building a transformation service that includes a Test Condition node and a schema from a custom wire format, the node's Test field must contain an XPath string with proper syntax, that is, there must be a space between any relational operator (for example, !=) and the test value (for example, ").

Workaround: Click the Test Condition node connector, view the Properties Panel, and edit the Test condition so there is a space after the relational operator.

Correct:/ sy2:OrderSummary/Sy2:OrderRef != "/ sy2:OrderSummary/Sy2:OrderRef!= "

Incorrect:

/sy2:OrderSummary/Sy2:OrderRef!= "/ sy2:OrderSummary/Sy2:OrderRef !="

7.9.4 Using applyDefault function in a transformation service

CR # 397813

Description: The Test property must be blank for connectors that use the applyDefault function to connect a source to a target when you always want the target to be created regardless of the source value.

Workaround: All connectors to optional terminal elements or attributes are given a Test property, which checks that the source of the connector is non-empty. If the source is non-empty, the target element or attribute is created; if the source is empty, the target element or attribute is not created. This behavior can be modified by editing the Test property of the connector. If you want the target element or attribute to be created regardless of the value in the source, delete the text in the Test property of the connector. If you use the applyDefault transformation function on a connector to an optional target element, and you always want the target element to be created, delete the text in the Test property.

7.9.5 Connecting correct input nodes to a Boolean transformation function

CR # 398994

Description: If you use a Boolean function, such as IsEqualTo, and you connect a constant to Input 1, you will not be able to package the service.

Workaround: Do not connect a constant to Input 1 of a Boolean function. Constants can only be connected to Input 2.

7.9.6 Mapping an optional source from one custom wire format to another custom wire format

CR # 400453

Description: When defining a transformation service that maps a custom wire format to another custom wire format, optional containers in the source schema cause a runtime error if the container is not present in the input message.

Workaround: Any test conditions on a repeating container child mapping must be removed.

7.9.7 Cannot drag and drop a source onto an If or Then tab

CR # 400576

Description: It is not possible to drag and drop a source element or attribute onto an If or Then tab in the Expression editor of the Transformation Service editor.

7.9.8 Intermittent exception error when testing a transformation service

CR # 400886

Description: When using the SOAP Request/Response Service Test wizard to test a transformation service, every other invocation results in the following error:

java.lang.reflect.InvocationTargetException

Workaround 1: Open the SOAP Inspector view and turn on the SOAP Inspector, then use the SOAP Request/Response Service Test wizard.

Workaround 2: Instead of the SOAP Request/Response Service Test wizard, use either the Dialog Service Test wizard or the Create Web Service Client wizard.

7.9.9 Conditional logic rule in transformation service not created in .map file

CR # 401348

Description: In the Transformation Service editor, if you map a Source string to a Target string and construct an expression on the link that uses a single If node connected to two Then nodes, the resulting map file contains "" instead of the expression. In the Expression editor, the If and Then nodes display decorated with an error indicated by a red X, and you will not be able to package or deploy the service.

Workaround: Select the If tab and each of the two Then tabs. When you return to the Expression tab, the error decorations no longer appear. Save the transformation service.

7.9.10 Multiple If/Then tabs caused by transformation tool palette

CR # 401514

Description: In the Expression editor, when using the Tool Palette to drag and drop functions or constants onto an If or Then tab, the expression may contain multiple If/Then tabs, which cause the transformation service to become invalid.

Workaround: Instead of using the Tool Palette, right-click in the Expression editor and use the context menu to select functions and constants. To fix existing transformation services with multiple If/Then tabs, close and re-open the editor, then verify your expression.

7.9.11 The getTimeZoneID() function always returns 0000

CR # 401702

Description: When using the Dialog Service Test wizard to test a transformation service that calls the getTimeZoneID() function, the Dialog Service Test wizard may send the incorrect time zone to the getTimeZoneID() function, resulting in an incorrect return value of 0000 every time you call the getTimeZoneID() function.

Workaround: Instead of using the Dialog Service Test wizard to test a transformation service that calls the getTimeZoneID() function, use the SOAP Request/Response Service Test wizard or the Create Web Service Client wizard.

7.10 Business Process and Integration

7.10.1 Saving a RepConnector profile in the RepConnector Manager view

CR # 400338

Description: Problems exist retaining the edits made to a RepConnector profile.

For example, if you open RepConnector Manager selecting Window|Show View|Other| Sybase |RepConnector Manager, and you create or edit a RepConnector profile (called localhost:8080) in the Sybase RepConnector view and then close and reopen Sybase WorkSpace, the edits to the profile may not persist.

Workaround: Close and reopen Sybase WorkSpace. Create or edit the RepConnector profile again. The edits persist after the second time.

7.11 Enterprise Modeling (PowerDesigner)

7.11.1 Cannot view icons unless display is set to True Color

CR # 400803

Description: When the Windows display is set to 256 colors, icons within some of the PowerDesigner models may be invisible.

Workaround: Set the Windows display to True Color (16-bit or higher).

7.11.2 Problems with single-rule conditions

CR # 398711

Description: When working with a model of language Sybase WorkSpace Business Process 1.0 in Enterprise Modeling perspective, problems may exist with single-rules.

For example, if you mark the upper branch of a single-rule as False and the lower branch as True and then generate the business process service using this model, when you open the .svc_bpmn file and select the Business Process tab, False appears when you roll the mouse over to the upper triangle of the single-rule and Output appears when you roll the mouse over the bottom triangle.

At runtime although the upper branch is marked as False, it is executed when the single-rule condition evaluates to True and vice versa.

Workaround: Implement the single-rule condition so that regardless of how the single-rule flows are marked, at runtime, the upper branch is executed if the single-rule condition evaluates to True and the lower branch is executed if single-rule condition evaluates to False.

7.11.3 Deployment problems when invoking a Java, transformation, message, or database service

CR # 401780

Description: When working with a model of language Sybase WorkSpace Business Process 1.0 in Enterprise Modeling perspective, if you mark an activity as Invoke New XXX Service where XXX could be a Java, transformation, message, or database service, you may encounter problems during deployment of the business process service generated from this model.

BUILD FAILED:

C:\Sybase\WorkSpace\Eclipse\workspace\ProcessOrder_1\build-ProcessOrder_2.xml:666:

The BPMN file

C:\Sybase\WorkSpace\Eclipse\workspace\ProcessOrder_1\. ProcessOrder_2.bpmn had a dangling namespace urn:Message_Provider_6"

This problem is caused by malformed namespace for the service operation during Business Process Editor files generation.

WorkAround: Do the following procedure.

To correct this problem:

Delete the service operation from the business process service.

Drag and drop the service operation from Service Explorer into the business process service.

7.12 Database Development

7.12.1 Connecting to ASE on HP-UX from Sybase WorkSpace

CR # 400163

Description: Failures occur when connecting the Database Explorer to ASE on HP-UX.

Workaround: Add the following two connection properties to the Connection Profile:

Charset=iso_1Properties='user=<userid>;password=<pw>;Charset=iso_1;'

The user and password values are required and the syntax of Properties must be maintained, as shown above, with semicolons and quotation marks.

7.12.2 Incomplete result set in XML message received from a Tibco queue

CR # 386625

Description: If there is an XML message that needs to be received from a TIBCO queue, use a Return Type of TEXT, otherwise, an incomplete result set is returned.

Workaround: Use a Return Type of TEXT to ensure a complete result set. For example, select msgrecv('tibco_jms:tcp://localhost:7222?queue=q.sample' RETURNS TEXT).

7.12.3 Turning off extended attributes

CR # 398114

Description: When exporting tables (export syntax) in the Database Explorer perspective, you may see unwanted catalog table syntax.

Workaround: Perform the following steps.

To turn off the catalog tables:

In the Database Explorer perspective, use the Database Explorer view drop-down menu, which is the black triangle on the far right end of the Database Explorer title bar.

Choose Design|Options.

In the Database Preferences dialog, select the General tab.

Clear the Use Extended Attributes check box.

This must be cleared before accessing a database if the catalog tables are not to be created.

7.13 Mobile Development

7.13.1 Javascript errors when creating a Web capture element

CR # 401043

Description: Sybase WorkSpace 1.0 runs on Eclipse 3.0.1. This version of Eclipse does not allow you to ignore Javascript errors for the browser widget. Because the number of errors reported can be numerous, this can affect the ability to capture Web sites when creating a Web Capture element.

Workaround: This will be fixed in a future release of Sybase WorkSpace. Until then, if a capture site has excessive Javascript errors, capture the Web site using the Web Studio browser interface, setting the advanced property Display a notification about every javascript error to disabled.

See the Unwired Accelerator Administration Guide for more information.

7.14 Security Administration

7.14.1 Enable OS Authentication option in EAServer causes deployment problems

CR # 398322

Description: In EAServer Manager, if the Enable OS Authentication option is selected, Sybase WorkSpace Services packages will not work when deployed.

Workaround: In EAServer Manager, do not select the Enable OS Authentication option.

See the Security Administration section of the Sybase WorkSpace Server Administration help on the Sybase WorkSpace bookshelf for more information.

8. Sybase Unwired Orchestrator Server Issues

The following known issues exist for Unwired Orchestrator Production Edition servers.

8.1 Adaptive Server Anywhere

8.1.1 ASA Web demo causes problems during service testing

CR # 402716

Description: If you are using the ASA network server (dbsrv9) or specifying a port for your HTTP listener and if you run the <installation directory>\DevRuntimes\ASA\startwebDemo.bat file to start the ASA Web Demo and do one of the following, the service will fail when tested:

Create a Web service from an ASA stored procedure.
Save the WSDL file and create a SOAP service from the WSDL.

Workaround: Use the following procedure.

To establish the correct namespace for Web services:

Run the following to start ASA: D:\Sybase\WorkSpace\DevRuntimes\ASA\startwebDemo.bat.

Create a connection profile for the ASA server.

Create a SQL file for the connection profile. Open the SQL Editor in the Database Development perspective and execute the following command:

set option public.Webservice_namespace_host='<hostname>:4646'

In the SQL command, replace 4646 with the http port number specified in startwebDemo.bat

8.1.2 Issues cause database shutdown on Solaris

CR # 362616

Description: On Solaris, when Adaptive Server Anywhere (ASA) gets to a certain size, it may shut down and not restart due to any of the following:

ASA runs out of space on the file system.
The database file grows to a point in which it exceeds the user quota on that file system.
ASA grows larger than the file size ulimit for a user.

Workaround: Use a large file system that does not have a quota and set the user file size to unlimited.

8.1.3 Shutting down Adaptive Server Anywhere

CRs # 402440, 402248

Description: If you shut down Adaptive Server Anywhere (ASA) while its associated ASA connection profile is still connected, system performance may be affected.

Workaround: Always disconnect the ASA connection profile first before shutting down its associated ASA server. However, if the ASA server is shut down while the connection profile is connected, you can fix the performance problem by disconnecting the ASA connection profile and restarting ASA server.

8.2 EAServer

8.2.1 Memory grows when using DOS windows

CR # 389162

Description: In Windows, memory continually grows when EAServer DOS windows are running.

Workaround: Minimize and maximize the windows occasionally to release memory back to the system.

8.2.2 Shutting down EAServer

CR # 403927

Description: On Solaris 9, running the OR50rtimeEAS_stop.sh shutdown script may not shut down EAServer on the first try.

Workaround: Minimize and maximize the windows occasionally to release memory back to the system, then run the OR50rtimeEAS_stop.sh shutdown script again.

8.3 Unwired Orchestrator

8.3.1 Restarting Unwired Orchestrator after uninstalling packages

CR # 401761

Description: When restarting Unwired Orchestrator after uninstalling some of the packages, the following warning may appear in EAServer Manager:

Warning: IP Library not specified. Defaulting to IPV4

Warning: -jvmtype not specified. Defaulting to client

Adaptive Server Anywhere Server Ping Utility Version 9.0.2.2551

======================================================

.... Waiting for ASA to startup. Stand by...

Adaptive Server Anywhere Server Ping Utility Version 9.0.2.2551

Ping server successful.

=======================================================

Jaguar CTS - Component Transaction Server/Version 5.2.0 (Build 52025)/P/PC Intel/Microsoft Windows/OPT/Nov 29 2004 16:40:29

Confidential property of Sybase, Inc.

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in FAR subparagraphs 52.227-19 (a)-(d) for civilian agency contracts and DFARS 252.227-7013(c)(1)(ii) for Department of Defense contracts. Sybase reserves all unpublished rights under the copyright laws of the United States.Sybase, Inc. One Sybase Drive, Dublin, CA 94568 USA.

Enabling "128-bit" encryption.

Sybase Enterprise Application Server(Developer Edition). This version of Enterprise Application Server(TM) is licensed solely for development purposes.Any other use of software, including but not limited to production use or use on a webserver is strictly prohibited. Deployment licenses may be obtained from Sybase, Inc. for a fee.

2 Phase Commit option licensed

Clustering option licensed

High Availability option licensed

Starting services...

CtsComponents/MessageService/start: cache=?:org.omg.CORBA.INTERNAL: org.omg.COR

BA.INTERNAL: com.sybase.jaguar.system.LookupError: Application AddJavaService -

C:\Sybase\WorkSpace\DevRuntimes\EAServer\Repository\Application\AddJavaService.props (The system cannot find the file specified) minor code: 0 completed: No minor code: 0 completed: No...

CtsComponents/MessageService/start: cache=?: org.omg.CORBA.INTERNAL: org.omg.COR