Thursday, November 6, 2014

Amazon EC2: Authorizing Inbound Traffic for Your Instances

Amazon EC2: Authorizing Inbound Traffic for Your Instances


Adding a Rule for Inbound SSH Traffic to a Linux Instance


  • In the navigation pane of the Amazon EC2 console, click Instances. Select your instance and look at the Description tab; Security groups lists the security groups that are associated with the instance. Click view rules to display a list of the rules that are in effect for the instance.








  • In the navigation pane, click Security Groups. Select one of the security groups associated with your instance.
  • In the details pane, on the Inbound tab, click Edit. In the dialog, click Add Rule, and then select SSH from the Type list.






  • In the Source field, specify the public IP address of your computer, in CIDR notation. For example, if your IP address is 203.0.113.25, specify 203.0.113.25/32 to list this single IP address in CIDR notation. If your company allocates addresses from a range, specify the entire range, such as 203.0.113.0/24.
     Use the url  http://checkip.amazonaws.com/ to find you IP Address



  • Click Save.





Amazon EC2: Converting Your Private Key Using PuTTYgen

Amazon EC2: Converting Your Private Key Using PuTTYgen

PuTTY does not natively support the private key format (.pem) generated by Amazon EC2. PuTTY has a tool named PuTTYgen, which can convert keys to the required PuTTY format (.ppk). You must convert your private key into this format (.ppk) before attempting to connect to your instance using PuTTY.


To convert your private key

  • Start PuTTYgen (for example, from the Start menu, click All Programs > PuTTY > PuTTYgen).
  • Under Type of key to generate, select SSH-2 RSA.













































  • Click Load. By default, PuTTYgen displays only files with the extension .ppk. To locate your .pem file, select the option to display files of all types.






















  • Click OK
















  • Click Save private key to save the key in the format that PuTTY can use. PuTTYgen displays a warning about saving the key without a passphrase. Click Yes.

Note
A passphrase on a private key is an extra layer of protection, so even if your private key is discovered, it can't be used without the passphrase. The downside to using a passphrase is that it makes automation harder because human intervention is needed to log on to an instance, or copy files to an instance.






  • Specify the same name for the key that you used for the key pair (for example, my-key-pair). PuTTY automatically adds the .ppk file extension.



















  • Your private key is now in the correct format for use with PuTTY. You can now connect to your instance using PuTTY's SSH client.

Wednesday, November 5, 2014

Amazon Elastic EC2: Steps to launch an Amazon EC2 Instance

Amazon Elastic EC2: Steps to launch an Amazon EC2 Instance

This thread discusses the steps to launch a Linux instance using AWS Management Console.


  • To launch an Amazon EC2 instance, open the Amazon EC2 console using the URL https://console.aws.amazon.com/ec2
  • This will take you the following page.



























  • Click on Launch Instance
  • Select The Amazon Machine Image (AMI).  Select the 64 bit Amazon Linux AMI. Marked
















  • Select t1.micro from the instance type page. Click on Next: Configure Instance Details. This will navigate you to the "Configure Instance Details" Page















  • Click on Review and Launch.


















  • Select "Make General Purpose SSD the default boot volume for all instances from the console going forward " as the option.



  • Click on Edit Security Groups from the Review Instance Launch screen

















  • Select an existing security group. Select the check box and click on Review and Launch






  • Click on Launch



















  • Choose and Existing Key pair if the key pair exists OR create another pair of key.
  • Click on Launch Instance



  • On the Resource screen, click on Running Instance



Amazon EC2 : Connecting to Your Linux Instance from Windows Using PuTTY

