Archive for category: APIX

You are here: / / APIX

Updating IdPSigningCertificate for ADFS

, ,

To update the IdPSigningCertificate for Active Directory Federation Services (ADFS) Token Signing Certificate that has been renewed. Follow these steps:

The steps below include the steps to export the Token Signing Certificate from ADFS after it has been renewed.

Export a Signing Certificate from AD FS; The following steps can also be found in the Infor Lawson Authentication Configuration Guide.

  1. Log into the AD FS server and click Administrative Tools->ADFS Management.
  2. On the AD FS window, Click Service to open the Service Snap-in.
  3. Click on Certificates under Service to see the Certificates pane showing all available certificates
  4. Select the certificate under Token-Signing in the Certificates Pane to get to the certificate folder
  5. Click the Copy to File option in the Details tab of the Certificate window
  6. Click Next in the Welcome to the Certificate Export Wizard window
  7. At the prompt, select the “Base64encoded X.509 (.CER)” option to choose the file format in which the certificate is to be exported and then click Next.
  8. At the prompt to select the location where the token signing certificate is to be saved and specify a filename
  9. At the prompt, verify that the file type is “Base 64 Encoded (.cer)” and then click Save.
  10. The Certificate Export Wizard window displays the File Name and location specified. Write down the file path specified or change it to your preferred location.
  11. Click Next to proceed with exporting.
  12. Click Finish. When you see this message, “The export was successful.” Click OK.
  13. Click OK again to close out the wizard.
  14. Locate the file you exported and copy it to the LSF server.

Reload AD FS signing certificate in Lawson System Foundation

  1. Make sure you copied the certificate that was exported in the above steps to a directory on the LSF server.
  2. Run the ssoconfig -c utility from a command prompt.  Enter the password when prompted.
  3. From the main menu, select “Manage WS Federation Settings”.
  4. From the sub-menu, select “Manage Certificates”.
  5. From the next sub-menu, select “Delete IdP certificate”.
  6. At the prompt, type the name of the IdP service, ADFS (this may be different)
  7. Message “Signing Certificate has been deleted successfully” is displayed
  8. From the menu, select “Import IdP certificate”
  9. At the prompt, type the name of the IdP service, ADFS (this may be different)
  10. At the prompt, type the path of the certificate. The system assumes that the certificate is in the current folder so supply path information as needed.
  11. Message “IdP signing certificate has been successfully imported to keystore”
  12. From the menu, select “Exit”

Restart the Lawson System Foundation environment and WebSphere Application server or Cluster in the proper order.

How to Find Your Database Schema Size in GB (SQL Server, Oracle, DB2)

Before we can prepare an APIX archiving proposal, we need one number from you: the total database schema size, in gigabytes (GB). Below are simple queries for the three most common database platforms. Run the one that matches your environment using an account with catalog/dictionary access, and send us the result.

Microsoft SQL Server

Run this against your production database. It returns the size of each schema, including data and indexes:

SELECT s.name AS schema_name,
       CAST(SUM(a.total_pages) * 8.0 / 1024 / 1024 AS DECIMAL(10,2)) AS size_gb
FROM sys.tables t
JOIN sys.schemas s ON t.schema_id = s.schema_id
JOIN sys.indexes i ON t.object_id = i.object_id
JOIN sys.partitions p ON i.object_id = p.object_id AND i.index_id = p.index_id
JOIN sys.allocation_units a ON p.partition_id = a.container_id
GROUP BY s.name
ORDER BY size_gb DESC;

Oracle

Replace YOUR_SCHEMA with your production schema name (for Infor Lawson environments this is often LAWSON):

SELECT owner AS schema_name,
       ROUND(SUM(bytes)/1024/1024/1024, 2) AS size_gb
FROM dba_segments
WHERE owner = 'YOUR_SCHEMA'
GROUP BY owner;

IBM DB2 (LUW)

Replace YOUR_SCHEMA with your production schema name:

SELECT tabschema AS schema_name,
       ROUND(SUM(data_object_p_size + index_object_p_size + long_object_p_size
                 + lob_object_p_size + xml_object_p_size)/1048576.0, 2) AS size_gb
FROM sysibmadm.admintabinfo
WHERE tabschema = 'YOUR_SCHEMA'
GROUP BY tabschema;

Getting your database version

While you’re connected, run the one-liner for your platform and include the output:

-- SQL Server
SELECT @@VERSION;

-- Oracle
SELECT banner FROM v$version;

-- DB2 (LUW)
SELECT service_level, fixpack_num FROM sysibmadm.env_inst_info;

What to send us

Reply to your Nogalis contact with the schema size in GB, your database platform, and the version output above. That’s all we need to prepare your proposal.