Optional Configuration

1. If you receive the No token set error when accessing the APM Connect Administration Center, as shown in the following image, select Validate your license manually.
   

   The Validation request screen appears.

   

2. In the Validation request window, in the Validation message (put this message on the form of the next Link) box, copy the text.
3. In the Validation link (put the generated validation token to the next text Area) section, select link.

   If a browser opens, displaying the Enter your validation request page, skip to step 6.

   -or-

   If a browser does not open, proceed to the next step.

4. Complete the validation.

   Response from selecting link	How to complete validation
   A browser opens displaying Enter your validation request.	Proceed to the next step.
   A browser does not open.	Right-click link, and then select copy link text. Via email or chat, send the link to a machine with internet access that is not behind the firewall, and then, on that machine, paste the link into a browser.

5. Paste or enter the text from the Validation message (put this message on the form of the next Link) box into the box in the browser, and then select Get your validation token.
6. Select .
7. In the Copy your validation token, copy the text in the box.
8. Return to the APM Connect Administration Center.
9. Paste the token text into the Validate box.
10. Select Validate.

1. On the APM Connect server, navigate to Control Panel\System and Security\System to open system properties for the Windows machine.

   The View basic information about your computer screen appears.

2. In the Control Panel Home pane, select Advanced systems settings.

   The System Properties window appears, displaying the Advanced tab.

3. Select Environment Variables....

   The Environment Variables window appears.

4. In the System variables section, select New....

   The New System Variable window appears.

5. In the Variable name box, enter
   JAVA_HOME
6. In the Variable value box, enter the path to the root jdk installation directory.
   
7. Select OK, and then close the properties window.

   The Java environment variables are created.

1. Access your APM Connect Installation package, navigate to the Jobs folder, and then copy the file CheckConnections.jar.
2. On your APM Connect server, navigate to C:\APMConnect\Utilities\runtime\deploy.
3. In the deploy directory, paste the file CheckConnections.jar.

Jobs in the APM Connect Administration Center are run by users. The apmService user is required to facilitate communication between APM Connect and Predix Essentials.

1. In the APM Connect Administration Center, from the Menu pane, in the Settings section, select the Users tab, and then select Add.
2. In the Users pane, enter the user information into the empty fields as necessary according to the following table, and then select Save.

   Field	Description	Value
   Login	Email login for user	[email protected]
   First name	User first name	apm
   Last name	User last name	service
   Password	User password	apmConnect (default password)
   Type	Type of data migration	Data Integration/ESB
   Role	User role	Operation manager
   Active	Select check box to signify active user	Must select check box

A job is used to extract information from the source and push it into Predix Essentials. Before you can initiate a job using the APM Connect Administration Center, you must first load the jobs into the APM Connect Administration Center.

1. In the Menu pane, in the Conductor section, select the Job Conductor tab.
2. In the Job Conductor menu, select Add.

   The Execution task pane is enabled.

3. In the Execution task pane, in the Label box, enter a label for the job.
4. In the Description box, enter a description for the Job.
5. Select the Active check box.
6. In the Job section, select .
7. In the Import generated code window, select Browse, and then navigate to the folder containing the updated jobs package.
8. Depending on the type of deployment, select the file that contains the job based on the following tables.
   Note: You must import every job, or run the respective wrapper job, in the table for the respective deployment.

   Job Name	Description
   CreateIntermediateRepository.zip	Creates the IR database.
   Extraction_Wrapper_Maximo.zip	Wrapper job for all Maximo Adapters allowing easy configuration of multiple Maximo Adapters jobs.
   connectServicesCloudClient.zip	Enables the cloud client services.

   Job Name	Description
   CreateIntermediateRepository.zip	Creates Intermediate Repository database.
   Email_notifcation.zip	Allows for an email notification to be sent when a job or extraction fails. This report, the Failure Details report, provides the reason for why a record did not load.
   EncryptString.zip	Used to encrypt passwords.
   Extraction_Wrapper.zip	Wrapper job for all SAP Adapters allowing easy configuration of multiple SAP jobs. Note: This job can be used to run all of the Adapter jobs. It is recommended to use this job solely. Additionally, if you are using multiple SAP systems, you must use this job.
   connectServicesCloudClient.zip	Enables the cloud client services.

9. On the Import generated code window, select Launch upload.

   The Project, Branch, Name, Version, and Context boxes are automatically populated with appropriate values.

10. In the Execution Server list, select the server on which the task should be run.
11. Select Save.

    The Adapter Job is imported into the APM Connect Administration Center.

12. Repeat steps 2 through 11 for every job.

1. Edit the file etc/org.apache.karaf.jaas.cfg.
2. Update the field values listed below:

   Field	Description
   encryption.enabled	By default it is set to False. Change the field value to True.
   encryption.algorithm	By default it is set to MD5. It can be changed to any of these values (MD2,MD5,SHA-1,SHA-256,SHA-384,SHA-512).
   encryption.encoding	By default it is set to hexadecimal. It can be changed to base64.

3. Restart the APM-Container Service.

   #    Licensed to the Apache Software Foundation (ASF) under one or more
   #    contributor license agreements.  See the NOTICE file distributed with
   #    this work for additional information regarding copyright ownership.
   #    The ASF licenses this file to You under the Apache License, Version 2.0
   #    (the "License"); you may not use this file except in compliance with
   #    the License.  You may obtain a copy of the License at
   #
   #       http://www.apache.org/licenses/LICENSE-2.0
   #
   #    Unless required by applicable law or agreed to in writing, software
   #    distributed under the License is distributed on an "AS IS" BASIS,
   #    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   #    See the License for the specific language governing permissions and
   #    limitations under the License.
   #
   ################################################################################
   
   #
   # Boolean enabling / disabling encrypted passwords
   #
   encryption.enabled = true
   
   #
   # Encryption Service name
   #   the default one is 'basic'
   #   a more powerful one named 'jasypt' is available
   #       when installing the encryption feature
   #
   encryption.name =
   
   #
   # Encryption prefix
   #
   encryption.prefix = {CRYPT}
   
   #
   # Encryption suffix
   #
   encryption.suffix = {CRYPT}
   
   #
   # Set the encryption algorithm to use in Karaf JAAS login module
   # Supported encryption algorithms follow:
   #   MD2
   #   MD5
   #   SHA-1
   #   SHA-256
   #   SHA-384
   #   SHA-512
   #
   encryption.algorithm = SHA-256
   
   #
   # Encoding of the encrypted password.
   # Can be:
   #   hexadecimal
   #   base64
   #
   encryption.encoding = base64