Ei dian otsikkoa*
*
*
*
ACCESSING VALUABLE INFORMATION
*
*
*
*
eBrowser publish
When you publish ebm-model the first time or you want to modify ebm-settings later.
Ebm-model has been published earlier, this is the fast way to publish ebm-model with the same settings. There can be saved several parameters for publishing.
Visualization sets are shown in hierarcies in eBrowser. Queries are saved under your wsp/pm_area.pm/publish/queries/misc.
Visualization sets are previewed in WalkAround. You have to select shading rule for visualization.
*
*
Define Custom XSL
5. Publish eBrowser
6. Define query for defining the object set for eBrowser
7. Define shading color rules in walkaround
8. Define scenes in walkaround. Lights and start points.
*
*
Choose correct XML BOM Generation Configuration file
Make sure that in XML BOM file are defined all necessary tags, that you are going to use in XSL.
Correct Hierarchy definitions
Choose Name of Custom XSL file
*
*
Location of files
XML BOM Generation Configuration file and Custom XSL file are located in folder …. Project.pms\Site\pm\publish
You could have more then one configuration file in the same project -> different kind of eBrowser publish
*
*
1. XML BOM Generation Configuration (*.xcf) / Hierarchies
Hierarcy is a model tree showing the structure of the model in desired way in eBrowser.
Hierarchies are constructed based on the attributes that the objects have.
Definition of hierarchies:
Layout of hierarchy
hno [name]; nom [name]; que [tag name];;
‘nom’ objects included to group if they do not have that tag
‘que’ the name of the tag
*
*
*
*
1. XML BOM Generation Configuration (*.xcf) / Data to be extracted
The first field (obt) object type
Every object type has own definitions
‘obt 1’ = Equipment
The second field (abr) defines abbreviation of the tag
The third field (dsc) description shown in the XML BOM listing
The fourth field (not mandatory)
‘key 1’ defines that the tag is available for locating in eBrowser model
*
*
*
*
2. Define how data will “look like” in View object details
File *.xsl defines how data will look in View Object Details-window, size of window, color, font, links, logos…
Use example.xsl file
You could edit it with UltraEdit and save as new with new name
See www.w3.org/TR/xslt for more information about XSL Transformations
You could define links for external documents in xls file so, that click on link in view object detail menu in eBrowser will open document in dwg, dxf, pdf format or any other link (for example to web page of equipment manufacturer).
*
*
Links to documents
Information from tags defined in xcf file
Document, opened in other application (for example AutoCad, DXF viewer, Adobe PDF…)
Example 1
*
*
Example 1. Defining link to iso drawing
It is necessary to define location of link – in this example it is doclink3, tag abbreviation name – “Idn”
And define location of dxf file, and rules how to find it
*
*
Defining links in *.xsl file, Example 2
*
*
Example 2. Defining link to iso drawing
*
*
2. Define hyperlinks
Save the file (setpos.html) to a certain location to your hard disk. Open it with some text editor and modify the eBrowser model name to match your eB file name from line 19.
*
*
Defining configuration of drawings export
Make the configurations to Drawing export configuration -object shown in picture below, you could find this settings in
ProjectEnvironment/Configu-ration/Common/Drawing export configuration
*
*
Export it (DWF -format)
Note: all files (setpos.html, eBrowser model and dwf -files) have to be stored to a same location.
*
*