I am requesting some sort of how-to tutorial, video or written steps on how to set up new and existing Python code using the RDi plugin. Trying to determine how to get Aldon LMe to recognize and how to check out code that already exists in production. And how to setup new developers. Need to use LMe/IDE for change control and use RDi for developers. The manuals do not show explain these non-standard situations. I've scanned all that I can of the Rocket Software system. Do I need to arrange training for something that should take less than 20-30 minutes to explain?    Thank you for your time.

Hi Michael, 
As you say, the installation guides won't have the overview or specifics on functionality of the Plugin features for LMe/LMi project coordination, but the Help contents that we install with the Plugin should get you started.
In RDi (after installing the Rocket Plugin), check out Help > Help contents.  In the 'Rocket Aldon...' Help, the 'Concepts' section on 'Projects, releases and IDE Projects' has an overview of the overlap between LMe IDE Projects and the LMi Filter Projects (Remote Systems Explorer). 
These topics would something normally covered as part of a customer implementation to ensure we account for your specific requirements or code that is already registered with LMe or LMi.  With that said, we should absolutely have you covered for these items: 
1 - steps on how to set up new and existing Python code using the RDi plugin (Help - Getting Started, and more below).
2 - how to get Aldon LMe to recognize and...check out code that already exists in production (Help - Getting Started, and The Team Menu ).
3 - how to setup new developers (same Help sections on Getting Started and Team).
I'll ask TSE's to look back through cases to confirm what we know of your LMe configurations for EOG (e.g. working with Stan or others), but thinking there have been 'some' IDE projects already added to LMe repository, so can start there...   If we need to get further into specifics  (e.g. for Python deployment, registering new projects, etc...) we might want to go thru support and create a case to document.
~~
For the Python questions, the setup overflow would look like this (see Help - Getting Started, and The Team Menu sections):

• The 'new' code will be registered via RDi or Eclipse using Team > Share options from a development path (not directly from production).  Would dup the production code (e.g. from IFS prod path to /home/<usrprf> path in IFS or could be local in Windows). 
• In RDi, would create a new project and import those files. 
• Then add an LMe connection in Rational to Share the Project with an existing LMe release (may need to add a new Application or Release(version) to LMe if these do not already exist for your python code - we can take a look thru support). 
• After Sharing the IDE Project from RDi, would use the Team > Add and Team > Checkin options to get the LMe repository populated. 
• At this point, other developers will be able to see/checkout the code use options to Add IDE Project to Workspace via the LMe connections view.

For seeing the 'back end' native objects, source, data areas, commands, etc...
If an LMe release is 'Associated' with an LMi release, you can further enable the visibility of the LMi objects/source in the LMe IDE project folders (e.g. in Navigator or other Views outside of RSE - where LMi developers 'normally' work).  This will allow you to see the native IBM i stuff from within the project containing the python or other (e.g. Java, perl) code outside of the Remote Systems Explorer views where the native development is actually done.  If a developer is working on both native and enterprise (e.g. IFS contents, Windows, Linux) then they can easily toggle between perspectives to review/update the different code managed in LMe or LMi.
Best, 
d

---

I am requesting some sort of how-to tutorial, video or written steps on how to set up new and existing Python code using the RDi plugin. Trying to determine how to get Aldon LMe to recognize and how to check out code that already exists in production. And how to setup new developers. Need to use LMe/IDE for change control and use RDi for developers. The manuals do not show explain these non-standard situations. I've scanned all that I can of the Rocket Software system. Do I need to arrange training for something that should take less than 20-30 minutes to explain?    Thank you for your time.

Hi Michael,

You may also find the attachment "Rational_Eclipse.pdf" useful.
It is a little dated and may have references to broken links. However, the content is still valid and in general accurate.

Best regards
Jay

---

I am requesting some sort of how-to tutorial, video or written steps on how to set up new and existing Python code using the RDi plugin. Trying to determine how to get Aldon LMe to recognize and how to check out code that already exists in production. And how to setup new developers. Need to use LMe/IDE for change control and use RDi for developers. The manuals do not show explain these non-standard situations. I've scanned all that I can of the Rocket Software system. Do I need to arrange training for something that should take less than 20-30 minutes to explain?    Thank you for your time.

Thanks Jay for the documentation but unfortunately I cannot view or download.

From what I can figure out, we have to use LMe or RDi to check out existing production code and check it back into production/promote in order to get LMe to recognize. Each object will be processed one by one. Am I correct? I couldn't see any easy way in the documentation. It's a lot so I may have missed it.

Added:   From RDi, how does a developer checkin/promote from INT to UAT? I understand it can be done using LMe but I cannot figure out the RDi side.

Thank you for everyone's time.

---

I am requesting some sort of how-to tutorial, video or written steps on how to set up new and existing Python code using the RDi plugin. Trying to determine how to get Aldon LMe to recognize and how to check out code that already exists in production. And how to setup new developers. Need to use LMe/IDE for change control and use RDi for developers. The manuals do not show explain these non-standard situations. I've scanned all that I can of the Rocket Software system. Do I need to arrange training for something that should take less than 20-30 minutes to explain?    Thank you for your time.

Hi Michael,

I re-uploaded the file, please retry.

From your description, my understanding is that the Python application has not yet been loaded into LMe?

Here is a little summary of what to expect from each of these Rocket Products

Eclipse Plug-In
The purpose of the Eclipse Plug-In is to allow Eclipse developers to develop in their favorite development tool (Eclipse) while retaining your Organization's policies which are managed in LMe.


Lifecycle Management Enterprise (LMe)
Managing Parts
Depending on your needs, Parts (Python, JAVA, PHP etc.) could be managed individually in LMe:
Parts could be added into LMe directly into the Inventory (PDN) environment.
LMe > Setup > Release Configuration > Expand Group/Application/Release > Right-Click > Load Inventory.
Once loaded, individual parts could be checked out, modified, checked in and promoted.

Alternatively, parts could be added directly in the Development Environment, checked in, Promoted.
LMe >  Expand Group/Application/Release > Right-Click > New > Parts > Add from development environment  (Drop Down)
Once added, individual parts could be checked in and promoted.

Managing a build
A whole application may be built (outside of LMe) then loaded into LMe as a Build-release. This could be promoted and deployed as a single unit.

Best of both worlds
A combination of both: such that Check out, change, Check in and promote the individual parts in LMe > Deploy the changed parts to your favorite build application (e.g. Jenkins) where the full application is built > IMPORT the build result into LMe build-release > Promote and deploy as a single unit.


Best regards
Jay

---