Amazon EC2 : Connecting to Your Linux Instance from Windows Using PuTTY
  1. Start PuTTY (from the Start menu, click All Programs > PuTTY > PuTTY).
  2. In the Category pane, select Session and complete the following fields:
    1. In the Host Name box, enter user_name@public_dns_name. Be sure to specify the appropriate user name for your AMI. For example:
      • For an Amazon Linux AMI, the user name is ec2-user.
      • For a RHEL5 AMI, the user name is either root or ec2-user.
      • For an Ubuntu AMI, the user name is ubuntu.
      • For a Fedora AMI, the user name is either fedora or ec2-user.
      • For SUSE Linux, the user name is root.
      • Otherwise, if ec2-user and root don't work, check with the AMI provider.
    2. Under Connection type, select SSH.
    3. Ensure that Port is 22.

  3. In the Category pane, expand Connection, expand SSH, and then select Auth. Complete the following:
    1. Click Browse.
    2. Select the .ppk file that you generated for your key pair, and then click Open.
    3. (Optional) If you plan to start this session again later, you can save the session information for future use. Select Session in the Category tree, enter a name for the session in Saved Sessions, and then click Save.
    4. Click Open to start the PuTTY session.
  4. If this is the first time you have connected to this instance, PuTTY displays a security alert dialog box that asks whether you trust the host you are connecting to.
  5. (Optional) Verify that the fingerprint in the security alert matches the fingerprint that you obtained in step 1. If these fingerprints don't match, someone might be attempting a "man-in-the-middle" attack. If they match, continue to the next step.
  6. Click Yes. A window opens and you are connected to your instance


Tuesday, October 21, 2014

Oracle® Fusion Middleware SOA-11g Release 2 (11.1.1.7) Configure SAP IDocs On Oracle SOA-B2B platform

Oracle® Fusion Middleware SOA-11g Release 2 (11.1.1.7) Configure SAP IDocs On Oracle SOA-B2B platform

This BLOG thread discusses the steps for Oracle B2B setup for SAP IDocs. The thread discusses the use of

  • Oracle EDIFECS Spec Builder Version 7.0.5
  • Oracle B2B Console for version 11.1.1.7  

Steps for building the ECS file, the Parser and XSD

  • Start the B2B Document Editor 
  • Click on File->New
  • Choose Positional Flat File
  • Choose Blank Positional





  • Press Next
  • You should be able to see a blank PFF guideline

  • Click on File-> Import
  • Select the SAP IDoc Guideline. Press next

  • Ensure the IDoc type is correct.


  • Please see below when the IDocs file is sucessfully imported

  • Click on File
  • Click Save
  • Give the Name to the ECS File


  • On the Analyzer /  Data window, open a sample Data File
  • On the Analyzer Wizard, verify the record terminator, Un-check the "First record in the guideline starts a new message and press Next, Press Finish in the subsequent window.



  • For each tag in the sample data displayed on the Analyzer / Data window, verify the tags, in the event the tags are different, 


  • Select the Record ID whose tag needs to be set, 



  • Click Edit, set Tag Value E2EDK14 (in this case). Click Set Current. Click Close


  • Ensure the Tag field is set to "Value" and  Tag Value is set to "E2EDk14"

  • Repeat this for all the elements.

Generate the Parser File

  • Click on Edit.Click on Generate Parser Schema



  • Ensure that the Record Terminator is correct and click on the browse button and give tne name to the parser file.



  • Give the name to the parser file and Click o Save





  • Copy the parser ecs  file in the directory $Oracle_SOA_Home\soa\thirdparty\edifecs\XEngine\config\schema (for eg. - D:\OFMW11g\PS3MWHome\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\config\schema)


  • Add an entry for this parser ecs in $Oracle_SOA_Home\soa\thirdparty\edifecs\XEngine\config\XERegistry.xml

  • To add this entry, edit the XERegistry.xml in a text editor and add below “Positional flat parser schemas”








Salesforce.com Creating the Community

Salesforce.com Creating the Community

To create the MindTelligent Community, complete the following steps:

  • Go to Setup | Customize | Communities | All Communities | Manage Communities.

  • Click on the New Community button.

  • Enter Force MindTelligents for the community name.

  •  Enter Community for MindTelligent  Clients and Partners for the Description field to describe the purpose of the community.

  •  The next step is to enter a URL for the community. This will equate to a subdirectory name underneath the domain prefix entered by you, when you  enabled the communities and the Salesforce instance that you are running on. For this example, enter volunteers.


  • Your screen should resemble the following screenshot:





















  • Verify the success message

Salesforce.com Building a Community

Salesforce.com Building a Community

The purpose of communities is to share information and support collaboration between companies, their customers, and their partners. A Salesforce organization can have multiple communities, each serving a distinct purpose or segment of customers/partners.

