Versions Compared

Old Version 2

changes.mady.by.user Anthony Chow

Saved on

compared with

New Version Current

changes.mady.by.user Anthony Chow

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added updated slide deck from Akana

Software and Tools Installation

This slide deck from Akana provides an overview of all software and tools relevant to day-to-day administrator tasks.

PuTTY

Used to create an SSH tunnel. An active session is required to connect to the backend database and LDAP directory.

...

Software can be downloaded at http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Note

Necessary to update the IP address and forwarding ports to use the v7 environment

 

Configuration Screenshot

Hostname

Private key

Note
  • The
actual
  • private key file
can be obtained on AWS IT Infrastructure for SHARE Development Team
  • , named cdisc-admin_021114_private.ppk, can be obtained here: private key
  • No need to update the private key file to use the v7.0 environment

Ports

Note

No need to include the letter L in Source port, it will be added by the tool

...

Software can be downloaded at http://www.oracle.com/technetwork/developer-tools/sql-developer

Note

No need to modify Oracle SQL Developer configurations after upgrading from Semantics Manager v6 to v7

 

Configuration Screenshot

Note
  1. Password is noi$yEnd65
  2. Reporting views are under these database named users:
    1. CDISC – for libraries SHARE-Testing (ID:4); and, SHARE (ID:5)
    2. CDISC_TRAINING – for libraries SHARE-Training (ID:4); and, SHARE-Sandbox (ID:5)
  3. View names contain library ID in the suffix, e.g., SHARE.RPT_ASSET_5 is the RPT_ASSET for the production SHARE library

...

Software can be downloaded at http://directory.apache.org/studio/downloads.html

Note

No need to modify Apache Directory Studio configurations after upgrading from Semantics Manager v6 to v7

Configuration Screenshot

Network Parameters

...

Refer to Installing SOA Rich Clients

Note
  • Library and Repository Client version must match; strongly advised to uninstall Repository Client v6 and install v7
  • Per Akana, the current internal configuration schema remains at 6.7.0.6. Therefore, when prompted for LPC version upversion, it is fine to not see version 7.x. Full response:

Image Added

CDISC: When opening the LPC, it asks me to upversion from 6.7.0.3 to 6.7.0.6. Is this okay since we are in version 7? I just want to make certain this is not an indication of an issue with my Repository Client install. Thanks.

Akana: That is correct and normal. The current internal LPC version used by the SM 7.0.0.83 Repository Client is 6.7.0.6. As I understand it, the engineer didn't have any LPC 7.x specific schema changes, so the internal LPC version remained as 6.7.x