Welcome to the i2x Academy! Here you will find a variety of resources such as articles, video tutorials, and infographics. Our goal is to provide you with the tools and knowledge you need to succeed.
Note. You must log in with an account that has been assigned the Task Manager role. Also, you cannot change the password for the account that is currently logged in.
Note. Passwords should be unique, at least 12 characters and must contain lowercase, uppercase and numbers.
Consider a grouping of related EDI data to be a batch.
Each batch will be referenced by different control numbers. There may be multiple batches and, therefore, multiple control numbers in one file, such as if you have two different 820 Payment Orders (each with their own related data) in one file.
In EDI Notepad, this will look like the following:
If the EDI file you’d like to convert to an XML file has multiple control numbers, you’ll need to complete steps 1 through 5 for the first control number with data you’d like to convert to an XML file and steps 3 and 5 for the remaining control numbers with data you’d like to convert to XML files.
If EDI Notepad is not already installed on your computer, then download and install EDI Notepad 8.2 according to the instructions in the article titled “How to Install EDI Notepad” before following the steps below.
Note. There are two ways to set up a new Project: Report Server Project Wizard and Report Server Project.
Note. Recommended via web or VNC, or via RDP if necessary.
Note. Make sure the new name has the new local port number in it.
Note. If you did TCP first, then do UDP second and vice versa. Skip this step if you have already completed this process for both TCP and UDP.
Note. If there is a port you want to change, then you can edit it instead of adding a new one.
Note. The steps in this article may vary in their order or description.
Note. Save this document and use it as an analysis tool. The Cube connection is active when this file is open and the Cube is accessible.
Note. This pop-up window is similar to a warning when saving a Microsoft Word file with the same name as an existing file, except this file contains Cube connection details. It's technical, but safe to click Yes.
$proc = get-process -Name "<process name>"
if([bool]$proc) {
Write-Output "The process is present"
} else {
Write-Output "The process is not present"
$EmailFrom = "<from email>"
$EmailTo = "<to email list (semicolon separated)>"
$Body = "<email body>"
$Subject = "<email subject>"
$SMTPServer = "<SMTP server>"
$SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, 25)
$SMTPClient.EnableSsl = $false
$SMTPClient.Send($EmailFrom, $EmailTo, $Subject, $Body)
}
A noticeable difference between Report Builder and Microsoft Visual Studio is the complexity of their designs. Report Builder is a much simpler environment, containing fewer windows and options.
Report Builder is essentially a slimmed down version of Visual Studio. In Report Builder, there is no solution to load; thus, you do not connect to a Source Control like TFS as you would in Visual Studio. Also, you do not need to get the latest version or check in to save any changes in Report Builder, you simply save the report as you would saving any regular file.
Report Builder opens reports directly from the Report Server and saves the reports there; thus, no local files are managed.
In Visual Studio, a Report Solution is created to house all of the reports, then the solution is deployed to the Report Server.
Report Builder is a much quicker method for building and deploying reports as they are easily saved, and access can be distributed without having to install Visual Studio on every machine. The access is simply based on getting to the Report directory.
Performance wise, both Report Builder and Visual Studio run very similarly, processing the logic behind datasets and report objects, and producing error messages as they are encountered.
Note. The Visual Studio Solution contains the reports.
When applying a UDP as part of an upgrade for a database that contains custom database objects, the process will halt with an invalid syntax error if any of those custom database objects have names that contain a special character.
Fundamentally, this issue is caused by missing '[ ]' around object names that the upgrade process reads from the data dictionary. Therefore, even if you are able to create an object with or rename an existing object to a name that contains an illegal character using '[ ]', the database upgrade process can fail.
The error message will contain the name of the DB object, which you can use to find the object in SSMS. Once you have access to the object, change its name to one that does not contain an illegal character. Once the upgrade is complete, you can return to SSMS and change the name back to its original form to minimize impact.
Note. You may have been provided a .SQL file or you may have the query text stashed elsewhere, it is up to you to identify the appropriate SQL query.
Note. This step is critical to prevent Excel from changing your data (like removing leading zeroes, treating dates as numbers, etc.).
SQL file with the associated script: MigrateWFData.sql
Note. See Major Considerations 2 and 3.
Note. If you are not interested in preserving workflow definitions, you can also pass 'N' as the flag to @preserveWorkflowData.
e.g. \\SOURCEAPPSERVER\e$\AderantExpert\SOURCE\Services\Workflow to\\TARGETAPPSERVER\e$\AderantExpert\TARGET\Services\Workflow
Update WFM_WORKFLOW_DEFINITION set ENVIRONMENTID = (Select ID from FWM_ENVIRONMENT)
?
?
?
To comply with modern security, servers should be compliant with HTTPS standards, which includes signing web bindings with a valid SSL certificate. This requires that you update the configuration on several servers including database and web/app servers in addition to configuring any networking appliances between those servers and client machines (e.g., load balancers). Please see the sections below for guidance when configuring your environment with appropriate SSL bindings.
- HOW TO CONFIGURE HTTPS ON AN EXPERT FRAMEWORK APPLICATION SERVER - To confirm and configure HTTPS on Aderant Expert framework application servers
- HOW TO IMPORT CERTIFICATES INTO IIS - To import certificate files onto application servers, including Aderant Expert framework application servers
- HOW TO CONFIGURE HTTPS FOR SECURE ACCESS TO REPORTS VIA SSRS - To confirm and configure HTTPS on your SQL Server Reporting Services servers
To ensure your binding is configured correctly for application servers using IIS as a web host, follow the steps below:
1. Open IIS Manager on an Aderant Expert Application Server (Start menu, Run, "inetmgr")
2. Select the web site host for your application services, in this case the "Default Website" under the Server > Sites node
3. Click on the "Bindings..." option under Actions on the right of your window
4. Verify that you see an HTTPS entry. This confirms that an https binding on 443 is enabled
a. If there is an HTTPS entry
i. Confirm that the binding is using a valid SSL certificate by selecting the HTTPS item and clicking on the "Edit" button
ii. On the Edit Site Binding screen, ensure an SSL certificate is selected and click "View..."
iii. Ensure the certificate attached is valid, non-expired, and not a self-signed certificate
1) If your certificate is not valid, choose a valid certificate from the dropdown
2) If there are no valid certificates listed, see the "HOW TO IMPORT CERTIFICATES INTO IIS" section to import your company's certificates.
b. If there is no HTTPS entry
i. Click on the "Add..." button
ii. On the Edit Bindings Screen, enter the following and click "OK"
- Type = HTTPS
- Port = 443
- IP Address = use the value from your HTTP entry (either "*" or a specific IP address)
- SSL Certificate = choose a valid certificate from the drop-down
Note. If there are no valid certificates listed, see the "HOW TO IMPORT CERTIFICATES INTO IIS" section to import your company's certificates.
5. Open a PowerShell or Command Prompt in Administrator mode, type "IISRESET"(no quotes), and hit Enter
NOTE. If the certificate used is a local, self-signed certificate, it will NOT be trusted by another machine even on the same LAN as this setup is intended for non-production, single-server scenarios.
For a test or production server that accepts traffic from other machines, you would need to associate the binding with your company's appropriate SSL certificate. To do that, follow the steps below:
1. Open IIS Manager on the Application Server (Start menu, Run, "intemgr")
2. Select the server node in the navigation area on the left
3. Double-click Server Certificates item from the central menu
4. Click the Import option in the right-hand menu
This will present the Certificate Import Wizard that allows you to import the certificate.
NOTE. It is considered best practice to NOT allow certificate exporting on a non-certificate store server, so our recommendation would be to uncheck the “Allow certificate to be exported” box when prompted.
5. Follow the Certificate Import Wizard until successful completion, selecting your certificate file, and providing other details as required
6. Open PowerShell as an administrator and issue the command “iisreset” to ensure that incoming traffic is handled appropriately
7. Return to your IIS bindings settings from the section "CONFIRM OR CONFIGURE HTTPS ON AN EXPERT FRAMEWORK APPLICATION SERVER" to select your newly imported certificates for use in the HTTPS binding (Step 4 a iii 1)
NOTE. It is considered best practice to NOT allow certificate exporting on a non-certificate store server, so our recommendation would be to uncheck the “Allow certificate to be exported” box when prompted.
From the SSRS Server desktop
1. Click the Start menu and search for “Manage Computer Certificates” to launch the certIm mmc snap-in
2. Right-click on the “Personal” node (as of this writing, this is the location required by Microsoft) and choose “All Tasks -> Import” from the menu.
This will present the Certificate Import Wizard that allows you to import the certificate.
NOTE. It is considered best practice to NOT allow certificate exporting on a non-certificate store server, so our recommendation would be to uncheck the “Allow certificate to be exported” box when prompted.
3. Follow the Certificate Import Wizard until successful completion, selecting your certificate file, and providing other details as required
4. Open the Report Server Configuration Manager application and connect to your SSRS server.
5. Perform a Stop and Start the SSRS service
6. Navigate to the Web Service URL item in the Report Server Configuration Manager and associate your certificate with port 443 for HTTPS by selecting it from the HTTPS Certificate dropdown
7. Navigate to the Web Portal URL page and click the “Advanced” button
8. Click “Add” under HTTPS Identities and associate the appropriate certificate with port 443:
