- Create or open the text file to contain customized properties. For more information, see Editing Properties Using MQL.
-
To define compound mapping, follow these steps:
The importer uses this mapping when creating or updating smelter objects so that the smelter can be associated with the correct substance classification for the smelter's conflict minerals.
-
To specify tin compounds, add or edit this line in the file used to import properties into a page object:
emxMaterialsCompliance.ConflictMineral.SubstClass.Tin
-
Set the value for this property to the substance classification number used for tin. For example:
emxMaterialsCompliance.ConflictMineral.SubstClass.Tin=SC97
-
To specify tantalum compounds, add or edit this line in the file used to import properties into a page object:
emxMaterialsCompliance.ConflictMineral.SubstClass.Tantalum
-
Set the value for this property to the substance classification number used for tantalum. For example:
emxMaterialsCompliance.ConflictMineral.SubstClass.Tantalum=SC99
-
To specify tungsten compounds, add or edit this line in the file used to import properties into a page object:
emxMaterialsCompliance.ConflictMineral.SubstClass.Tungsten
-
Set the value for this property to the substance classification number used for tungsten. For example:
emxMaterialsCompliance.ConflictMineral.SubstClass.Tungsten=SC98
-
To specify gold compounds, add or edit this line in the file used to import properties into a page object:
emxMaterialsCompliance.ConflictMineral.SubstClass.Gold
-
Set the value for this property to the substance classification number used for gold. For example:
emxMaterialsCompliance.ConflictMineral.SubstClass.Gold=SC100
- To define the display text for a substance classification, follow these steps:
- Add or edit this line in the file used to import properties into a page object:
emxMaterialsCompliance.ConflictMineral.SubstClass.<CODE> Where <CODE> is a substance classification code defined above. - Set the values of these properties to match the substance classifications defined above. You should have a property for each of the codes defined above.
For example: emxMaterialsCompliance.ConflictMineral.SubstClass.SC100=Gold
-
To list the available codes for the status of conflict mineral declarations, follow these steps:
The available codes are defined by the emxMaterialComplianceCentral.ConflictMineralDeclarationStatus.<STATUS> properties.
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialsCompliance.ConflictMineralDeclarationStatuses=
-
Set the value for this property to a comma-separated list of characters that correspond to values for the following
emxMaterialComplianceCentral.ConflictMineralDeclarationStatus.<STATUS> properties.
-
To define the status codes for conflict mineral declarations, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.ConflictMineralDeclarationStatus.Complete=C
emxMaterialComplianceCentral.ConflictMineralDeclarationStatus.Incomplete=I
emxMaterialComplianceCentral.ConflictMineralDeclarationStatus.Unreported=U
emxMaterialComplianceCentral.ConflictMineralDeclarationStatus.Invalid=V
-
Set the value for these properties to the codes you want to use.
-
To define the maximum number of MEPs to display in the MEPs column of the Conflict Mineral Reporting Status report, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.ConflictMineralStatusReport.MaxDisplayMEPs
-
Set the value for this property to a positive integer. The default value is 30.
- When finished updating the text file with all properties you want to modify, including the ones shown here, use the text file to modify the emxMaterialsComplianceCentral.properties page object. For more information, see Editing Properties Using MQL.
- To configure expiration polling for conflict minerals conflict-free certifications, follow these steps:
- Open the web.xml file for editing.
-
If not already done, enable the timer servlet by adding the following
lines.
Note:
The timer servlet is usually enabled when configuring Materials Compliance Management to monitor input folders (for more information, see Enable the Timer Servlet. If they are already defined, you
do not need to re-enter them.
<servlet id="Servlet_19">
<servlet-name>TimerServlet</servlet-name>
<servlet-class>com.matrixone.servlet.TimerServlet</servlet-class>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping id="ServletMapping_16">
<servlet-name>TimerServlet</servlet-name>
<url-pattern>/servlet/timer/*</url-pattern>
</servlet-mapping>
Note:
Make sure there isn't already a servlet id="Servlet_19", or
"ServletMapping_16" in the web.xml file. If
there are, use the next number available for each id. These numbers
are simply identifiers, so it does not matter what they are but they
cannot be duplicated in the file.
- If the timer agent has not been defined yet for Materials Compliance Management, enter these lines:
Note:
These entries are usually defined when configuring Materials Compliance Management to monitor input folders (for more information, see Enable the Timer Servlet. If they are already defined, you do not need to re-enter them.
<context-param id="ContextParam_14">
<param-name>ematrix.timer.agent</param-name>
<param-value>creator</param-value>
</context-param>
<context-param id="ContextParam_15">
<param-name>ematrix.timer.agent.key</param-name>
<param-value></param-value>
</context-param> - In the above entries, edit the username, password, and timer interval values between the corresponding
<param-value> and
</param-value> tags. The interval value is in seconds.
For ematrix.timer.agent , enter the username of a valid admin person that the servlet should use to set context in
MQL. To configure expiration polling, this user must have an Materials Compliance Management license. For ematrix.timer.agent.key , enter the password for the above username, if there is any. Use the password from the database, and not from the external authentication (such as 3DPassport) used to log into the web apps. - Add these lines:
<!-- Timer Servlet for Conflict Minerals Conflict-free certification expiration polling within the Materials Compliance application -->
<context-param id="ContextParam_MCM_CMS_15">
<param-name>ematrix.timer.interval1</param-name>
<param-value>86400</param-value>
</context-param>
<context-param id="ContextParam_MCM_CMS_16">
<param-name>ematrix.timer.command1</param-name>
<param-value>execute program jpo.materialscompliance.Smelter -method pollSmelterConflictFreeCertficationExpiration</param-value>
</context-param> The values for each context-param id must use this format: ContextParam_value and the value must be unique within the file. If you configure multiple timer agents in the web.xml file, add an integer to ematrix.timer.interval and ematrix.timer.command , such as ematrix.timer.interval1 and ematrix.timer.command1 as shown above. Each related timer interval and timer command should use the same integer, and the integer should not be duplicated in the web.xml file. - Save the web.xml file.
- Run the warutil to create the archive files that include the updated web.xml file.
- Copy the
enovia folder from distrib to the Application folder.
|