Capital Service Explorer

Various artifacts are available as standard with the a Capital Service Explorer package. This package can be viewed in a standard web browser and is also supported on a Windows tablet device.

• 2D Location Views

• Assembly BOM - Report

• Attributes and Properties

• CATIA 3D Models

• Component BOM - Report

• Cross References

• Diagram Generation

• Connector Views

• Fault Code Data Generator

• Ground Report

• Ground and Power Signal

• JT 3D Model Viewer

• Links

• Multicore List - Report

• Net List - Report

• Project Level Wire Report Based on Harness Filtering

• RapidAuthor 3D Catalog Model Viewer

• Lean SVG Diagrams

• Wire List - Report

Configuring

a Capital Service Explorer Package

Package configuration only needs to be performed once after the Capital E/E Publisher installation. However, you can edit the configuration to change how your generated Capital Service Explorer package looks and operates.

You can configure various aspects of the Capital Service Explorer package, such as the attributes and properties, available languages, and the order and content of navigation sections and popovers. The publisher folder in the Capital installation directory contains the following files:

• attributeList.xml

• config.xml

• NavigationPanel.xml

• popup.xml

• publisher_report.xsl

The following aspects of the Capital Service Explorer application are configurable:

• Attributes and Properties

• Language Support

• Navigation Panel Configuration

• Pop-up Configuration

• Hotspot Configuration

Caution

Capital Service Explorer package configuration must only be performed by a system administrator or an experienced Web designer.

Accessing

a Capital Service Explorer Package

There are two methods available to access Capital Service Explorer packages depending on whether you need local or remote access.

Local Access

Use when the Capital Service Explorer client is shipped on a removable media device, such as a flash drive, USB Memory Stick, or a DVD.

• The package output is the Packets folder, app files, and the CapitalServiceExplorer.exe.

• The whole package folder (with everything noted above) must be included on the removable media device.

• Open the CapitalServiceExplorer.exe to start a local server on your computer, to which the browser connects.

• A Browser tab opens automatically, connecting to the local server (indicated as “localhost”, in the address bar).

Remote Access

Use to host the package data on a dedicated online web server, implemented for example using Tomcat, IBM WebSphere, Microsoft Azure, or WildFly.

• Only the contents of the Packets folder are relevant; the remaining files are not used. The next step depends on server type: For instance in case of Tomcat, the Packets folder is copied into the webapps folder under Tomcat, and then renamed to a unique name to be used in the URL connecting to the server to access this package.

For IBM WebSphere, the contents from the Packets folder are packaged into a .war file and added as a New Enterprise Application using the Admin Console, as shown in Figure 36. Figure 36: Example IBM WebSphere Admin Console

• The URL link to access the Capital Service Explorer client is then obtained from the hosting server, and is made available for technicians to access it over the network / internet.

• With the release of Capital 2408, the software has adopted Java 17. This has led to some changes in how Java manages access to certain parts of its code, known as modules. This being the case certain settings must be considered when hosting Service Explorer packages on third-party web servers. One of the changes introduced with Java 17 is increased encapsulation, which means some parts of the Java code that Capital needs to access are now more restricted. To ensure your system continues to function correctly, you must instruct the JVM to “open” these parts of the code to Capital. This is achieved using the --add-opens option. Adding this option when you start Capital instructs the JVM to allow access to the required elements of the Java code. When deploying Service Explorer on third-party web servers, these options must be added manually as detailed in the Setting JVM Options When Hosting Packages on Third-party Web Servers topic in the Capital Installation and Upgrade - Additional Information Guide.

Note

To adhere to increased browser security, opening the Capital Service Explorer files directly (for example by clicking the index.html file) is not supported in Capital Service Explorer Clients. You must have a server running either locally, or remotely, as described above, for the client (browser tab) in order for Capital Service Explorer to function correctly.

Note

For the Remote Access use case, you must ensure that the Java (JRE) version used on the server matches with the Java version used in Capital (where the package was created). Without this, some functions such as “click and sprout” may not function correctly. The version used is noted in the your_install_location\Capital\config\javaprops.xml file.

Attributes and Properties

Each object within a design has its own set of attributes and properties. The Attributes and Properties artifact will export those values and make them available on selection of that object within the Capital Service Explorer application.

