Wednesday, August 14, 2019

Share your code in Git using Eclipse

Share your code in Git using Eclipse


Share your Eclipse project with your team in an Azure DevOps Services/TFS Git repo.

Prerequisites

  • An Azure DevOps organization. If you don't have one, you can sign up for one for free. Each organization includes free, unlimited private Git repositories.
  • A local Eclipse project. If your code is already in version control in Azure Repos or TFS and you want to clone it, see Clone an Azure DevOps Services Git repo using Eclipse.

Use Team Explorer Everywhere

Team Explorer Everywhere is an open-source Eclipse plug-in to connect Eclipse to Azure DevOps Services or Team Foundation Server. If you're working with Azure DevOps Services/TFS and Eclipse, use this plugin to connect to your repos, builds, and work items.
 Note
The Team Explorer Everywhere plug-in works with Eclipse versions 4.2 (Juno) - 4.6 (Neon).
  1. Add the Team Explorer Everywhere view in Eclipse. Go to Window, Show View and select Other... Search for Team Explorer, select the Team Explorer view, and select OK.
    Add the Team Explorer view to Eclipse

Connect to Azure DevOps Services

  1. In the Team Explorer Everywhere view, select Connect to VSTS or a Team Foundation Server .
    Select Connect to Team Foundation Server to connect your TFS or Azure DevOps organization
  2. If you know your Azure DevOps Services or Team Foundation Server account URL, select the Servers... button under Connect to a Team Foundation Server or Azure DevOps organization to add your TFS server or account to the drop-down list. If you don't know your account information for Azure DevOps Services, select Browse Visual Studio Services and select Next.
    Add Existing Project Dialog
    Either choice will prompt for your credentials before continuing further.
  3. Select the project where you will share your code from the Project Selection dialog and select Finish.

Create a local Git repo for your Eclipse project

Before you can push your project to Azure Repos, you need to add it to a local Git repo.
 Note
If your code is already in a local Git repo, you can skip this step.
  1. With your project open in Eclipse, right-click the project name in Project Explorer and select Team, Share Project... Select Gitand select Next.
  2. Select Create... from the Configure Git Repository window and choose a folder for your local Git repo. Select Finish.
    Create a local Git repo in Eclipse
  3. Right-click your project in Project Explorer and select Team, Commit.... Stage your changes by dragging your files to the Staged Changes field, enter a commit message, then select Commit.
    Commit your code with Git in Eclipse

Push your project to your Azure DevOps Services/TFS repo

  1. In Team Explorer Everywhere, select Git Repositories, then right-click the empty repo you want to push your Eclipse project to and select Copy Clone URL. If you don't have an empty Git repo created in Azure DevOps Services/TFS yet, you can create one using these instructions.
    Copy the Git repo clone URL in Team Explorer Everywhere with a right-click
  2. In Package Explorer, right-click your project and Select Team, Push Branch ... . Paste the clone URL from the clipboard into the URI field and select Next. Make sure Configure upstream for push and pull is selected in the next window and select Next.
    Push your code to Azure Repos using the Clone URL from the web
  3. Review the changes and select Finish in the Push Branch window.
Your project code is now in your Git repo.

Visual Studio Team Explorer Everywhere for Eclipse (Azure DevOps Services and TFS)

Visual Studio Team Explorer Everywhere for Eclipse (Azure DevOps Services and TFS)

 Note
The Team Explorer Everywhere plugin works with Eclipse versions 4.2 (Juno) - 4.6 (Neon).
Visual Studio Team Explorer Everywhere (TEE) is a plug-in for Eclipse that enables you to work with Team Foundation Server (TFS) and Azure DevOps using both Team Foundation Version Control (TFVC) and Git version control systems.
For information on connecting to an Azure DevOps Services Git repo from Eclipse with TEE, read Share your code with Eclipse and Azure DevOps Services Git.

Eclipse Update Site for Latest Release

The latest release of TEE can always be installed in Eclipse using this update site URL:

To install Team Explorer Everywhere from within Eclipse

  1. Click on the Eclipse icon in the toolbar to open the Eclipse Java IDE.
    Click Eclipse in the Toolbar
  2. The first time you run Eclipse, it will prompt for default workspace. Click on the box "Use this as the default and do not ask again" to use the default workspace on startup.
    Accept the default Eclipse workspace
  3. When the Welcome dialog appears, on the Help Menu select Install New Software.
    Click on Help > Install New Software
  4. Choose the Add button to add a new repository. Use Team Explorer Everywhere as the name. The location of the update site is https://dl.microsoft.com/eclipse.
    Add Repository
  5. Choose the OK button.
  6. In the list of features in the Install dialog box, select the check box that corresponds to the Team Explorer Everywhere plugin. If you don't see this option, use the pull-down menu for "Work with:" and find the update site URL you just entered in the list and select it, then select the check box beside the plug-in mentioned above.
    Select Team Explorer Everywhere
  7. Choose Next two times. Accept the license agreement and choose Finish
  8. Eclipse will need to restart.

Tuesday, August 13, 2019

Adding an existing project to GitHub using the command line