To enable communities in Salesforce, log in to your Salesforce Developer edition and complete the following steps:
  • Go to Setup | Customize | Communities | Settings.
  • Select Enable Communities
  • Enter a domain name prefix that will uniquely identify your communities on Force.com, and click on the Check Availability button. If the domain prefix is already used, enter a different domain prefix and try again.

  • Click on Save and then click on OK in the dialog window that will give you a warning that the changes cannot be undone.








    Tuesday, September 9, 2014

    Oracle® Fusion Middleware Identity Governance Framework Initialize and Obtain Identity Directory Handle from JPS Context

    The Identity Governance Framework (IGF) initiative enables secure exchange of identity-related information between users and applications and service providers. It provides privacy and governance semantics to applications and services infrastructure.


    The following code sample initializes and obtains the identity directory handle from JPS context.
    import oracle.igf.ids.UserManager;
    import oracle.igf.ids.GroupManager;
    import oracle.igf.ids.config.OperationalConfig;
    import oracle.igf.ids.IdentityDirectoryFactory;
    import oracle.igf.ids.IdentityDirectory;
    import oracle.igf.ids.IDSException;
    
    import oracle.security.jps.JpsContext;
    import oracle.security.jps.JpsContextFactory;
    import oracle.security.jps.service.idstore.IdentityStoreService;
    
    public class IdsSample {
    
        private IdentityDirectory ids;
        private UserManager uMgr;
        private GroupManager gMgr;
    
        public IdsSample() throws IDSException {
    
            // Get IdentityDirectory from JpsContext
            try {
                JpsContext context =
    JpsContextFactory.getContextFactory().getContext();
                IdentityStoreService idstore = (IdentityStoreService)
    context.getServiceInstance(IdentityStoreService.class);
                ids = idstore.getIdentityStore();
            } catch (Exception e) {
                throw new IDSException(e);
            }        
    
     // Get UserManager and GroupManager handles
            uMgr = ids.getUserManager();
            gMgr = ids.getGroupManager();
        }
    }

    Monday, September 8, 2014

    Oracle® Fusion Middleware OES-11g Release 2 (11.1.2.2.0)-Configure Oracle Entitlements Server WebLogic Security Module High Availability

     


    1. Run OESCLIENT_HOME/oessm/bin/config.sh to create a WebLogic Security Module and a WebLogic Server domain.
       For example: ./config.sh -smType wls -smConfigId <wls_name> -serverLocation <wls_home> -pdServer <oes_admin_server> -pdPort <oes_admin_ssl_port>
    2. On the Welcome screen, select Create a WebLogic Domain then click Next.

    3. On the Select Domain Source screen, select Generate a domain configured automatically to support the following added products. From the list, select Oracle Entitlements Server WebLogic Security Module on Weblogic For Managed Server.

    4. On the Specify Domain Name and Location screen, enter the name and location for the domain and all its applications.

    5. On the Configure Administration Server Username and Password screen, enter the admin user name and password

    6. On the Configure Server Start Mode and JDK screen, select Production Mode and JDK.

    7. On the Configure Administration Server screen, enter the following:
        Name: AdminServer
        Listen address: All Local Addresses
        Listen port: 7001
        SSL listen port: 7002
        Select SSL Enabled then click Next.

    8. Create two managed servers as the following:
        Name           Listen Address      Port     SSL
       wlssm_server1  All Local Addresses  14610   14611  
       wlssm_server2  All Local Addresses  14612   14613

    9. Create a cluster and add wlssm_server1, wlssm_server2 to the cluster.

    10. Finish to create the domain.

    11. Start the admin Server,  wlssm_server1 and wlssm_server2, make sure to have Node Manager Running, 
    having StartScriptEnabled=true

    12. Check in deployments => oracle.oes.client.pd.ssl (11.1.1.3.0) Active

    13. You will see "PDP registration succeeded".

    Thursday, September 4, 2014

    Oracle API Gateway 11.1.2.3 Virtualizing a Service in API Service Manager

    Oracle API Gateway 11.1.2.3 Virtualizing a Service in API Service Manager

    You can use the API Services tab in API Service Manager to virtualize services with the API Gateway. The Business Services repository stores service URLs, definitions and related information such as XML schemas. Clients can query this repository for service information (for example, URLs or WSDL files), and use it to send messages to the service through the API Gateway.


    Step 1—Basic Information

    The first step in the New API Service wizard enables you to virtualize a service with or without a Web Services Definition Language (WSDL) file.
    Virtualizing a REST API-based Service
    To virtualize a REST API-based service without a WSDL file, perform the following steps:
    1. Click No, my Service will be defined manually, and enter the details for your service, for example:
      • NameMyService
      • Destination URLhttp://www.example.com/my_service
    2. Click Next to specify how service is exposed.
    Virtualizing a Web Service
    To virtualize an example Web service using the API Service Manager, perform the following steps:
    1. Click Yes, I know a URL from which to get a WSDL, and enter a URL in the WSDL URL field, for example:
      http://localhost:7070/axis/services/urn:xmltoday-delayed-quotes?wsdl
    2. Click Next to view a WSDL import summary.
    3. Click Next to specify how the service is exposed.

    Step 2—Service Exposure

    The second step in the wizard enables you to specify how the service is exposed. Perform the following steps:
    1. Enter or select the protocol. Defaults to HTTP. You can also click Show Details to view the default port address (${env.PORT.TRAFFIC} defaults to 8080).
    2. Enter or select the services group. Defaults to Default Services.
    3. Enter the relative path. Defaults to the path after the service domain name (for example, my_service). You may wish to virtualize the service on a different relative path.
    4. Click Next.

    Step 3—Request Processing

    The third step in the wizard enables you to specify policy packages used for request processing. (for example, an OAuth policy package for authentication. Perform the following steps:
    1. Click the green plus icon, and select a policy package from the list.
    2. Select whether this policy package is Required or Optional. Defaults to Required.
    3. Click the Edit Parameters icon to specify any policy parameters (for example, the value of a message attribute selector such as ${http.request.uri}).
    4. Repeat these steps to add more request processing policy packages.
    5. Click Next when finished.
    [Note]Note
    You can use the Policy Studio to create reusabe policy packages that can be applied to services in API Service Manager.  

    Step 4—Routing

    The fourth step in the wizard enables you to specify policy packages used for routing (for example, JMS). Perform the following steps:
    1. Click the green plus icon, and select a policy package from the list.
    2. Select whether this policy package is Required or Optional. Defaults to Required.
    3. Click the Edit Parameters icon to specify any policy parameters (for example, the value of a message attribute selector such as ${http.headers}).
    4. Repeat these steps to add more routing policy packages.
    5. Click Next when finished.

    Step 5—Response Processing

    The fifth step in the wizard enables you to specify policy packages used for response processing (for example, a policy package that removes sensitive information such as credit card details from the message). Perform the following steps:
    1. Click the green plus icon, and select a policy package from the list.
    2. Select whether this policy package is Required or Optional. Defaults to Required.
    3. Click the Edit Parameters icon to specify any policy parameters (for example, the value of a message attribute selector such as ${content.body}).
    4. Repeat these steps to add more repsonse processing policy packages.
    5. Click Next when finished.

    Step 6—Monitoring

    The sixth step in the wizard enables you to select the following monitoring options for the service:
    • Monitor API Service usage:
      Specifies whether to store message metrics for this service. This is selected by default.
    • Monitor API Service usage per client:
      Specifies whether to generate reports monitoring which authenticated clients are calling which services. This is selected by default.
    • Monitor client usage:
      If you want to generate reports on authenticated clients, but are not interested in which services they are calling, select this option and deselectMonitoring service usage per client.
    • Message Attribute:
      Enter the message attribute to use to identify authenticated clients. The default authentication.subject.id attribute stores the identifier of the authenticated user (for example, the username or user's X.509 Distinguished Name).
    Click Next when finished.

    Step 7—Tags

    The final step in the wizard enables you to specify tags for this service. Tags are user-friendly names to help organize, search, and browse API Gateways and services in API Gateway Manager and Policy Studio. Perform the following steps:
    1. Click the green plus icon to add a tag.
    2. Enter a Tag name (for example, Dept).
    3. Enter a Value (for example, QA).
    4. Click Finish.
    To view services by tag in API Gateway Manager, perform the following steps:
    1. Click the Show Columns button on the right in the API Services toolbar.
    2. Select the tag that you wish to display.
    3. Click Apply to view tag in the list.
    The virtualized service is displayed on the API Services tab:
    Registered Service

    Deploying to a Group

    When you have completed the steps in the wizard, you must deploy the updated configuration to a API Gateway group, or a subset of API Gateways in a group, as follows:
    1. Click Actions -> Deploy on the left in the API Services tab.
    2. In the Deployment Wizard, select the group and API Gateway instance(s) to which you wish to deploy the current working configuration, and click theNext.
    3. Enter a comment for this deployment (for example, registering google search service).
    4. Click Deploy.
    5. Click Finish.