The set of attributes and properties to be included are specified in the attributeList.xml, located in the publisher folder in the Capital application installation directory. The attributeList.xml can be configured as follows:

Each attribute or property is made up of a triplet of text elements that define how it is identified on an object and how it is displayed to the user.

The tag refers to either an attribute or a property:

name='PartNumber' refers to the Part Number attribute on any object.

displayName='PartNumber' refers to the text that is displayed in the Capital Service Explorer application for that attribute.

Note

The class attribute for an object can be used with the API JavaDoc to identify the correct attribute names for any object. This list will be included in the appendix but can also be found with any install of a Capital application.

Language Support

The i18n folder found in the publisher folder in the Capital installation directory, contains several resources.properties files. Each file contains all of the text that appears in the user interface of the Capital Service Explorer application. This can be used as the basis to provide support for different languages.

Each language can have its own copy of the file where the text is translated. Several language files are already provided and you can edit these directly or create your own from scratch. The correct file will be loaded by the application based upon the locale of the operating system from which it is invoked.

Invoking

Greyscale Printing in the Capital Service Explorer Packager

To invoke greyscale printing in the Capital Service Explorer packager, follow the instructions detailed in Invoking Greyscale Printing.

License

Consumption and Timeouts

Viewing a package in a web browser consumes a license. To avoid situations where sessions may not have been closed correctly— locking a license that may be required by another user—you can configure runtime timeouts. Edit the config.xml file contained in the publisher/capital-explorer-runtime\app folder to amend the relevant settings. The sets the maximum time limit (in seconds) allowed for communications between the server and browser, while the sets the limit on user interaction with the browser. In both cases, if no response is received within the specified limit, the session is automatically closed, and the license is released. Figure 37 shows a scenario where the is set to 25 seconds, while the is set for 600 seconds.

Figure 37: Example Timeout Configuration File

Navigation Panel Configuration

Use the NavigationPanel.xml to configure how content is displayed:

• Order that the sections display.

• Content displayed on the items within each section.

• Tooltips.

The sections of the Navigation panel will appear in the Capital Service Explorer application in the order they appear in the file.

You can define up to four attributes (properties for objects) for each section, all will appear in the tooltip:

• The first attribute is the primary text for objects within that section.

• The second attribute is used as the subtext for all objects.

• The third and fourth attributes will appear only in the tooltip.

All four attributes and properties are used in the “Filter” at the base of the panel to determine applicability.

If no attribute or property is defined for a section, the name is used as the default.

Note

If you define more than four attributes / properties, the system uses the first four it locates for any object.

Systems

and Harness Diagrams Display Configuration

Use the following parameters in the config.xml file to configure how designs are displayed on the List Panel.

Copy

<showSystemsAsTree value="false"/>
<showHarnessAsTree value="false"/>

Specify false to display a single list of designs, or true to display a folder tree that reflects the structure of the design browser in the Capital design applications, containing all the designs included in the open package. The default is false.

Note

Packages generated prior to the availability of the parameters will not display the folder trees on the List panel.

Figure 38: Example List Configurations

Pop-up Configuration

Use the popup.xml file to configure the popup windows that appear when you select any object within the Capital Service Explorer application.

Each object type has its own section that can be configured independently of the others.

You can open popups from reports, cavity chart tables, harnesses, and fault codes.

Hotspot Configuration

Clickable hotspots can be added to any 2D Location SVG. When you click a hotspot you will be presented with a popup showing the links to systems diagrams.

Figure 39: Hotspot Example 1

On a connector face view, if a Connector Pin datum were provided per pin, the packager tool would generate an intelligent Lean SVG. Each datum would be a clickable hotspot displaying a pop-over with information including cross-references and the ability to render the signal path for any wires that terminate at that connector pin. See also “Adding Datums” in the Capital Symbol Designer User Guide.

Figure 40: Connector Face example 1

Reports

The following reports are available to be included in the Capital Service Explorer package. The reports are in the default Capital format and can be additionally customized by amending the publisher_report.xsl stylesheet found in the /publisher folder in the Capital installation directory.

• Assembly BOM - Report

• Component BOM - Report

• Multicore List - Report

• Net List - Report

• Project Level Wire Report Based on Harness Filtering

• Wire List - Report

Parent Topic:

Packagers

Capital E/E Publisher User Guide, 2512.2606

Unpublished work. © 2026 Siemens