Putting your existing work on GitHub can let you share and collaborate in lots of great ways.
If you are migrating your project from CodePlex, read the migration guide for more information.Hub Desktop Help.


Create a new repository on GitHub. To avoid errors, do not initialize the new repository with README, license, or gitignore files. You can add these files after your project has been pushed to GitHub.
  1. Create New Repository drop-down
  2. Open Git Bash.
  3. Change the current working directory to your local project.
  4. Initialize the local directory as a Git repository.
    $ git init
  5. Add the files in your new local repository. This stages them for the first commit.
    $ git add .
    # Adds the files in the local repository and stages them for commit. To unstage a file, use 'git reset HEAD YOUR-FILE'.
  6. Commit the files that you've staged in your local repository.
    $ git commit -m "First commit"
    # Commits the tracked changes and prepares them to be pushed to a remote repository. To remove this commit and modify the file, use 'git reset --soft HEAD~1' and commit and add the file again.
  7. At the top of your GitHub repository's Quick Setup page, click  to copy the remote repository URL.
    Copy remote repository URL field
  8. In the Command prompt, add the URL for the remote repository where your local repository will be pushed.
    $ git remote add origin remote repository URL
    # Sets the new remote
    $ git remote -v
    # Verifies the new remote URL
  9. Push the changes in your local repository to GitHub.
    $ git push origin master
    # Pushes the changes in your local repository up to the remote repository you specified as th

Wednesday, March 6, 2019

Oracle SOA 12c: How To Create READ-ONLY Access To The JMS Messages For Monitor User

Create a user who only can view the JMS Messages and can not create,  delete,  move or import JMS Messages, and can not monitor other resources.

The following are the steps to allow Non Admin role users to monitor JMS resources:

1. In the left pane, select Security Realm.
2. Select <your_realm_name>.
3. In "Configuration" tab, check "Use Authorization Providers to Protect JMX Access", click save and then activate changes.
4. Restart the server.
5. In the left pane, select Security Realm.
6. Select <your_realm_name>.
7. Go to "Users and Groups".
8. In users, create a new user (such as say "jmsmonitor")
9. Adding it to group "Monitors":
    a. Select <your_realm_name>.
    b. Select "Users and Groups".
    c. Click on user name, in right pane select "Groups".
    d. From Parent Groups, select monitors, click arrow pointing right side.
10. Go to "Roles and Policies" - > Realm Policies
11. In Policy table, select "JMX Policy Editor".
12. Select "Global Scope", click next.
13. From MBean Types, select "weblogic.management.runtime"
14. Select "JMSDestinationRuntimeMBean", click next.
15. In Attributes and Operations, expand "Operations: Permission to Invoke".
16. Select "getCursorEndPosition" operation.
17. Click on "Create Policy" button
18. Click on "Add Condition", Select "User" in "Predicate List", click next, type User Argument Name (jmsmonitor), say add. Click "Finish"
19. Click on "Add Condition", Select Role in "Predicate List", click next, type Role Argument Name (Admin), say add. Click "Finish"
20. Select "Or" between Role:Admin and User:jmsmonitor and Click "Save"
21. Repeat step 10~19 for set the following operations.
    a. getCursorSize
    b. getCursorStartPosition
    c. getItems
    d. getMessage
    e. getMessages
    f. getNext
    g. getPrevious 
    h. sort

22 - Logout weblogic user and login with the new user.
23 - Go to the created module and click on the created queue
24 - Click on Monitoring tab
25 - Click on the check box associated to the queue and them Show Message button

Friday, February 8, 2019

Oracle Customer Care and Billing 2.6 IWS Services to be accessed from SOA 11g running JDK 1.6


Oracle Customer Care and Billing 2.6 is deployed on WebLogic 12c. Weblogic 12c uses JDK 1.8, which uses TLS1.2 for Transport Level Security.

If the IWS services are used by composites running on SOA11g (11.1.1.5/11.1.1.7), if we use the JDK from Oracle Download Archives, we will get an SSL Handshake Exception.

The JSK1.6 does not support TLS 1.2 unless we use the upgrade JDK to 1.7 or


The following chart depicts the protocols and algorithms supported in each JDK version:

JDK 8
(March 2014 to present)
JDK 7
(July 2011 to present)
JDK 6
(2006 to end of public updates 2013)
TLS ProtocolsTLSv1.2 (default)
TLSv1.1
TLSv1
SSLv3
TLSv1.2
TLSv1.1
TLSv1 (default)
SSLv3

TLS v1.1 (JDK 6 update 111 and above)
TLSv1 (default)
SSLv3
JSSE Ciphers:Ciphers in JDK 8Ciphers in JDK 7Ciphers in JDK 6
Reference:JDK 8 JSSEJDK 7 JSSEJDK 6 JSSE
Java Cryptography Extension, Unlimited Strength (explained later)JCE for JDK 8JCE for JDK 7JCE for JDK 6



JDK 1.6 update 211 can be downloaded from https://support.oracle.com patch # 28414647


Share your code in Git using Eclipse

Share your code in Git using Eclipse Share your Eclipse project with your team in an Azure DevOps Services/TFS Git repo. Prerequisites ...