Label*

Default Value: Teamcenter Project Remove
Example: TC project_doc

String

None

The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.

Object ID*

Default Value: N/A
Example: $._id

Dropdown

None

Select the UID (unique identifier) or the Teamcenter adapter ID of the object.

Project*

Default Value: N/A
Example: ade_345

String

None

Specify the UID or an Adapter ID of the project.

Configure Output

Default Value: deselected

Checkbox

None

Select this checkbox if you want the Snap to specify the configuration of the Teamcenter properties in the output

Expand attributes path

Default Value: N/A
Example: attributes1 → item_response

String/Expression

Configure Output

Specify the path of the expand attributes in the input document.

Expand Attributes

Specify the attributes you want the Snap to fetch from the Teamcenter software. Each attribute must be specified as a new row. Click to add a row.

Name*

Default Value: None.
Example: Item_response

Configure Output

Specify the name of the attribute.

Snap Execution

Default Value: Execute only
Example: Validate & Execute

Dropdown list

None

Select one of the following three modes in which the Snap executes:

• Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

• Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

• Disabled: Disables the Snap and all Snaps that are downstream from it.

Unable to start embedded Teamcenter Adapter.

The Teamcenter SnapPack requires SOA API Libraries. The required SOA API Libraries are not available in the JCC (Java Command Center) environment.

Copy the necessary API library files to the %SL_ROOT%/teamcenter_lib directory. Then, ensure they are added to SL_CLASSPATH. Verify the correct library setup.

Communication failure with Teamcenter. Host cannot be connected

The configured host name cannot be resolved to an IP address.

• Host Name Check: Verify and correct the hostname.

• DNS Configuration: Check and correct DNS configuration.

Connection Failed while connecting to Teamcenter

Communication with the Teamcenter Webtier cannot be established due to firewall settings or incorrect URL/port configuration.

Investigate if there's a firewall between Groundplex and Teamcenter Server. Verify URL and port settings.

Incorrect account credentials

The username and password provided in the account configuration are incorrect

Ensure that the correct username and password are configured in the account.

Invalid user or user does not exist.

The user configured in the account is set to inactive in Teamcenter.

Reactivate the user account in Teamcenter through an authorized user, typically an administrator.