Configure JBoss ISAPI with IIS for Security Services login service
A CORBA COMM_FAILURE error is reported in the web tier
This error usually indicates one of the following:
1. The Teamcenter server has terminated while processing a request.
2. The Teamcenter server encountered a serious error (for example, failed memory allocation) while attempting to process a request.
The message generally does not indicate a problem in the web tier itself. Teamcenter server syslog files may contain information useful in diagnosing the root cause of Teamcenter server failures.
Problem Solution After publishing an item to an
ODS, the Sun Java System Application Server becomes unresponsive.
A Teamcenter web application deployed on a Sun Java System Application Server can become unresponsive. This can occur especially when:
• You publish and item to the default ODS site that is also the site publishing the item.
• You attempt to view the published item's details in the home folder.
To correct this problem, ensure that you have set the Thread Count and Initial Thread Count to at least the minimum values required (25 and 15 respectively) and restart the application server.
Note
Depending on Teamcenter web tier activity, you may have to set these values higher than the minimum to get the best performance.
Client-side Java session cookies are overwritten by web tier applications deployed in the same domain on a WebLogic application server.
Multiple applications deployed in the same WebLogic domain can cause client session cookies to overwrite each other. To avoid this, deploy your Teamcenter web application in a domain by itself or ensure each application has a separate cookie path.
To set your web application session cookie path:
1. Navigate to the
WEB-ROOT/staging-directory/webapp_root/WEB-INF directory for the application.
Note
WEB_ROOT is the location where you installed the Web Application Manager (insweb) forWindowsor UNIX/Linux), and staging-directory is the directory where the specific web application was generated.
2. Open the weblogic.xml file and add the following elements:
<session-param>
<param-name>CookiePath</param-name>
<param-value>/deployable-name</param-value>
</session-param>
Replace deployable-name with the deployable file name set in the Web Application Manager, for example, tc.
3. Launch the Web Application Manager (insweb).
4. Select the web application name and click Modify.
Problem Solution
5. In the Modify Web Application dialog box, click Generate Deployable File.
6. In the Generate Deployable File dialog box, click OK.
The Web Application Manager displays the status of the installation in the Progress dialog box. When the installation is complete, click OK to close the Progress dialog box.
7. Click OK to close the Modify Web Application dialog box.
During peak activity, the web tier encounters errors obtaining JCA connections.
The Teamcenter web application is using all available connections in the connection pool. To avoid this, increase the number of available connections by increasing the
Max_Capacity context parameter value in the web application WAR file.
To set your web application maximum connection pool size:
1. Launch the Web Application Manager (insweb) for WindowsorUNIX/Linux).
2. Select the web application name and click Modify.
3. In the Modify Web Application dialog box, click Modify Context Parameters.
4. In the Modify Context Parameters dialog box, locate Max_Capacity, double-click the Value column, and type a larger number.
5. Click OK and click Generate Deployable File.
6. In the Generate Deployable File dialog box, click OK.
The Web Application Manager displays the status of the installation in the Progress dialog box. When the installation is complete, click OK to close the Progress dialog box.
7. Click OK to close the Modify Web Application dialog box.
8. Redeploy the WAR file in your application server.
Problem Solution Chinese characters are
displayed as square blocks in the Teamcenter rich client.
If you use a nonnative language operating system version of Windows, you must install and enable the Multilingual User Interface (MUI) pack to ensure the language font is displayed properly.
1. Download and install the MUI pack for Windows from Microsoft.
2. Open the Regional and Language Options dialog box in the Windows Control Panel.
3. In the Languages tab, set the required language for the menus and dialogs.
4. In the Advanced tab and the Regional Options tab, set the required language.
JBoss 5.1.0 GA displays an error message during startup when installed on Oracle Solaris operating system.
The following error message displays during JBoss startup:
AttachmentStore MC bean (org.jboss.system.server.profileservice.
repository.abstractAttachmentStore)configuration does not specify the parameter type for constructor
This is a known JBoss bug (JBAS-6981). You must edit the profile.xml file for your application server
instance. Using the default server as an example, edit the {jboss-5.1.0.GS}/server/default/conf/boodstrap/profile.xml file as follows:
1. Locate the following parameter element in the file:
<!-- The attachment store -->
<bean name="AttachmentStore"
2. Update the parameter element to include a class attribute:
<parameter class="java.io.File">
3. Save the file and restart the application server.
Problem Solution During successive calls to get
activity status in the Global Services user interface, out of memory errors are displayed.
During large Global Services transactions, such as a replication manager transaction during site consolidation orchestration, you may encounter a Java out of memory error from the application server. This usually is caused by repeated checks on activity status (AuditActivity business object) from the Global Services user interface.
The Java virtual machine (JVM) size grows with each call to get the status. To avoid this, reduce the application server’s Java memory property to between 1200m and 1500m (-Xmx1200m or -Xmx1500m, respectively).
Teamcenter web application fails to deploy on JBoss with the following error message:
Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
The Teamcenter web application takes longer than the default 60 seconds theJBoss deploymentscanner allows for deployments. Add the deployment-timeout attribute to the deployment-scanner element and set the value to at least 600 seconds before attempting to deploy the web application.
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
<deployment-scanner path="deployments"
relative-to="jboss.server.base.dir" s scan-interval="5000"
deployment-timeout="600"/>
</subsystem>
If your Teamcenter application requires more memory than what is currently allocated in WebSphere, out-of-memory errors can occur. For example, if you use the NX Integration and attempt to
launch NX from the rich client, Teamcenter may report an out-of-memory error during a call to getAttrMappingsForDatasetType.
If errors like this occur, you must modify the JVM arguments in WebSphere to increase memory allocation. For information about how to modify JVM arguments, see the IBM support article titled Setting generic JVM arguments in WebSphere Application Server:
http://www-01.ibm.com/support/docview.wss?uid=swg21417365
Before you tune JVM arguments, use memory profiling tools to analyze your memory issues and determine which tuning options you need to use. The following table provides some suggestions, but these may not be suitable in all cases.
JVM options for tuning the WebSphere Application Server memory usage
JVM option Description
Typical default value
Suggested value -Xms Controls the initial size of the Java heap.
Properly tuning this parameter reduces the overhead of garbage collection, improving server response time and throughput. For some applications, the default setting for this option may be too low, resulting in a high number of minor garbage collections.
50 MB 512 MB
-Xmx Controls the maximum size of the Java heap.
Note
In general, increasing the minimum/maximum heap size can improve startup, reduce the number of garbage collection occurrences, and increase the throughput until the heap no longer resides in physical memory. After the heap begins swapping to disk, Java performance suffers drastically. Therefore, The heap sizes should be set to values such that the maximum amount of memory the VM uses does not exceed the amount of available physical RAM.
256 MB 1024 MB
JVM options for tuning the WebSphere Application Server memory usage JVM option Description
Typical default value
Suggested value -XX:PermSize Sets the section of the heap reserved for the
permanent generation of the reflective data for the JVM. This setting should be increased to optimize the performance of applications that dynamically load and unload many classes.
Note
PermSize memory consumption is in addition to the -Xmx value set by the user on the JVM options. Setting this to a value of 128 MB eliminates the overhead of increasing this part of the heap.
Client: 32 MB
Server: 64 MB
128 MB
-XX:MaxPermSize Allows for the JVM to be able to increase the PermSize setting to the amount specified.
Initially, when a VM is loaded, the MaxPermSize is the default value, but the VM does not actually use that amount until it is needed. If you set both PermSize and MaxPermSize to 256 MB, the overall heap increases by 256 MB in addition to the -Xmx setting.
Note
If an application needs to load or reload a large number of classes, the following error may result:
messageOutOfMemoryError: PermGen space
Typically, this means that the JVM started with an insufficient maximum value for permanent generation.
N/A 256 MB
B BLOB
Binary large object; attribute type of undefined structure. BLOBs are stored as binary images within an object.
business object
Logical grouping of data attributes and properties that are manipulated at the enterprise level.
A Global Services business object allows users to query for and update information in multiple data sources.
business object definition file
File that contains the XML-based definition of a Global Services business object.
D
data source
System that manages enterprise data and can be accessed by Teamcenter. Examples are product knowledge management (PKM) systems, product lifecycle management systems, relational databases, enterprise resource planning (ERP) systems, component and supplier management (CSM) systems, mechanical design automation (MDA) systems, purchasing systems, systems engineering GroupWare, and maintenance, repair, and overhaul (MRO) systems.
datastore
Java Database Connectivity (JDBC) database instance used to store the Global Services configuration and business object definition (BOD) information. The majority of the objects in the datastore are stored as serialized objects for improved performance. The configuration and BOD files are serialized during the process of uploading them to the datastore. Global Services users with administrator privileges can access the Configuration Object form in Global Services that allows them to add, remove, and update objects in the datastore. See alsobusiness object definition file.
E
enterprise tier
Teamcenter architectural tier that comprises a configurable pool of Teamcenter C++ server processes and a server manager. Larger sites can distribute the pool of server processes across multiple hosts.
Smaller sites can run the pool of servers on the same host as the web tier.
N
network load balancer (NLB)
HTTP web servers are configured to allow each HTTP web server in the load balanced cluster to respond to a virtual IP address. Requests to this virtual IP are intercepted and routed to a machine running one of the web servers in the cluster.
O
Oracle home
Directory in which Oracle software is installed on the Oracle server node.
Oracle system identifier (SID)
Alphanumeric word used to identify a collection of processes and associated memory structures as belonging to a particular Oracle database instance. The ORACLE_SID environment variable defines the Teamcenter-Oracle system identifier.
P
preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter session is initiated. Preferences allow administrators and users to configure many aspects of a session, such as user logon names and the columns displayed by default in a properties table.
S
site preference
Teamcenter preference that applies to the entire site.
SQL
See Structured Query Language.
Structured Query Language
ANSI standard command and embedded language for manipulating data in a relational database.
W
Web Application Manager
Graphical installation utility that generates supporting web files (WAR format) for a named web application. Web Application Manager also installs the rich client distribution server and creates distribution server instances.
web archive (WAR)
Web application that requires an HTTP web server and servlet engine.
web tier
Teamcenter architectural tier that comprises a Java application running in a Java Platform, Enterprise Edition (Java EE) application server. The web tier is responsible for communication between the client tier and enterprise tier.
5800 Granite Parkway
AIA Kowloon Tower, Landmark East 100 How Ming Street
Kwun Tong, Kowloon Hong Kong
+852 2230 3308
About Siemens PLM Software
Siemens PLM Software, a business unit of the Siemens Industry Automation Division, is a leading global provider of product lifecycle management (PLM) software and services with 7 million licensed seats and 71,000 customers worldwide. Headquartered in Plano, Texas, Siemens PLM Software works collaboratively with companies to deliver open solutions that help them turn more ideas into successful products. For more information on Siemens PLM Software products and services, visit www.siemens.com/plm.
© 2015 Siemens Product Lifecycle Management Software Inc. Siemens and the Siemens logo are registered trademarks of Siemens AG. D-Cubed, Femap, Geolus, GO PLM, I-deas, Insight, JT, NX, Parasolid, Solid Edge, Teamcenter, Tecnomatix and Velocity Series are trademarks or registered trademarks of Siemens Product Lifecycle Management Software Inc. or its subsidiaries in the United States and in other countries. All other trademarks, registered trademarks or service marks belong to their respective holders.